Reporting (WSS Sync) Error

[Anum_10]

Receiving the following error as we added new issues and changed some of the
old tasks/issues in PWA.

Reporting Wss list sync failed
ReportingWssTransferLinksFailed
ReportingWSSSyncMessageFailed
ReportingWssSyncHRefFailed
Queue
GeneralQueueJobFailed

What could be causing this error? How can we resolve this?

Any assistance would be greatly appreciated. Thanks!

 

[Anum_10]

Receiving the following error as we added new issues and changed some of the
old tasks/issues in PWA.

Reporting Wss list sync failed
ReportingWssTransferLinksFailed
ReportingWSSSyncMessageFailed
ReportingWssSyncHRefFailed
Queue
GeneralQueueJobFailed

What could be causing this error? How can we resolve this?

Any assistance would be greatly appreciated. Thanks!

The errors returned from the queue are as follows:
Error ID: 24018
Error ID: 24019
Error ID: 24016
Error ID: 24021
Error ID: 26000

 

[paul conroy]

The errors relate to the fact the you've changed/deleted some of the default
risks/issues/deliverables. PS is expecting certain columns and data types
during the sync. The SDK details exactly what you can change. To get rif of
these errors you should restore the orginal columns for
risk/issues/deliverables.

 

[Anum_10]

Thank you so much for your prompt response!

Where can I find SDK detailing exactly what can and cannot be changed?

In addition, can you please advise on how I can restore the original columns
for risk/issues/deliverables?

Thanks,
Saima.

 

[paul conroy]

I've not got the link to hand, search for Project 2007 SDK download in any
search engine.

Restore the original columns is a manual process (unless you recreate the
sites). To find the original column names and data types create a site from
the original site template and note down the list details.

 

[Gary L. Chefetz]

Anum:

The original version of the Project Workspace Template should be on your
system unless you deleted it.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[Anum_10]

Thank you Paul. I restored the original columns as they were and it worked.

 

[meganw]

We are having the same issue, and have customized our Sharepoint Template and
have not deleted any of these fields. We are having an additional issue
whereby we have developed a custom report and the sharepoint issues and risks
fields take days to pull through - and this is not due to performance issues.
We have to spent a lot of money with our support provider now to develop a
utility to help us identify which fields are in fact giving these issues so
that we can review and fix. Microsoft should seriously look into this issue
and provide a resolution please.

Thanks

 

[Gary L. Chefetz]

Megan:

In order to have the same issue as this thread, you would have had to have
altered something in the WSS list to cause the error. Perhaps you didn't
delete a field, but maybe you changed an expected value? What do you mean by
"sharepoint issues and risks fields take days to pull through?" I can't
begin to respond to this without understanding your meaning. Thanks.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[meganw]

Hi Gary;
Thanks for the reply. When you make mention of a change to an expected value
- are you referring to a 'standard value' field that we changed on the global
WSS template to something else?
We get a number of WSS failed messages, and are currently testing the
Utility that our 3rd Party Support providers have developed for us to
identify where the fields are in the various WSS's that are giving us
problems. We have embarked on a mission to 'fix' these individual WSS sites,
however this is not solving our problem as we have fixed 1 project specific
WSS site as a test so far and we are still getting WSS failed messages. The
issues and risks are also not pulling through to the Issues and Risks cube
straight away after a successful cube run, as well as through a custom report
that we have developed.
What do you advise?
Thanks so much!

 

[meganw]

Hi Gary;
Thanks for the reply. When you make mention of a change to an expected value
- are you referring to a 'standard value' field that we changed on the global
WSS template to something else?
We get a number of WSS failed messages, and are currently testing the
Utility that our 3rd Party Support providers have developed for us to
identify where the fields are in the various WSS's that are giving us
problems. We have embarked on a mission to 'fix' these individual WSS sites,
however this is not solving our problem as we have fixed 1 project specific
WSS site as a test and we are still getting WSS failed messages. The issues
and risks are also not pulling through to the Issues and Risks cube straight
away after a successful cube run, as well as through a custom report that we
have developed.
What do you advise?
Thanks so much!

 

[meganw]

Hi Gary;
Thanks for the reply. When you make mention of a change to an expected value
- are you referring to a 'standard value' field that we changed on the global
WSS template to something else?
We get a number of WSS failed messages, and are currently testing the
Utility that our 3rd Party Support providers have developed for us to
identify where the fields are in the various WSS's that are giving us
problems. We have embarked on a mission to 'fix' these individual WSS sites,
however this is not solving our problem as we have fixed 1 project specific
WSS site so far as a test and we are still getting WSS failed messages. The
issues and risks are also not pulling through to the Issues and Risks cube
straight away after a successful cube run, as well as through a custom report
that we have developed.
What do you advise?
Thanks so much!

 

[meganw]

Hi Gary;
Thanks for the reply. When you make mention of a change to an expected value
- are you referring to a 'standard value' field that we changed on the global
WSS template to something else?
We get a number of WSS failed messages, and are currently testing the
Utility that our 3rd Party Support providers have developed for us to
identify where the fields are in the various WSS's that are giving us
problems. We have embarked on a mission to 'fix' these individual WSS sites,
however this is not solving our problem as we have fixed 1 project specific
WSS site so far as a test and we are still getting WSS failed messages. The
issues and risks are also not pulling through to the Issues and Risks cube
straight away after a successful cube run, as well as through a custom report
that we have developed.
What do you advise?
Thanks so much!

 

[Gary L. Chefetz]

Megan:

Yes, I was referring to expected values in the WSS Project Workspace
template. I'm certain that is your problem. New issues and risks do not
appear in the cube until you first publish the project and then build the
cube. Does that help you understand what you're seeing?

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[meganw]

Hi Gary,

I have logged this with Microsoft Support last week, and have sent them my
test results and copy of our database, and it was discovered that this is in
fact a bug in the system, and they will release a fix in the cumulitive
update at the end of Feb/beginning March.

Thanks!
Megan.