PS2007 reporting: Violation of PRIMARY KEY constraint 'PK_MSP_EpmT

P

Pawel

Hi,

I have a serious problem with publishing projects into the Reporting
database (which in turn disallows any serious Data Analysis).
I searched the Internet for a solution or a hint where I do somethjing
wrong, but in vain. On this very discussion group I found 3 entries of the
same kind but no replies. Maybe now someone will be able to help. Please?

I have a couple of projects using a number (6) enterprise fields, attached
mainly to to tasks (plus one to the project and one to a resource).
All of these fields are texts, required and mapped from dedicated lookup
tables.

Seemingly everything is fine - project managers can alter their projects,
assign enterprise field values, save and publish projects. The team members
can report their time etc.

Unfortunately, looking at the queue management, the "Reporting (Project
Publish)" tasks get the sleeping status and after a number of re-tries get
into the "Failed But Not Blocking Correlation".

The details of the error message (from the queue management report) are
pasted below. The PK_MSP_EpmTask violation message totally escapes me. Why
would anything like that happen if noone fiddled around the DB structure nor
the PS code?

I suspect (after reading a couple of hits on this forum) that there must be
some kind of de-synchronization between the Enterprise Customn Fields defined
in the main PS databases and the reporting structure. I tired to apply a
scenario to rename all the fields (to have them refreshed in the reporting
DB), but that did not help. I now have no idea either where to look for the
problem nor how to fix it...

Thanks in advance,

Pawel

*** ERROR REPORT: ***
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="4ccf10a9-a54f-4e0c-8984-8264381fbcb9" QueueMessageBody="Project
UID='c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'. 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="228b0d46-5f3c-40b0-ab8f-2678b4dac77f" QueueMessageBody="Project
UID='c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'. PublishType='ProjectPublish'"
Error="One or more custom field metadata mismatch were detected while
transfering project 'c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'" />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="d7a241be-310e-4a22-840a-2e20a6d86763" QueueMessageBody="Project
UID='c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'. PublishType='ProjectPublish'"
Error="One or more custom field metadata mismatch were detected while
transfering project 'c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'" />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="065c0560-680b-4446-a0cd-976fb454f45e" QueueMessageBody="Project
UID='c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'. PublishType='ProjectPublish'"
Error="One or more custom field metadata mismatch were detected while
transfering project 'c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'" />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="0e3110c5-bd69-4a83-a817-dbb0500f16e1" QueueMessageBody="Project
UID='c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'. PublishType='ProjectPublish'"
Error="One or more custom field metadata mismatch were detected while
transfering project 'c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'" />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="b3b2fb2a-9e21-4b60-b62f-327ed52b39fb" QueueMessageBody="Project
UID='c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'. PublishType='ProjectPublish'"
Error="One or more custom field metadata mismatch were detected while
transfering project 'c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'" />
</class>
<class name="Queue">
<error id="26000" name="GeneralQueueJobFailed"
uid="b0138767-9987-422a-a432-92a750864911"
JobUID="4aee5bb3-167e-4429-b33c-2e2f3c94f984" ComputerName="ROBOT2"
GroupType="ReportingProjectPublish"
MessageType="ReportProjectPublishMessageEx" MessageId="1" Stage="" />
</class>
</general>
</errinfo>
 
S

