Fixing SharePoint Sync Errors in Project Server 2010

Here’s a common issue I am finally getting around to blogging up: certain projects always seem to throw an error on Publish, specifically on the part of the Publish job where the Publish database data is pushed into the Reporting database.  Everything works fine in Project Server, but the Reporting database (RDB) doesn’t refresh.

This issue is almost always caused by somebody messing with key settings in the SharePoint site attached to the project.  You’ll be able to determine if that is the case when you go into the Project Server queue and see something like this:

GeneralQueueJobFailed (26000) – ReportingWSSSync.WSSSyncMessageEx. Details: id=’26000′ name=’GeneralQueueJobFailed’ uid=’dae69759-a3c3-4ac4-a3bf-032022b0dd17′ JobUID=’41f0e5ef-9ca4-4edd-bcf6-f5fca87b3ae8′ ComputerName=’mypc’ GroupType=’ReportingWSSSync’ MessageType=’WSSSyncMessageEx’ MessageId=’1′ Stage=”. For more details, check the ULS logs on machine  myserver for entries with JobUID 41f0e5ef-9ca4-4edd-bcf6-f5fca87b3ae8.

Check the ULS log, and it will tell you exactly what’s wrong with the SharePoint site in question.

PWA:, ServiceApp:Project Web App Service Application, User:myuser, PSI: [RDS] Failed to transfer SP list 1101 associated with project ‘920997d9-050c-4b54-84f2-7d365cbf3449’ to project server reporting database. Error: Microsoft.Office.Project.Reporting.ProjectReportingPublic.ReportException: The field: ‘Category’ on the list for project ‘920997d9-050c-4b54-84f2-7d365cbf3449’ should have type Choice. It was found having a different type (MultiChoice)…

…indicates that someone has changed the default Category field from a single select to a multiselect.

PWA:, ServiceApp:Project Web App Service Application, User:myuser, PSI: [RDS] Failed to transfer SP list 1101 associated with project ‘d32cf50b-8ccf-4405-8251-d26fb59c5d68’ to project server reporting database. Error: Microsoft.Office.Project.Reporting.ProjectReportingPublic.ReportException: Failed to prepare the transfer of SP list 1101 for project ‘d32cf50b-8ccf-4405-8251-d26fb59c5d68’. The field AssignedTo was missing from the SP list and was ignored.

…indicates that someone has deleted the AssignedTo field from the relevant list.  You’ll also be able to determine which list specifically causing the issues, i.e. 1100 equals the Risk list and 1101 correlates to the Issues list.

More Background

As a little background to this discussion, Project Server has certain structures hard coded into the RDB.  Specifically, every time a project is published, a routine hits the Website and pulls a dozen or so specifically named fields from the key Project Server lists and libraries on that site: Deliverables, Issues, Risks and Project Documents.

If a user inadvertently deletes any of those entities – or modifies them in such a way that the RDB can’t find them anymore, an error will be thrown.  If the organization isn’t leveraging the RDB for custom reporting, that’s probably not an issue, as it really doesn’t matter what’s in the RDB.  If the organization is leveraging custom reporting however, this becomes a priority.

Fixing Deleted Lists and Libraries

The first scenario we’ll look at is fixing deleted lists or libraries.  This might happen if the site owner decides “Hey, I don’t need this Issues list.” and simply deletes it.  To fix this, navigate to the site in question, turn off the Project Server feature, and then reenable it.  That reprovisions lists that don’t already exist on the site – but doesn’t seem to impact lists already on the site.


Fixing Deleted or Modified Columns

The second scenario would involve the user modifying or deleting columns.  In this case, simply add a new column with the expected name back to the list in question.  Check a working project site to confirm the correct name for the field – specifically check the URL for the column in a working site to confirm that you’re creating a new column with the appropriate system identifier, and not the alias.

For example, “Assigned To” should be created as “AssignedTo.”  Once the field has been created with the appropriate system name, go back and rename it to something a bit more user friendly, i.e. “Assigned To.”  It will keep the original name, but display as the more user friendly “Assigned To.”

Fixing the Linked Column

The only column that can’t be fixed in this way is the Linked column.  This column captures the links between list items and project tasks. That’s specifically provisioned as part of the list, and can’t simply be added back into the list using the method above.  If there’s no data in the list, go ahead and delete the list and reprovision it using the technique above.

