I’ve been battling a project publishing issue for a couple of months now and I’m desperately in need of help! I’ve seen very similar issue in 2010 while researching for a resolution.
Initially in our first step, we had identified the resources who were causing errors in the ULS logs and deleted those records when we failed to publish a project schedule.
E.g. Level: Product: Project Server, Category: Project Server & Level: Unexpected
Message from ULS Log:
Node Consistency Message: Exception Recreating Server Level Summary Resource Assignment. ResUid=bc1fe81c-1558-e311-93f7-005056a212ba
Node Consistency Message: Error Updating Summary Resource Assignment. ProjUid=c0cf864b-8200-e411-93fc-005056a212ba, ResUid=625cf762-599e-e311-93f9-005056a212ba
We ran a query to delete the associated resource (ResUID)
WHERE RES_UID = ‘####################################’
Two types of messages that directly relate when a project fail to publish. This still did not resolve the publishing issue as more resources were identified as “corrupted” SRA records.
Finally in our second step, we delete all SRA records, knowing that they would be recreated when a project schedule publishes. This has helped some project schedule to publish more successfully but there are a small handful that continue to fail even though the SRA records were deleted.
ProjectPublishFailure (23000). Details: id=’23000′ name=’ProjectPublishFailure’ uid=’c5f3ccc8-500a-e511-9408-005056a212ba’ projectuid=’f57a6790-3ab4-e311-93fa-005056a212ba’ messagetype=’Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.UpdateSRAMessage: projectUid = f57a6790-3ab4-e311-93fa-005056a212ba’ messageID=’33’ stage=” blocking=’Block’.
GeneralQueueJobFailed (26000) – ProjectPublish.UpdateSRAMessage. Details: id=’26000′ name=’GeneralQueueJobFailed’ uid=’c6f3ccc8-500a-e511-9408-005056a212ba’ JobUID=’5da84ab8-500a-e511-953c-a4db3022301d’ ComputerName=’24871cfb-c910-4046-8964-595d7868d55c’ GroupType=’ProjectPublish’ MessageType=’UpdateSRAMessage’ MessageId=’33’ Stage=” CorrelationUID=’5ae20c9d-bb12-d007-8d55-c1dcf2cb0765′. For more details, check the ULS logs on machine 24871cfb-c910-4046-8964-595d7868d55c for entries with JobUID 5da84ab8-500a-e511-953c-a4db3022301d.
Question: What can I do to resolve this publishing issue?
Thank you, any recommendations or advice is greatly appreciated. Project Server 2013 – September 2014 CU
Paul, difficult question for this forum. You seem like you’ve done a lot of research already with no success. If you don’t get an answer here I might suggest:
1. Post it one of the TechNet project forums: https://social.technet.microsoft.com/Forums/projectserver/en-US/home?category=project. Maybe the Project Server – Setup, Upgrade, Administration and Operation forum.
2. Submit help from Microsoft