Sharry Heberer [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.
 
R

Rashwan

I've got a similar problem with the "Violation of Primary Key..."
but... instead of the error:
"One or more custom field metadata mismatch were detected while
transfering project 'c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'"

I recieve this:
"Conversion failed when converting from a character string to
uniqueidentifier"

I can't seem to find an answer anywhere or even a similar problem on any
post (or google for that matter) that could give me a hint where to look for
an answer.

I would be grateful for any help.
Thanks,

M.R.
 
T

Ty

Sharry,

I have a slightly different error but along the same line, instead of the
error stating "duplicate" key I get the following;

Error="The INSERT statement conflicted with the FOREIGN KEY constraint
"FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID". The conflict occurred in
database "PWA_Reporting", table "dbo.MSP_EpmTask".
The statement has been terminated"

This happens to only one of our project plans and during the publish
although any changes you make to the plan then save and publish do show
within the plan.

Any ideas ?

Thanks Ty
 
J

JesseR

I am having the same issue Pawel is having. The steps you gave are not
changes but more of looking for errors. I have tried republishing the
projects as you stated but still yield the same problem.
 
G

GM

Hi Sharry,

I have exactly the same error but I don't seem have any issue with custom
fields and lookup table syn. All my jobs for these two job types have been
executed successfully.

Are there any further hint on this topic?

Thanks so much!!!

GM.
 
G

GM

Hi Sharry,

I have exactly the same error but I don't seem have any issue with custom
fields and lookup table syn. All my jobs for these two job types have been
executed successfully.

Are there any further hint on this topic?

Thanks so much!!!

GM.
 
B

B ReynoldsFFIC

I have tried this, but all my Reporting Jobs are OKAY, and when I republish I
get the same errors.

This is the error I am receving on a number of my projects at the "Reporting
(Project Publish):
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="3a079247-6b9c-47a1-95ac-ad4560975805" QueueMessageBody="Project
UID='49acdb6c-ec37-4d1f-8d9a-daba0d74a21d'. 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="2caf6478-fe0a-42ee-8cf6-b5ec07b6559f" QueueMessageBody="Project
UID='49acdb6c-ec37-4d1f-8d9a-daba0d74a21d'. PublishType='ProjectPublish'"
Error="Cannot transfer project : '49acdb6c-ec37-4d1f-8d9a-daba0d74a21d'. A FK
constraint was thrown." />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="47791a1c-0112-48bd-b536-18e167c59217" QueueMessageBody="Project
UID='49acdb6c-ec37-4d1f-8d9a-daba0d74a21d'. PublishType='ProjectPublish'"
Error="Cannot transfer project : '49acdb6c-ec37-4d1f-8d9a-daba0d74a21d'. A FK
constraint was thrown." />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="95cc50cd-a7fb-480a-85b9-70f8a5066809" QueueMessageBody="Project
UID='49acdb6c-ec37-4d1f-8d9a-daba0d74a21d'. PublishType='ProjectPublish'"
Error="Cannot transfer project : '49acdb6c-ec37-4d1f-8d9a-daba0d74a21d'. A FK
constraint was thrown." />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="e0c04545-eb2a-40dc-a821-9f18a2deb958" QueueMessageBody="Project
UID='49acdb6c-ec37-4d1f-8d9a-daba0d74a21d'. PublishType='ProjectPublish'"
Error="Cannot transfer project : '49acdb6c-ec37-4d1f-8d9a-daba0d74a21d'. A FK
constraint was thrown." />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="c486df5e-320f-4b96-a923-7e22eeff9142" QueueMessageBody="Project
UID='49acdb6c-ec37-4d1f-8d9a-daba0d74a21d'. PublishType='ProjectPublish'"
Error="Cannot transfer project : '49acdb6c-ec37-4d1f-8d9a-daba0d74a21d'. A FK
constraint was thrown." />
</class>
<class name="Queue">
<error id="26000" name="GeneralQueueJobFailed"
uid="0414a413-8112-4238-abc2-2a5bdfd7fcbc"
JobUID="bb3f1ebd-7f52-4b18-83a5-efe544174c90" ComputerName="C352"
GroupType="ReportingProjectPublish"
MessageType="ReportProjectPublishMessageEx" MessageId="1" Stage="" />
</class>
</general>
</errinfo>

and
 
W

Wijgert IJlst

Hello,

We are experiencing the same kind of problems you state with several or our
projects aswell. We are still waiting for an implementation of SP1 by our IT
department, so can't confirm this would fix it.

Here is a part of the string we get on one of the failing project we intent
to publish to the reporting database:
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="b0f26439-385b-4529-ac3f-e3c5edc1afde" QueueMessageBody="Project
UID='bfd73c23-3d2b-4149-8b92-30d77f8f96bb'. PublishType='ProjectPublish'"
Error="Cannot transfer project : 'bfd73c23-3d2b-4149-8b92-30d77f8f96bb'. A FK
constraint was thrown." />

Have you found out how to fix or resolve these kind of problems? This is a
big problem as our projects have got Actual Work hours within the
project-files, but in the published database these hours keep on growing and
in the reporting database this proces has come to a standstill... so making
reports with Data Analysis seems to be worthless now.

Hope you know how to help us.

Kind Regards,
Wijgert IJlst
 
R

Ray

Hi for everyone, I need help, this is my error, the difference is not about
Project publish error is when i try to save chenges to my resources.

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

<?xml version="1.0" encoding="utf-16"?>
<errinfo>
<general>
<class name="Reporting message processor failed">
<error id="24008" name="ReportingResourceChangeMessageFailed"
uid="f6a96ffc-d1be-41ce-a412-f0f4dc9cff8e" QueueMessageBody="Resource UID:
'e0e30cfc-2eaf-419d-aa8c-48fff5928d79'. ChangeType='Alter'.
ResourceChangeType='All'" Error="One or more custom field metadata mismatch
were detected while transfering resource
'e0e30cfc-2eaf-419d-aa8c-48fff5928d79'" />
<error id="24008" name="ReportingResourceChangeMessageFailed"
uid="850dc12a-824a-44f7-8159-bfdeb792d45b" QueueMessageBody="Resource UID:
'e0e30cfc-2eaf-419d-aa8c-48fff5928d79'. ChangeType='Alter'.
ResourceChangeType='All'" Error="One or more custom field metadata mismatch
were detected while transfering resource
'e0e30cfc-2eaf-419d-aa8c-48fff5928d79'" />
<error id="24008" name="ReportingResourceChangeMessageFailed"
uid="3bb1ae06-47d8-4904-9240-6d5238ac7d2a" QueueMessageBody="Resource UID:
'e0e30cfc-2eaf-419d-aa8c-48fff5928d79'. ChangeType='Alter'.
ResourceChangeType='All'" Error="One or more custom field metadata mismatch
were detected while transfering resource
'e0e30cfc-2eaf-419d-aa8c-48fff5928d79'" />
<error id="24008" name="ReportingResourceChangeMessageFailed"
uid="957b44e7-8b42-4dbc-aa8b-d910da93c0ff" QueueMessageBody="Resource UID:
'e0e30cfc-2eaf-419d-aa8c-48fff5928d79'. ChangeType='Alter'.
ResourceChangeType='All'" Error="One or more custom field metadata mismatch
were detected while transfering resource
'e0e30cfc-2eaf-419d-aa8c-48fff5928d79'" />
<error id="24008" name="ReportingResourceChangeMessageFailed"
uid="376f9339-3362-4bd1-8229-2a0313993be1" QueueMessageBody="Resource UID:
'e0e30cfc-2eaf-419d-aa8c-48fff5928d79'. ChangeType='Alter'.
ResourceChangeType='All'" Error="One or more custom field metadata mismatch
were detected while transfering resource
'e0e30cfc-2eaf-419d-aa8c-48fff5928d79'" />
<error id="24008" name="ReportingResourceChangeMessageFailed"
uid="6dfb60cb-1a94-41d7-8c50-da265fb03a7a" QueueMessageBody="Resource UID:
'e0e30cfc-2eaf-419d-aa8c-48fff5928d79'. ChangeType='Alter'.
ResourceChangeType='All'" Error="One or more custom field metadata mismatch
were detected while transfering resource
'e0e30cfc-2eaf-419d-aa8c-48fff5928d79'" />
</class>
<class name="Queue">
<error id="26000" name="GeneralQueueJobFailed"
uid="e55e6056-ffa1-4ce5-951b-80e94e3987a7"
JobUID="6e1b4f08-80cb-4491-9000-8dd6de5091d6" ComputerName="DREAMWES"
GroupType="ReportingResourceSync" MessageType="ReportResourceSyncMessageEx"
MessageId="1" Stage="" />
</class>
</general>
</errinfo>
 
B

Brant

Pawel said:
Hi,

I have a serious problem with publishing projects into the Reporting
database (which in turn disallows any serious Data Analysis).
I searched the Internet for a solution or a hint where I do somethjing
wrong, but in vain. On this very discussion group I found 3 entries of the
same kind but no replies. Maybe now someone will be able to help. Please?

I have a couple of projects using a number (6) enterprise fields, attached
mainly to to tasks (plus one to the project and one to a resource).
All of these fields are texts, required and mapped from dedicated lookup
tables.

Seemingly everything is fine - project managers can alter their projects,
assign enterprise field values, save and publish projects. The team members
can report their time etc.

Unfortunately, looking at the queue management, the "Reporting (Project
Publish)" tasks get the sleeping status and after a number of re-tries get
into the "Failed But Not Blocking Correlation".

