EPMFAQ
Project Server Help, FAQs, Blogs, and HowTos
This is The Header Then

Are you recieving a ReportingWssSyncListFailed error after modifying a Project Workspace or deploying a customized Project Workspace Template?

posted January 13th, 2008 by Stephen Sanderlin
1 Star2 Stars3 Stars4 Stars5 Stars (3 votes, average: 4.33 out of 5)
Loading ... Loading ...

A few of our clients have reported that after customizing a Project Workspace or deploying a customized Project Workspace, they begin to see Reporting (WSS Sync) errors in their queue:

Queue Errors

When they view the details of this error, they see the following details (duplicate lines removed for your convenience):

Error summary/areas:
Reporting Wss list sync failed
ReportingWssSyncListFailed
Reporting message processor failed
ReportingWSSSyncMessageFailed
Queue
GeneralQueueJobFailed

Error details:

<errinfo>
<general>
<class name="Reporting Wss list sync failed">
<error id="24018" name="ReportingWssSyncListFailed" uid="7e7fa8da-24d4-4c4d-a9ab-c32ed46e205c" SPListType="1100" Error="Failed to prepare the transfer of SP list 1100 for project ‘89ec6841-1f56-46b1-b97b-d775f0ca7e06′. The field Category was missing from the SP list and was ignored." />
</class>
<class name="Reporting message processor failed">
<error id="24016" name="ReportingWSSSyncMessageFailed" uid="79d63cef-5a83-46b1-bc6c-c0124311b60f" QueueMessageBody="ProjectUID=’89ec6841-1f56-46b1-b97b-d775f0ca7e06′. ForceFullSync=’False’" Error="RDS failed while trying to sync one or more SP lists. The RDS queue message will be retried." />
</class>
<class name="Queue">
<error id="26000" name="GeneralQueueJobFailed" uid="b04b7077-731c-4149-87ac-89af07377229" JobUID="ba088e4e-781a-4bc4-b787-3e24ac2849ec" ComputerName="EPM2007DEMO" GroupType="ReportingWSSSync" MessageType="WSSSyncMessageEx" MessageId="1" Stage="" />
</class>
</general>
</errinfo>

This error is pretty clear… Project Server 2007 was trying to import data from a Project’s Workspace into the Reporting Database. Unfortunately, when it gets to List 1100, it didn’t find the Category field, so it ignores it.

But which list in the Project’s Workspace is SP List 1100? Here’s your answer:

SP List ID SP List Name
1100 Issues
1101 Risks
1104 Deliverables

So, how do we avoid this whole problem in the first place? Quite simply, don’t delete any of the default fields in these lists. From my testing, you can rename any field and everything will be okay… but deleting any of the default fields will result in the errors described above. If you want to customize these lists but don’t want all of the fields, just remove them from all of your views. Just keep in mind that not using these fields for their intended purpose means that they won’t be in the Reporting Database, nor will they show up in the Data Analysis views.

Happy customizing!


Stephen Sanderlin is Vice President of Technology for MSProjectExperts and a Microsoft Project MVP. His earlier writings on Project Management and Microsoft Project can be read at EPMFAQ.
He is actively posting new content at ProjectServerHelp.

Popularity: 32%




Discuss this post on the EPMFAQ Blog Posts Forum.


Related Posts



« Previous Entry Next Entry »

Please discuss this post on the EPMFAQ Blog Posts Forum.

2 Responses to “Are you recieving a ReportingWssSyncListFailed error after modifying a Project Workspace or deploying a customized Project Workspace Template?”


  1. […] Are you recieving a ReportingWssSyncListFailed error after modifying a Project Workspace or deployin… […]


  2. […] Force checking on queue Favor revisa esta p?gina http://www.epmfaq.com/ssanderlin/pro…space-template "Luis Esteban Valencia" wrote: > Error details here: > > ?reas o resumen de […]


The opinions expressed on this site by the authors and those providing comments are theirs alone, and do not reflect the opinions of the respective employers of the authors or any employee thereof. Our respective employers are not responsible for the accuracy of any of the information supplied by on this site.

Terms of Use | Privacy Policy | Publishers

All content on this website is covered by the
Creative Commons Attribution-Share Alike 3.0 United States License.
Theme ©2007 The Heckerped WordPress Theme created by JTk of Doc5 under the Creative Commons Attribution License.