none
Error when Publishing Project on PS2013 - Blocking correlation 78% RRS feed

  • Question

  • Hello,

    I have a strange error on a Project Server 2013 Platform. Certain projects refuse to be published, and the task finishes as an blocking job, with an achievement level of 78%. The error is Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.SynchronizeTaskListInManagedModeMessage. I put the complete error message at the end of this post. The ULS doesn't provide me more détails.

    To get more infos in ULS, I switched the log mode to verbose, and I got an interesting message:

    Node   Consistency Message: Assignment Save.   Uid=35d15af1-908a-e311-b465-005056a27863
    Bad assnIndex 4 passed for   654d65c4-0a59-e311-a55a-005056a27863
    Bad assnIndex 4 passed for   654d65c4-0a59-e311-a55a-005056a27863
    Bad assnIndex 4 passed for   654d65c4-0a59-e311-a55a-005056a27863
    Node Consistency Message:   Summary Resource Assignment Save.

    I tried googling this keyword "assnIndex" : it returns no answer. The GUID after the "for" is a ResourceUID. But what means assnIndex ?

    Here are some additional info, saying when the project can be publihed, and when it returns an error:

    • - if the project contains tasks with only generic resources, it can be publiehed without pb => OK
    • - if the project contains tasks assigned to less than 2 named resources  it can be published => OK
    • - if the project contains at least 1 task with more than 2 named resource, it fails => KO
    • - if I desactivate this task with 3 named resource, the project can be published => OK

    The workaround is to split tasks, so that each is assigned to max 2 resources, but it can not be a solution.

    If somebody can help me to find a solution, it would be very great !

    I looked for some CU but, it seems that I'm up to date:

    Archi: 1 WFE, 1 AS, 1 SQL Server 2012

    OS: W2008R2SP1

    Version extracted from the dbo.Versions table: 15.0.4420.1017

    We use only standard function, no specific developement, Handler, etc.

    Than you for your help,

    Sylvain

    Detailed error message:

    <?xml version="1.0" encoding="utf-16"?>
    <errinfo>
     <general>
      <class name="Microsoft.Office.Project.Server.BusinessLayer.Queue.Message">
       <error id="23000" name="ProjectPublishFailure" uid="7de05826-878e-e311-a08b-005056a27863" projectuid="b0baeed4-c48d-e311-b465-005056a27863" messagetype="Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.SynchronizeTaskListInManagedModeMessage" messageID="38" stage="" blocking="Block"/>
      </class>
      <class name="Queue">
       <error id="26000" name="GeneralQueueJobFailed" uid="7ee05826-878e-e311-a08b-005056a27863" JobUID="9f48511e-878e-e311-838a-005056a25f52" ComputerName="b29ed4a6-9e80-4c9f-b3c2-ad2d85d17ffa" GroupType="ProjectPublish" MessageType="SynchronizeTaskListInManagedModeMessage" MessageId="38" Stage="" CorrelationUID="e99d521e-878e-e311-a08b-005056a27863"/>
      </class>
     </general>
    </errinfo>

    Wednesday, February 5, 2014 5:59 PM

Answers

  • Hi Sylvain,

    I think I have the answer to your problem. Solved the same issue yesterday on a customers system. Please check the properties of the task list in the project site. If you select the properties of the "assigned to" field you might find that it is set to "Allow multiple selections: No".

    If this is the case you will find that there is only one resource on the task list in the site, even if you assign to resources in the project plan. Cool thing is that there is no error on publishing with two resources. But with three resources and more the publish will fail on 78%.

    So switch back to allow multiple selections and it should work again.

    Hope that helps

    Kind regards

    Christoph


    Christoph Muelder | Senior Consultant, MCTS, MCSE, MCT | SOLVIN information management GmbH, Germany

    Friday, April 4, 2014 5:57 AM