The details of the error message (from the queue management report) are
pasted below. The PK_MSP_EpmTask violation message totally escapes me. Why
would anything like that happen if noone fiddled around the DB structure nor
the PS code?

I suspect (after reading a couple of hits on this forum) that there must be
some kind of de-synchronization between the Enterprise Customn Fields defined
in the main PS databases and the reporting structure. I tired to apply a
scenario to rename all the fields (to have them refreshed in the reporting
DB), but that did not help. I now have no idea either where to look for the
problem nor how to fix it...

Thanks in advance,

Pawel

*** ERROR REPORT: ***
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="4ccf10a9-a54f-4e0c-8984-8264381fbcb9" QueueMessageBody="Project
UID='c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'. 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="228b0d46-5f3c-40b0-ab8f-2678b4dac77f" QueueMessageBody="Project
UID='c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'. PublishType='ProjectPublish'"
Error="One or more custom field metadata mismatch were detected while
transfering project 'c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'" />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="d7a241be-310e-4a22-840a-2e20a6d86763" QueueMessageBody="Project
UID='c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'. PublishType='ProjectPublish'"
Error="One or more custom field metadata mismatch were detected while
transfering project 'c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'" />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="065c0560-680b-4446-a0cd-976fb454f45e" QueueMessageBody="Project
UID='c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'. PublishType='ProjectPublish'"
Error="One or more custom field metadata mismatch were detected while
transfering project 'c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'" />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="0e3110c5-bd69-4a83-a817-dbb0500f16e1" QueueMessageBody="Project
UID='c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'. PublishType='ProjectPublish'"
Error="One or more custom field metadata mismatch were detected while
transfering project 'c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'" />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="b3b2fb2a-9e21-4b60-b62f-327ed52b39fb" QueueMessageBody="Project
UID='c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'. PublishType='ProjectPublish'"
Error="One or more custom field metadata mismatch were detected while
transfering project 'c8065bd6-5fed-4aa1-b8a2-4d1c5e80e974'" />
</class>
<class name="Queue">
<error id="26000" name="GeneralQueueJobFailed"
uid="b0138767-9987-422a-a432-92a750864911"
JobUID="4aee5bb3-167e-4429-b33c-2e2f3c94f984" ComputerName="ROBOT2"
GroupType="ReportingProjectPublish"
MessageType="ReportProjectPublishMessageEx" MessageId="1" Stage="" />
</class>
</general>
</errinfo>
Click to expand...
 
B

Brant

Sharry,
I was able to identify the enterprise custom fields causing this
problem for me. However, I keep getting a failure every time I try to add any
custom field. When I removed the custom fields causing the problem I could
publish projects again but I cannot seem to get rid of this error when trying
to add a custom field.

<error id="24002" name="ReportingCustomFieldMetadataChangeMessageFailed"
uid="6f71b469-19a2-4a95-93d9-b5ff1a8eae8b"
QueueMessageBody="CustomFieldTypeUID='6225f795-05bf-4ef5-9cc6-101b759e700f'.
ChangeType='Alter'" Error="Unable to add the custom field: 'New Project
Field'. MSP_Epm_AddCustomField failed." />
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Project Failing in the Reporting(Project Publish) Step 0
Error=Cannot transfer project, A FK constraint was thrown 3
Project Fails in the "Reporting(Project Publish) Step 2
Projects not finishing the publish process. 1
Reporting (Project Publish) -- Error 1
Project 2007 Publishing Fails: Report Job, Failed But Not Blocking 1
Master Project Publishing Error + Alerts†1
Project Plan Publishing Error 26000 1

Top