Project - Failed but not blocking correlation

[Venu]

We are on MSPS 2007 + SP1. One of the users projects creates this error
repeatedly. It is not the same project each time but a different one. The
only solution thus far is to dump the old project and recreate a new one with
a different name. This is frustrating to the users and for us to
troubleshoot. Any help on how to resolve this issue. Why is it happening on
one project plan and not everyone elses. There are 100 other project plans
that dont have a problem like this. What are we doing wrong. Any thoughts?


Error summary/areas:
Reporting message processor failed
ReportingProjectChangeMessageFailed
ReportingProjectChangeMessageFailed
ReportingProjectChangeMessageFailed
ReportingProjectChangeMessageFailed
ReportingProjectChangeMessageFailed
ReportingProjectChangeMessageFailed
Queue
GeneralQueueJobFailed
Error details:

<?xml version="1.0" encoding="utf-16"?>
<errinfo>
<general>
<class name="Reporting message processor failed">
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="0bd2db88-62ae-410d-8afa-25407855c6e6" QueueMessageBody="Project
UID='b477fee5-530d-441e-b837-40fc246f721c'. PublishType='ProjectPublish'"
Error="Violation of PRIMARY KEY constraint 'PK_MSP_EpmTask'. Cannot insert
duplicate key in object 'dbo.MSP_EpmTask'.
The statement has been terminated." />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="5781eef5-d301-4798-a09b-c529eb6dfa38" QueueMessageBody="Project
UID='b477fee5-530d-441e-b837-40fc246f721c'. PublishType='ProjectPublish'"
Error="Object reference not set to an instance of an object." />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="48c8c59e-8e55-471b-b675-cb52257dce08" QueueMessageBody="Project
UID='b477fee5-530d-441e-b837-40fc246f721c'. PublishType='ProjectPublish'"
Error="Object reference not set to an instance of an object." />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="eb6e56dc-a473-404e-b1e6-24845c33c12d" QueueMessageBody="Project
UID='b477fee5-530d-441e-b837-40fc246f721c'. PublishType='ProjectPublish'"
Error="Object reference not set to an instance of an object." />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="bc19cc00-975a-4a3e-a549-672c65a07e1c" QueueMessageBody="Project
UID='b477fee5-530d-441e-b837-40fc246f721c'. PublishType='ProjectPublish'"
Error="Object reference not set to an instance of an object." />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="cdf6b974-18c7-4728-a5bf-d76e1cd651f6" QueueMessageBody="Project
UID='b477fee5-530d-441e-b837-40fc246f721c'. PublishType='ProjectPublish'"
Error="Object reference not set to an instance of an object." />
</class>
<class name="Queue">
<error id="26000" name="GeneralQueueJobFailed"
uid="ce8267bb-e445-47dc-adb2-82df27691500"
JobUID="1bd5d2e8-3764-4953-993b-645e7b9e3f97" ComputerName="RTPROJECT2"
GroupType="ReportingProjectPublish"
MessageType="ReportProjectPublishMessageEx" MessageId="1" Stage="" />
</class>
</general>
</errinfo>

 

[Paul Conroy]

Previous response from Barry (MSFT)
The first step is to find out which custom field(s) is causing the problem.
Please follow these steps:
1. Change the Job History section on your Manage Queue page and set the
"From" date to more than 1 week ago (leave the "To" date as the current
date).
2. Change the Job Types to include only "Reporting (Custom Field Metadata
Sync)" and "Reporting (Lookup Table Sync)."
3. Hit the Refresh Status button on the Manage Queue grid.

If NONE of the jobs are in the Failed states (either Failed Blocking or
Failed Not Blocking) or Canceled state, Go to the "Ready To Publish" section
below.

If any of these jobs are in the Failed states (either Failed Blocking or
Failed Not Blocking) or Canceled state, those are the custom fields with the
problem - follow these steps before continuing:
1. Note the field down that have the problem.
2. Go to the Custom Field page and try to edit something about these fields
(something as simple as adding a character to the name, which you can remove
later) so they will sync again to the Reporting Databse.
3. Check your Queue again and make sure ALL of these jobs have completed
successfully.

If they did not all complete successfully, look at the error and then post
back with what it says. (do not proceed to "Ready To Publish" because it
will just fail again)

If they all completed successfully, then do the "Ready To Publish" steps
below:

Ready To Publish
1. Publish your project(s) once and wait until the Reporting Project Publish
job has completed (the reporting publish might fail again this first time)
2. Publish them again if they did fail the first time. This *should* fix
the problem if you have followed all the steps correctly.

Please let me know if you have any questions about this process, or if I
haven't covered an issue that you are seeing along the way.

 

[Donna]

Have you tried saving the file locally and reimporting?
We've also gotten some strange errors if there were local resources that
didn't make sense or had same name as an enterprise. We fixed these issues
- but still had to export
We've done that on a few projects - seems to clear up whatever got stuck.
Use the same name - that way you can keep workspaces, etc and reporting
hours in tacts.
Can't explain why - which doesn't help , but it clears up things for the user.

Donna

 

[Venu]

Paul,

I need a little more help. How do I identify which field is causing this
problem.

Your wrote in the trouble shooting steps: If any of these jobs are in the
Failed states (either Failed Blocking or Failed Not Blocking) or Canceled
state, those are the custom fields with the problem - --


Where exactly do I look in the Queue details message to identify the CUSTOM
FIELD that has the problem. Thanks for your help.
Thanks
V