none
PM receiving 9000(0x2328) Error Upon Save

    Question

  • I have a PM that is getting a 9000(0x2328) when saving a particular project.  Details:

    • She attempts the save – but the save process never even reaches her personal queue.  When re-attempting the save, she receives the error.
    • She is able to open and save other schedules without encountering this issue
    • Admin (myself) can open this schedule on my computer and save & publish without any issues
    • We must clear her cache to get the schedule checked back in (checking it in from the server doesn’t seem to work)
    • I’ve had her clear out the Microsoft > MS Project >14 > Cache file – no change

    Any ideas what could be causing this on her computer (especially since she can work with other schedules and I can work with this one)?

    Thanks,

    Randy

    Tuesday, October 23, 2012 7:10 PM

All replies

  • Randy,

    Can user reproduce this issue using different computer?

    Try creating another User Profile in Project  Pro.


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Please click Mark As Answer; if a post solves your problem or Vote As Helpful; if a post has been useful to you.This can be beneficial to other community members reading the thread.

    Tuesday, October 23, 2012 7:39 PM
    Moderator
  • Randy --
     
    Please refer to the following Hotfix for this very issue:
     
     
    Hope this helps.

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    • Proposed as answer by ARaja Wednesday, October 24, 2012 5:40 AM
    Tuesday, October 23, 2012 8:05 PM
    Moderator
  • HI,

    Below Project Professional 2010 December 2011 client CU adresses the same issue

    Try doing "save for sharing" for that project if the issue is still there after installing the CU 

    Wednesday, October 24, 2012 3:19 AM
  • Hi Dale -  Thanks for the reply.     According to the link, installing the hotfix changes the version number of SharePoint to 14.0.6015.  We’re at 14.0.6029, which is the Service Pack 1 version, which was released June 2011.  Service packs include the set of hotfixes and updates up to that point, so since this hotfix is from late 2010, it should be part of the service pack.  Which means that yes we do have the hotfix applied, and if we try to deploy it the hotfix will let us know a later version of the update has already been applied....

    What I did find is that after I (Admin) opened and published the project, the problem went away for the PM.

    Wednesday, October 24, 2012 4:25 PM
  • Randy --
     
    So, is the problem fixed or not fixed?  And yes, you are more than welcome for the help, my friend!  :)

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Wednesday, October 24, 2012 8:32 PM
    Moderator
  • I guess we can close this post.   No action was taken - other than me publishing the schedule - which resulted in the error going away for the PM.    It will happen again - when it does, I will try the same thing.  If having someone else publish the schedule in question resolves this issue, then we have a valid work around.     Thanks!
    Wednesday, October 24, 2012 9:33 PM
  • Randy --
     
    Thanks for letting us know.  You are always welcome for the help, my friend.

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Thursday, October 25, 2012 12:34 AM
    Moderator