Monthly Archives: August 2013

The Project Site already exist – When try to create the Project Site for a Project

Environment: Project Server 2010
Cause: User trying to create the Project site with the name which already exist in the database.
Background: One of our client has deleted the project before creation of new project with the same name and has not selected the option – “Delete the associated Microsoft SharePoint Foundation sites” while deletion.
Solution: Below two possible approaches can be possible as per your customer request:
Approach 1 – Relink the existing project site to the new Project.
Steps as below:
1. Launch Project Web App -> Server Settings -> Project Sites under Operational Policies -> Select the Project


2. Click on the Edit Site Address
3. Mention the existing site URL as per snapshot below and hit OK.


Approach 2 – Create the new Project Site after deleting/renaming the existing Project site with the same name in the database
Steps as below:
1. How to delete the existing Project site
Site Action -> Site Settings -> Sites and Workspaces -> Locate the site to be deleted and click on below cross icon to delete the site


2. How to rename the existing Project Site
Open the project site -> Site Action -> Site Settings -> Title, Description and icon ->
Rename the URL Name and Title and description.
Important: Don’t miss to rename the Project Site URL name otherwise it won’t allow to create the new project site with the same. I would also suggest to rename the “Title and description” for the Project site to avoid the ambiguity in the future.


3. How to create the new Project Site
Launch Project Web App -> Server Settings -> Project Sites under Operational Policies -> Select the Project and click on Create Site.



Now, this will allow you to create the new project site because as per above step2/3, the old project site with the same name doesn’t not exist.

Note: To perform above steps, user needs an administrative privileges. Hope this helps you.




Could Not Retrieve Enterprise Global Template

Environment: Project Server 2010 and MS Project 2010

Background: Users get the below error message when try to connect to Project Server using MS Project.


Possible Causes:
1. The PWA URL set up by user in the MS Project is incorrect.
2. The PWA URL is not added to the trusted sites.
3. Corrupted cache / user profile on the computer having MSP (Project Client) installed.
1. Validate the PWA URL set up in the MS Profile account. For example: It should be ‘https://servername:port/PWA’.
2. Add the PWA URL to browser trusted sites. Steps as below –
Internet Option -> Security -> Trusted Sites -> Site -> Mention the URL and click on Add button -> Ok.
3. Clear the cache files of the user on the computer. Steps as below:
File -> Options -> Select Quick Access Toolbar -> Under Choose commands from select All Commands-> Find and select Cleanup Cache in the list and click Add -> Click OK to exit-> You will now see the cleanup cache button in your quick access toolbar at the top right-> Click the Green icon to open-> You will now see projects that are cached in two ways
• Projects not check out to you
• Projects checkout to you
Select one at a time and click remove from cache -> Close the Project Pro Client and reopen
Note: If you are facing the issue after taking care of above all causes then in that case as per my previous experience you may want to ask the user to re-setup the PWA account in the MS Project/Under file/ Info/Manage Accounts as a workaround.
Let me know if you have come across any other fix for this problem. Thanks.

Error ID: 9133 or 26000 – Project Server 2010

Background: When a user update 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″?>
<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 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=”” />

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.


Fixing of Tasks circulation relationship issue in the project plan resolved the issue.

Way to identify the circular relationship in the project plan

  1. The single most prevalent cause of circular relationships is links on summary lines. I would first turn off automatic calculation and then apply the Summary Tasks filter. If not already present in your view, add the Predecessor and Successor fields. Note which summary lines have links, then apply the All Tasks filter and restructure your file to eliminate summary line links.

I know no 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 analyze changes made to the file thereafter.

  1. Circular Relationship Error When Indenting Task

Refer the link to find the solution –

Note: If in your case, 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.

Hope this helps you.


The WebPart was unable to load

Environment: Project Server 2010

Background: Web Part fail to open on one project in the PDP.


ULS Error Details:


Cause: Project schedule is corrupted.



As a workaround, the user need to recover the corrupted project file as per below steps:

1. Open the corrupted project in MS Project.

2. File, Save As, Save As File.

3. When prompted select to save with “All Enterprise Custom Fields”.

4. In the file dialog select the Save as type: XML


5. Save the file to your local computer.

6. Once saved, close the project (don’t forget to check in!) and reopen the saved XML file, when prompted choose to import ‘As a new project’.

7. Once opened, select Save As and save the project to the project server using the exact same project name.

8. When prompted say yes to overwrite the existing project (you did check it in right?)

9. Publish and you’re done.

10. Check the project in the PWA.

Note: This process will overwrite any previously saved data for that project, the impacts of this are as follows;
• In-progress timesheets will be affected and remember that internally all tasks and assignments are recreated so existing OPEN timesheet periods will be updated. This may result in un-submitted timesheets losing actual work, or worse in progress timesheets failing to submit.

Refer the following link to find out other options to recover the corrupted Project using the Microsoft Project Professional –

Alternatively, user can restore the schedule to the previous day’s version if daily Administrative backup is configured. In theory, the user should only ever lose maximum of one day’s work on the schedule. Refer the following link to restore the previous version project plan –