All replies

  • Hi,

    Since its happening with certain projects only, chances are that it could be due to corrupted project data and confusing details in ULS may can seen as misleading.

    you can follow these steps (credit goes to our very dear Dale Howard), he also listed these steps in a blog but i cudnt find it rite now:

    1.  Ask the Project Server administrator to restore the backed up project again (even though it is corrupted).
    2.  Ask the PM to open the project in Microsoft Project 2010.
    3.  Ask the PM to add the Save for Sharing button to the Quick Access Toolbar (File > Options > Quick Access Toolbar).
    4.  Click the Save for Sharing button and save the enterprise project as an MPP file.
    5.  Close the MPP file and then reopen it.
    6.  Save the MPP file with the same name as the enterprise project.
     

    According to Microsoft staff, the Save for Sharing feature is the new way to repair a corrupted enterprise project.  

    http://social.technet.microsoft.com/Forums/projectserver/en-US/cda7b102-b0a0-4ec1-9a1e-b059f565a47e/msp2010-project-schedule-can-not-be-opened-in-project-client?forum=projectserver2010general

    let us know if this works for you.

    cheers.


    Khurram Jamshed - MBA, PMP, MCTS, MCITP ( Blog, Twitter, Linkedin )
    If you found this post helpful, please “Vote as Helpful”. If it answered your question, please “Mark as Answer”.

    Thursday, February 6, 2014 7:28 AM
  • Hi Khurram,

    Thank you for your suggestion. I've just tried it, without success.

    In fact I can reproduce exactly the same problem with a completly new Project:

    1. Create a new project
    2. Add only one task
    3. Add 3 resources to the team
    4. Assign those 3 ressources to the task
    5. Publish
    6. I get the publish error

    Then to "solve" the problem

    1. I remove one of the 3 resources,
    2. I publish
    3. It's OK, the project is published

    Regardless the resource I use, it will always be the same, so it's not a problem on my project, but with my config: maybe something wrong with calendars, resource settings or whatever.

    Thank you, and don't hesitate if you have other suggestions :)

    Sylvain

    Thursday, February 6, 2014 7:51 AM
  • It can also be the case where there are duplicate resources or duplicate RES_OPTINDX values. Please run the below queries.

    1. Get the Proj_GUID by running the below query on ProjectServer Draft database

    Select * from MSP_PROJECTS where Proj_name like 'name of the project' – Get the project GUID

    2. Run the below query on draft database and look for duplicate RES_OPTINDX values

    select res_type, RES_OPTINDX, RES_UID, RES_name from MSP_PROJECT_RESOURCES where PROJ_UID= 'PROJ UID' order by RES_OPTINDX

    what is the output let us know if some thing is wrong delete that from project plan then publish.


    kirtesh

    Thursday, February 6, 2014 9:48 AM
  • Thank for your reply.

    The result of the SQL Request is:

    res_type RES_OPTINDX	RES_UID					RES_name
    -1	0.0000000000	A0CB8B77-2A8C-436D-0000-0000000000FF	NULL
    -3	0.0000000000	A0CB8B78-2A8C-436D-0000-0000000000FF	NULL
    -2	0.0000000000	A0CB8B79-2A8C-436D-0000-0000000000FF	NULL
    -4	1.0000000000	2453DD69-018F-E311-838A-005056A25F52	NULL
    2	2.0000000000	26A34761-B156-E311-B3B4-005056A27863	NAMED1
    2	3.0000000000	E59CEBB7-8984-E311-B465-005056A27863	NAMED2
    2	4.0000000000	D24D65C4-0A59-E311-A55A-005056A27863	NAMED3
    20	5.0000000000	9692DDC5-B45D-E311-A55A-005056A27863	GENE1
    20	6.0000000000	9792DDC5-B45D-E311-A55A-005056A27863	GENE2
    20	7.0000000000	9892DDC5-B45D-E311-A55A-005056A27863	GENE3
    20	8.0000000000	9992DDC5-B45D-E311-A55A-005056A27863	GENE4
    

    Something wrong ?

    Sylvain

     

    Thursday, February 6, 2014 1:44 PM
  • Remove upper 4 resource from plan then publish. 

    It will work issue is because of RES_OPTINDX. 

    Who are these resource you can query on resource table and givewhere condition for above 4  RES_UID then remove them from plan and publish it.


    kirtesh

    Thursday, February 6, 2014 1:48 PM
  • Hi,

    if I execute this request:

    SELECT *
    FROM [draft].[MSP_RESOURCES]
    WHERE
    [RES_UID] IN
    (
    'A0CB8B77-2A8C-436D-0000-0000000000FF',
    'A0CB8B78-2A8C-436D-0000-0000000000FF',
    'A0CB8B79-2A8C-436D-0000-0000000000FF',
    '2453DD69-018F-E311-838A-005056A25F52'
    )
    

    I get no resource. ,So I can not exclude them from the plan.

    But who are these resources ? What is stange, is that I found some assignment invoving this 4 resource in all projects (ask through SQL Request in draft db)

    How can unexisting resources have assignments ?

    Sylvain

    Thursday, February 6, 2014 2:17 PM
  • I am sure earlier these resources were part of project plan then project and they had assignment.

    Project Owner removed them after ward when i dont know :) .

    You are not getting Resource name as they are null now and not having any value.

    check in Publish and reporting DB to investigate further and delete those assignment. until unless you will not remove it you can not be able to publish the project.

    Open Project Team from PWA or MPP and check if you can get any resource which may cause issue and remove them.

    If there is no problem then remove those assignment form plan then save and publish. 


    kirtesh

    Thursday, February 6, 2014 2:25 PM
  • Hi Sylvain, 

    this seems to be like a bug identified by project team in Redmond now. Brian Smith has blogged about it, you may can open a incident ticket to get a fix soon, or wait till April CU if its not really urgent.

    Here are the details: http://blogs.technet.com/b/projectsupport/archive/2014/02/06/project-server-2013-and-project-online-what-happened-to-my-resources.aspx

    hope this helps.


    Khurram Jamshed - MBA, PMP, MCTS, MCITP ( Blog, Twitter, Linkedin )
    If you found this post helpful, please “Vote as Helpful”. If it answered your question, please “Mark as Answer”.

    Friday, February 7, 2014 7:08 AM
  • Hi Khurram,

    Thank you for this link: knowing that it's a MS bug does not solve the problem, but help to understand what's happening.

    We already opened a ticket yesterday morning, and we are in the process of investigation. Thanks to your very relevant advices, I have a lot of data to communicate to them, so it will help the resolution.

    In Brians's article, he talks about "MSP changes named resource to unnamed material ressource". We also have this symptom as well.

    So I guess that we are in the good direction.

    The bad news is that unless my researchs in all tables, I still have not found my "null" resources.

    I will try to delete the assignments on these resources, but the problem is that if I create a new project, this assignment are created. It means that somewhere, these void resources must be stored, and that I have to "kill" them. But first, I have to find them.

    I will keep you informed of the resolution of the problem.

    Sylvain


    Friday, February 7, 2014 8:46 AM
  • Hi Khurram,

    We are facing the same error in Project Server 2010 SP2 environment.

    Is someone aware of this issue happening in MS EPM 2010 and any fix for this.

    Thanks,

    Srivatsava Konduri

    Monday, March 3, 2014 4:16 PM
  • This looks like a corrupted SQL server database.  I would suggest that you run DBCC CHECKDB on all four of your project databases and see if that runs without any issues.  IF it does you can do the DBCC CHECKDB /REPAIR.   If you have torn page then you may need to go back to a previous backup.

    Also its a good practice to run SQL database maintenance plan to UPDATE STATIS and UPDATE INDEXES

    Cheers


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Tuesday, March 4, 2014 1:30 AM
    Moderator
  • Hi,

    Here is an update on my problem: publish error at 78% if more than 2 resources on a task.

    The issue is still open: we have a ticket opened with Microsoft Support.

    The workaround is to split all tasks where more than 2 resources are involved.

    We also had the problem described by Brian Smith "Where are my resources", and applied the hotfix (update of stored procedure, repair of the corrupted projects).

    But even after this hotfix, we still have the problem: project publication blocked at 78%.

    If somebody already had this problem, please let me know. Thank you !

    Sylvain

    Tuesday, March 4, 2014 9:21 AM
  • Hi

    Check if you have inactive tasks in those projects which you are getting error at 78% when publishing ?

    Tuesday, March 4, 2014 3:42 PM
  • Hi,

    In some cases, I have inactive tasks, but in some other projects which fails, there are non inactive tasks.

    Wednesday, March 5, 2014 7:34 AM
  • Hi Sylvain,

    I think I have the answer to your problem. Solved the same issue yesterday on a customers system. Please check the properties of the task list in the project site. If you select the properties of the "assigned to" field you might find that it is set to "Allow multiple selections: No".

    If this is the case you will find that there is only one resource on the task list in the site, even if you assign to resources in the project plan. Cool thing is that there is no error on publishing with two resources. But with three resources and more the publish will fail on 78%.

    So switch back to allow multiple selections and it should work again.

    Hope that helps

    Kind regards

    Christoph


    Christoph Muelder | Senior Consultant, MCTS, MCSE, MCT | SOLVIN information management GmbH, Germany

    Friday, April 4, 2014 5:57 AM
  • Hi Christoph,

    Bravo, you exactly pointed my problem. I've just checked, and the Assigned To field was set with Allow multiple selection to NO. I switched it to  yes, publish the project with 3 resources, and it worked :-)

    Thank you very much for your help, it's a really great news !

    Sylvain

    Friday, April 4, 2014 6:47 AM
  • Hi Sylvain

    great. Your support call is still open?

    If yes, tell them please the issue with the two resources assigned :-)

    Kind regards from Hamburg

    Christoph


    Christoph Muelder | Senior Consultant, MCTS, MCSE, MCT | SOLVIN information management GmbH, Germany

    Friday, April 4, 2014 7:16 AM
  • Hi,

    I gave them the feedback that you found the solution. Now when I read the error message, it seems to be so obvious ! But it wasn't: the fact that it crashed at 3 and not at 2 resources didn't simplify the diagnostic...

    <error id="23000" name="ProjectPublishFailure" uid="7de05826-878e-e311-a08b-005056a27863"

    projectuid="b0baeed4-c48d-e311-b465-005056a27863"

    messagetype="Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.SynchronizeTaskListInManagedModeMessage"

    Anyway, vielen Dank for sharing the solution to this problem !

    Sylvain


    Friday, April 4, 2014 9:21 AM
  • Hi Sylvain, Christoph,

    please tell me where to locate the assigned to field properties. I ahve same issue and I need to check this field  for multiple selection. please help.

    Thanks

    james

    Monday, September 1, 2014 7:06 PM
  • Hi Christoph,

    I am facing the same issue and tried to go with your solution.

    But, I could not find the "Allow Multiple Selection" anywhere on project Site.

    Can you please let me know the steps to reach that option ?

    Thanks,

    Abhishek

    Thursday, May 21, 2015 6:12 AM
  • Hi

    on the project site (the website associated with the project having the issue) you will find a SharePoint list named "tasks".

    In the field settings of the list there is a field "assigned to". That might have the option "allow multiple selection" in the properties.

    Christoph


    Christoph Muelder | Senior Consultant, MCTS, MCSE | SOLVIN information management GmbH, Germany

    Thursday, May 21, 2015 6:17 AM
  • With reference to this screenshot, can you specify where can i find properties option.

    Thanks,

    Abhishek

    Thursday, May 21, 2015 6:32 AM
  • Ribbon / List / List Settings

    Regards

    Christoph


    Christoph Muelder | Senior Consultant, MCTS, MCSE | SOLVIN information management GmbH, Germany

    Thursday, May 21, 2015 6:48 AM
  • As i can see, the option, you are specifying, is already selected as 'Yes'.

    But, publishing is still getting stuck at 78%.

    Can you please look into the attached screenshot and verify all other options are correctly chosen ?

    Thursday, May 21, 2015 6:57 AM
  • Hi Abhishek,

    Your settings seem to be correct. I enclose a screenshot of my settings: seems to be similar (just in French...).

    Could you check if the cause of the Publishing issue at 78% is the same: in my case, it was a exception like that: messagetype="Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.SynchronizeTaskListInManagedModeMessage" 

    You can find it in the ULS log, or in the dialog box in Project Pro.

    What you could also do, is to disable the synchro between the Project and the SharePoint Workspace. In the PWA Settings, you can change the SharePoint SIte Provisionning rules:

    PWA Settings / Operationnal Policies / Connected SharePoint sites / Settings/ uncheck the synchronize checkbox.

    After that, maybe you should be able to publish, and continue to investigate in the right direction.

    Please let us know the results,

    Sylvain


    Thursday, May 21, 2015 8:44 AM
  • Hi Christoph,

    You mentioned  'the properties of the task list in the project site', where is it? Could you help to give me more information. I face the same information like Sylvain. 

    thanks a lot!


    Jou Chen

    Monday, September 14, 2015 4:23 PM
  • HI,

    I was facing the same problem,i apply all the above solution but not succeeded at last i save the project plan on local drive then delete the plan from project server and again published the plan on project server now the problem solved.

    Tuesday, September 15, 2015 5:14 AM
  • Hi All,

    I faced same problem, after I run the  patch, projeect SP1, sloved.


    Jou Chen

    Thursday, September 17, 2015 2:20 AM
  • Hi

    I'd have the same problem yesterday, but my project's tasks don't have any resources 

    for solving this issue, first I activated the inactive task again,then added the "publish" column to MSP file, and set the "publish" filed for that task "yes" , and publish the project...

    so Project published correctly  without error

    after that I changed the "publish" filed to "No" for the task and Publish the again ...

    at last inactivated the task again and publish the project ...

    .....................

    If you must inactive a task, first you need to set the "publish"field to "No" and then inactive the task and publish the project without errors...

    good luck

    Mary

    EPM Admin

    Wednesday, January 4, 2017 2:54 PM