The Solution to Error ID: 9133 or 26000 – Project Server 2010

Posted By Posted by: EPM Partners on September 3, 2013

Background: When a user updates the project using the PWA, the below error message will be received via email:

Your Project Update job failed.  Its current state is failed.  It was 50% complete.  It entered the queue Error ID: 9133 Error ID: 26000

Detailed error below – send it to the administrator for more detailed troubleshooting.

<?xml version=”1.0″ encoding=”utf-16″?> <errinfo> <general> <class name=”Project”> <error id=”9133″ name=”ProjectSchedulingEngineException” uid=”406b1860-4ca7-49ed-ae5c-1befa88569c5″ exception=”Microsoft.Office.Project.Scheduling.SchedulingCycleException: Cycle detected.    at Microsoft.Office.Project.Server.BusinessLayer.ProjectSchedule.Schedule()    at Microsoft.Office.Project.Server.BusinessLayer.ProjectMain.HandleProject(ProjectDataSet dataset, Guid projectUid, Boolean fSkipSchedulingCalc, Guid userUid, String userName, Boolean isNew, Boolean addColumns, ProjectLocks projectLock, Boolean fCheckReadOnly, Boolean fCheckProtectedActuals, Boolean fAllowAddEntRes, Boolean fOptIndexRecalced, Guid templateUid, Boolean fSkipCfFormulaCalc) Item = b07fb83c-a1f0-4a31-be39-c6d6ae028be7, Link = 00000000-0000-0000-0000-000000000000″ /> </class> <class name=”Queue”> <error id=”26000″ name=”GeneralQueueJobFailed” uid=”0895224c-0676-45e9-8157-98918704973d” JobUID=”db6df25a-d4c1-4631-b7a1-2e7aae9f5c16″ ComputerName=”HSTSP99″ GroupType=”ProjectUpdate” MessageType=”ProjectUpdateMessage” MessageId=”2″ Stage=”” /> </class> </general> </errinfo>

You can do the following:

1. Try troubleshooting using the error IDs, error XML.

2. Contact administrator with your jobID (db6df25a-d4c1-4631-b7a1-2e7aae9f5c16) and error XML.

Environment: Project Server 2010

Cause: Confliction in Schedule due to circular relationship.

Solution:

Fixing the tasks circulation relationship issue in the project plan resolved the issue.

Ways to Identify the Circular Relationship in the Project Plan

The single most prevalent cause of circular relationships is links on the summary lines:

  1. I would first turn off automatic calculation and then apply the Summary Tasks filter.
  2. If not already present in your view, add the Predecessor and Successor fields.
  3. Note which summary lines have links, then apply the All Tasks filter and restructure your file to eliminate summary line links.

I don’t know a tool to help find circular relationships other than a thorough review of the link structure. If possible, try and isolate various parts of the file by selectively deleting groups of tasks until you find a group that has the problem. Obviously you only want to do this on a copy of the live file. Also, see if you can go back to a previous version of the file before you experienced circular relationship issues. Then analyse changes made to the file thereafter.

  1. Circular Relationship Error When Indenting Task

Refer the link to find the solution – http://support.microsoft.com/kb/176293

Note: If in your case, the user is able to update the plan via MS Project but not from the PWA then I would strongly recommend to check the ULS logs for further information on this error.

We hope this helps you.


Blog Posted In Blog Posted In: Project Server
Blog Posted In 

Leave a Reply

Your email address will not be published.