Saving Error in Project Server 2013, Need Help! RRS feed

  • Question

  • Hey All,

    I am running into issues with a Projects saving from Project Pro 2013 to our Project Server 2013 Farm.

    It is strange, when someone tries to save a project out of Project Pro 2013 to Project Server, it will run through the "Synchronizing Data to the Server", and then bombs out with error

    Job Type: Save

    Error ID:9000(0x2328)

    The project could not be saved to the server, Etc..

    My understanding is that this is a generic save error that could mean many things.

    In the ULS logs under "Active Cache Save" , I am getting:

    "Cancelling correlation 1339927b-e9e5-e311-941d-00155d2bc10d as save is an overwrite or resubmit"

    What is strange at this point is if I check the project back in, and re-open/re-checkout the project, and try to save again, it is successful in saving.

    Just a few details about the environment:

    Project Server Version: 2013 RTM (In the process of upgrading)

    SharePoint Version: 2013 RTM (In the process of upgrading)

    Project Structure: One Master Project with all other projects being subprojects of the master

    Published Status: All Published

    SQL Version: SQL Server 2012 SP1

    User Count: About 5 currently

    Deployment: 1 WFE, 1 APP Server, 1 SQL Server

    It is just odd, as it seems to be completely random. We have tried clearing caches out to see if that resolves it but it did not. It is just odd that it takes two saves for it to actually work correctly, and is problematic as the many times they are saving from the master and it bombs out there.

    I am not sure how it could be an issue as it is usually just a single user working on the individual subprojects.

    Maybe it is an issue in the RTM? I couldn't find any info in any of the CU's or SP's that addresses this directly

    Has anyone seen this, or have any suggestions?

    MS Support has not been any help at all.

    Thanks all

    Thursday, June 26, 2014 2:39 PM


  • I have heard of issues with Master and Sub-Projects and both being published to Project Server, as a rule it is a feature I learnt to avoid as a result of bad experiences with earlier versions of Project Server.

    Whilst this will not resolve the issue you have encountered the following suggestion may help you avoid pain in the future and leverages the potential of Project Server to represent common attributes for projects.

    Typically a Master/Sub Project environment is intended to reflect projects that are commonly aligned - it is not unusual for a Master Project to represent a programme and for there to be multiple sub-projects forming the programme - there can be programme level events that have multiple predecessors from multiple sub-projects. 

    Rather than create a master and sub-project situation I would suggest looking to define two Enterprise Custom Project fields to assist with such situations. The first being a Project Field called Programme that has a look up table with a list of current programmes you can select from. The second Project Field would be a Programme Status Field  with an associated lookup table with 3 values, Master, Sub-Project, Standalone.

    You can have a project represent the Master (Programme) project and open it and all sub-projects in the programme (albeit this would have to be a one by one action to begin with). With all the projects open go and open a New Window in Project Professional and elect to include all the open projects in the new window - this will create a new project with all the selected projects showing as "embedded objects" and then create dependencies from sub-projects to programme level events in the Master Project (I would suggest what I call "one way traffic" when creating "cross project dependencies" to avoid further headaches). Close the project, you will be prompted to save changes which you should do but do not save the new window "container" project. The dependencies across the projects will persist - in each project you will be able to see external successors - tasks in the master project. In the master project you will be able to see external predecessors.

    In PWA you can create Project Centre Programme views that filter to exclude projects that ARE Standalone and group them by Programme and sort by Programme Status Field - this will ensure that the "Master" sits at the top of the pile for each programme grouping.

    Just a suggestion - I hope the issue you have encountered is resolved soon.

    Dominic Moss | MAPM Microsoft Certified Technology Specialist | Our Newsletter: PM News Project Server Specialists Project Server PRIME | Twitter: @Twitter | Facebook: @Facebook | Linkedin: Wellingtone

    • Marked as answer by jman26 Monday, June 30, 2014 10:09 PM
    Thursday, June 26, 2014 3:25 PM