If the user has deleted this column and has data in the list, you’ll have to bring out the big guns.  Here’s the approach that worked for me:

1) Provision a blank team site and add the Project Server Lists feature to this site.  That site will be a parking lot for our data while we fix the list in our source site.

2) In the source site, navigate to Site Settings > Content and Structure.


3) Use the Content and Structure interface to copy the list data to our temporary site.


4) Delete the list in the source site.

5) Reprovision the Project Server list items in the source site (i.e. Site Settings > Site Features > Deactivate and Activate)

6) Use the Content and Structure to copy the data back from our temporary site to the source site.

7) Delete the temporary site to clean up.

Publish the project to refresh the RDB and check the queue to ensure everything processed as it should, and you should be good to go – until the next time an end user deletes a field.  Note that you may have to do this a couple of times on the site, as the ULS logs seem to only catch the first error on a site before failing.  If multiple changes have been made to the site, you may need to review the logs a couple of times to ensure you got everything.

Fixing SharePoint Sync Errors in Project Server 2010

16 thoughts on “Fixing SharePoint Sync Errors in Project Server 2010

  1. Nice article again! How about the error caused by creating additional Issues and Risks lists using the issue tracking template from SharePoint. This will cause a 1100 error, if i remember correctly. The only solution seems to be to “Custom List” template to begin with and then save it as a template to be used for all new issues and risks lists.

  2. Yeah – what’s tricky is that there is a default SharePoint Issues list and a Project Server Issues list – and those are different list types. A common approach is to simply go Create List > Create Issues List, which Project Server won’t recognize. Instead, you have to turn off and back on the Project Server feature to provision the correct Issues list.

  3. Ris says:

    Hi Andrew,

    A very nice and detailed article on SharePoint’s sync errors.

    We are also encountering the same sync errors. Maximum number of pending jobs in the Manage Queue Jobs panel are related to:

    – Reporting (Project Sync)
    – Reporting (Resource Sync)
    – Internal (CBS Timesheet Rendezvous)

    And every job is in the state of “Waiting To Be Processed”.

    After reading this article, I feel that this is because we have also customized few columns (Issue Type, Status, Priority, Category) of Issue lists on 4 different sites.

    Now I plan to act as per the option 2 discussed in this article i.e. creating similar columns and hiding the original ones. But please advise me if we also need to put the values back to the original ones? For example:

    Default Status drop down contains three values: (1) Active, (2) Closed, (3) Postponed
    Whereas after modifying these are 6 different values.

    So do we need to restore the original values of the Status field also?


    1. I don’t think this article pertains to those issues specifically. I’d urge you to check the ULS logs, but off of the top of my head, there may be two potential remedies:
      1) Restart the Project Server queue service on the application server.
      2) Rebuild the reporting database.

      Both procedures are documented online. If the issues addressed in this post were observed, they would be cancelling in the queue, not waiting to be processed.

  4. Andrew says:

    Hello, Andrew!
    I have the same problem with pushing data from published to reporting, but i couldn’t find the same errors in my ULS log. Is it possible to contact with your for a few questions about it?

  5. Josh says:

    This is really helpful. One question though: I created a workflow on a list at the project site template. I’m thinking this messed up my connected Tasks list as the Tasks list is now editable. How can I make it connected to PWA again? Or do I have to start over?

  6. Robert says:

    is there any way to synchronize data on the state of workflow projects from the Publishing database to the Reporting database?

    after performing backup and restore custom fields (administrative backup and restore) disappeared informations about status workflows for projects in the database Reporting

  7. Kathy says:

    Hi Andrew,

    I’m trying to link Risks and Issues. I am able to link to tasks, documents and the current list im in: Issues or Risks. However, I get an error whenever I try to link across Issues and Risks in particular.

    My error just says an unexpected error has occurred. 😦

    Any guidance is greatly appreciated.

  8. Thanks a lot for great article! It was really helpful in resolving the error for project crashes. but just one correction 1100 is for Issues and 1101 is for Risks.


  9. Hendrik says:

    Hi Andrew, have you encountered the “Link” field issue with the document Library, as the site features option does not recreate the Linked Document Library again, and I’m not sure how to fix that.
    Any Thoughts will be most appreciated.
    Thank You

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s