Category Archives: Issues

Project Server 2010 Error: WorkflowStartWorkflow job failed (35115) (35100) – 26000

Error: Your WorkflowStartWorkflow job failed. Its current state is FailedNotBlocking. It was 0% complete. It entered the queue at 03/07/2013 09:35:57.

To get more information about the job failure, please go to Project Web App. Select Personal Settings from the left menu. Then select My Queued Jobs.

The errors returned from the queue are as follows:
Error ID: 35115
Error ID: 35100
Error ID: 26000

Solution:

You have to go into Central Admin, to verify that workflow is enabled. Below steps helps you to enable the Microsoft SharePoint Foundation Workflow Timer Service in Central Administrator:

1. Open the Central Administrator page on Application server.

2. Click on Manage Services on Server under System Settings section on Central Admin default page

manageServices

3. Make sure you start the below service, this will fix the issue.

services on server

Good Luck!

Project Server 2010 Queue Error: WSSCreateSiteFailure (16400) – 26000

Error Description:  Your CreateWssSite job failed.  Its current state is FailedNotBlocking.  It was 0% complete.  It entered the queue at 03/01/2013 13:00:01. To get more information about the job failure, please go to Project Web App.  Select Personal Settings from the left menu.  Then select My Queued Jobs.

The errors returned from the queue are as follows:

Error ID: 16400

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=”CreateWssSiteContent: Creating project site failed! Project Uid=36b1e386-6353-4cac-99b5-5f923c072a93, site URL=http://tsts12:99/PWA/test12, site name=test12. Microsoft.SharePoint.SPException: The site template requires that the Feature {0575f1d6-6c61-4be7-9d01-77aaa8b392a4} be installed in the farm or site collection.

<error id=”16400″ name=”WSSCreateSiteFailure” uid=”16b7a8a4-5bae-405f-9ac1-fe865045aa06″ projectUID=”36b1e386-6353-4cac-99b5-5f923c072a93″ workspaceUrl=”http://tsts12:99/PWA/test12/test12” projectWorkspaceName=”test12″ />

</class>

<class name=”Queue”>

<error id=”26000″ name=”GeneralQueueJobFailed” uid=”ac561a59-f2e5-4d4c-9ccf-33113a2c1b8e” JobUID=”8863c4dd-073e-4940-bec8-e30e7bff9701″ ComputerName=”SNAPPSTST12″ GroupType=”CreateWssSite” MessageType=”CreateWssSiteMessage” MessageId=”1″ Stage=”” />

</class>

</general>

</errinfo>

Solution:

Enable-SPFeature –identity ‘0575f1d6-6c61-4be7-9d01-77aaa8b392a4–URL http://yourservername:PortNumber/PWA.

Please note in above script the identity will be the GUID from the first error message and URL will be the PWA instance where you want this template to work.

Saving an Lookup Table with a large series of values results in ”The Security Validation for this page has timed out” error

Scenario: Attempting to save a large look up table value set in MS EPM 2010.

Cause: The time taken to popluate the large value set exceeds the time available to update the lookup table resulting in a time out error when a save is attempted on the the lookup tables data set.

Error: Timed Out error as per below snapshot:

RBSLookUpTimedOUt

Workaround: To overcome this issue save the look up table in more frequent and shorter intervals after making just a few updates rather than attempting to save all changes at once at the end.Failure to do this will result in the Timed out error and you will lose the data.:(

Error Code (2058): New Project has been created successfully, but failed to publish

Error: Your new <Project Name> has been created successfully, but failed to publish and will not be listed in the Project Center. For more information on the failure, visit the My Queue Jobs page or
contact your administrator.

Queue Error Details:

Datasets: ProjectDataSet Table ProjectResource Row: RES_UID=’ef1d05bf-1aa2-4268-a052-40aa14bfbfd9′ PROJ_UID=’9ef874f5-9b0b-4c8f-90f0-0bcac9e3ea32′ Error rsResourceCannotAddLocalWithSameNameAsEnterprise (2058) – column RES_UID Row: RES_UID=’1489e8bc-1a3f-4f74-8d54-8e2c8371b5e5′ PROJ_UID=’9ef874f5-9b0b-4c8f-90f0-General Queue: GeneralQueueJobFailed (26000) – ProjectCreate.ProjectAddToMessage. Details: id=’26000′ name=’GeneralQueueJobFailed’ uid=’8bd26794-965a-450d-9d52-aec9224dbfc8′ JobUID=’d5e8599f-a259-4f15-abdc-0bcc5dd2b8e8′ ComputerName=’SNAPPSTST12′ GroupType=’ProjectCreate’ MessageType=’ProjectAddToMessage’ MessageId=’1′ Stage=”. For more details, check the ULS logs on machine SNAPPSTST12 for entries with JobUID d5e8599f-a259-4f15-abdc-0bcc5dd2b8e8.

Cause: The project WBS/Schedule template uses Enterprise Resources that have been deleted or converted to Users.

Resolution:

Step 1: Open the Project Template (MPT) in MS Project professional 2010. You will see the below pop up message. It has listed the resources those have been deleted or converted to Users.

Please note, in this case, we are assuming one Project template configured in MS EPM Project Management System. You will need to check all the project templates when using more than one.

bl

Step 2: Now, we have two solutions to resolve this issue for future projects:

Solution 1: You can remove the above resources from the Enterprise Project Template Resource sheet and update the Project Template.

Solution 2: Convert the resources into Local Resources by clicking OK on the dialog box illustrated in above screenshot  and overwrite the existing project template.

Either of the above solution will allow you to Create/Publish the project now and resolve the project creation issue.

Hope this helps you.

Cheers,

Badal

Issue: No Prompt for Document Check In Option in the Project Documents List

Issue: Users don’t get prompted to Check in a document after  closing the document and saving changes to a sharepoint document library.

Reason: By Default, Checked OUT option is disabled in the Project Document Library settings:)

Objective: To enable the Checked Out option in the Project Document list so the user will be prompted to check-in the document when it is saved back to the server.

Solution Steps:

  1. Open the Project Site Template Site Action -> Site Settings -> Sites & Workspaces under Site Administration -> Click on the Project Site Template under Sites
  2. Now, you need to Click on the Project Document list under Libraries on the Quick Launch menu
  3. Click on Library Settings in the group Settings under Library ribbon option
  4. On the Library settings page, click on Versioning Settings under General Settings section
  5. On the Versioning setting page, you need to select the ‘Yes’ radio button in section Require Check out option
  6. Save it as a latest project site template and configure to the Enterprise Project Type (EPT).

Cheers,

Badal

Error: The document could not be checked out from the Project Site

Recently, we faced an issue with a client using the Project Site document library. When the users clicked on a document in the Project Document Library and choose “Check Out and Edit” the Users received the below error message:

Issue: This document could not be checked out. You may not have permission to check out the document or it is already checked out or locked for editing by another user

Cause: User unable to check out the document with office word 2007.

Resolution: In this case checking out the document with Office 2010 has resolved the issue, however I need to do further research to see why this was the case – as normally Office 2007 works without causing such issues. Let me know if any of you have had a similar experience

Removing Corrupted Web Parts from a Project Site/Project Server Web Part Page

Issue: Project Site home page displays closed/Corrupted WebPart on the page after saving as a Project Site Template.

Cause: Web Part Corruption or closed WebParts which has not been deleted on the page.

Solution:  To fix it you need to follow below steps:

1. Click on Site Action then Site Settings.

step1

2. Click on Site and Workspaces under Site Administration section on the Site Setting Page.

step2

3. On Site and Workspaces page, click on your Site Template under section Sites.

4. On Project site landing page, in the address bar Append ?contents=1 in the URL right after .aspx

step3

5. Press <Enter>

6. Project Site template displays the Web Part Page Maintenance page.

7. Select the Web part of which you cannot see when you open the Project Site home page and then click the appropriate function on the toolbar like Delete.

step4

8. Now, you can save project site as a Template, this will remove the unwanted WebPart on the Project site landing page.

Cheers,

Badal