ProjectPublish - ReportingProjectChangeMessageFailed - FOREIGN KEY constraint "FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID"
I often recieve this error message at our customers, 9 out of 10 times it is because the Project Server Reporting database is out of sync with publish database.
The solution is to rebuild the database. See below.
Error message from queue:
- 2013: Central Administration
- 2010: PWA->PWA Settings
Go to
- 2013: Central Administration->General Application Settings->PWA Settings->Manage
- 2010: PWA settings (Server settings in 2010).
Go to Administrative Backup.
Backup all the custom fields.
Go to Administrative Restore.
Restore all the custom fields.
As everything in the reporting database someway has a custom field connected this will cause the whole database to get rebuilded.
Follow the restore in the queue.
The solution is to rebuild the database. See below.
Error message from queue:
• Reporting message processor failed:
o ReportingProjectChangeMessageFailed (24006) - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID".
The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmTask". The statement has been terminated.. Detaljer: id='24006' name='ReportingProjectChangeMessageFailed'
uid='05540895-3c37-41ca-a02b-8572d0d3ab68' QueueMessageBody='Project UID='f12dced7-1d84-47e0-86ee-4049dbd9b1cd'. PublishType='ProjectPublish'' Error='The INSERT statement conflicted with
the FOREIGN KEY constraint "FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmTask". The statement has been
terminated.'.
o ReportingProjectChangeMessageFailed (24006) - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID".
The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmTask". The statement has been terminated.. Detaljer: id='24006' name='ReportingProjectChangeMessageFailed'
uid='5313a512-da56-481d-a9b0-7bf8ebcbf564' QueueMessageBody='Project UID='f12dced7-1d84-47e0-86ee-4049dbd9b1cd'. PublishType='ProjectPublish'' Error='The INSERT statement conflicted with
the FOREIGN KEY constraint "FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmTask". The statement has been
terminated.'.
o ReportingProjectChangeMessageFailed (24006) - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID".
The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmTask". The statement has been terminated.. Detaljer: id='24006' name='ReportingProjectChangeMessageFailed'
uid='b12c9639-f86c-47e3-af28-9b016b5f576a' QueueMessageBody='Project UID='f12dced7-1d84-47e0-86ee-4049dbd9b1cd'. PublishType='ProjectPublish'' Error='The INSERT statement conflicted with
the FOREIGN KEY constraint "FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmTask". The statement has been
terminated.'.
o ReportingProjectChangeMessageFailed (24006) - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID".
The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmTask". The statement has been terminated.. Detaljer: id='24006' name='ReportingProjectChangeMessageFailed'
uid='cc89ca62-5edb-4c8b-b129-1e75e3792ef5' QueueMessageBody='Project UID='f12dced7-1d84-47e0-86ee-4049dbd9b1cd'. PublishType='ProjectPublish'' Error='The INSERT statement conflicted with
the FOREIGN KEY constraint "FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmTask". The statement has been
terminated.'.
o ReportingProjectChangeMessageFailed (24006) - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID".
The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmTask". The statement has been terminated.. Detaljer: id='24006' name='ReportingProjectChangeMessageFailed'
uid='b0519801-3d0b-4405-a10e-de73103e5913' QueueMessageBody='Project UID='f12dced7-1d84-47e0-86ee-4049dbd9b1cd'. PublishType='ProjectPublish'' Error='The INSERT statement conflicted with
the FOREIGN KEY constraint "FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmTask". The statement has been
terminated.'.
o ReportingProjectChangeMessageFailed (24006) - The INSERT statement conflicted with the FOREIGN KEY constraint "FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID".
The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmTask". The statement has been terminated.. Detaljer: id='24006' name='ReportingProjectChangeMessageFailed'
uid='5a1493b2-e725-41e0-b315-42e76309b7a3' QueueMessageBody='Project UID='f12dced7-1d84-47e0-86ee-4049dbd9b1cd'. PublishType='ProjectPublish'' Error='The INSERT statement conflicted with
the FOREIGN KEY constraint "FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_EpmTask". The statement has been
terminated.'.
• Queue:
o GeneralQueueJobFailed (26000) - ReportingProjectPublish.ReportProjectPublishMessageEx. Detaljer: id='26000' name='GeneralQueueJobFailed' uid='4c4a3d86-cdc6-485b-adde-289cb3c563f1'
JobUID='e575ba26-9256-417d-86d8-95280e4f66a4' ComputerName='XXX-XXXXX' GroupType='ReportingProjectPublish' MessageType='ReportProjectPublishMessageEx' MessageId='1' Stage=''.
Der er flere oplysninger i ULS-logfilerne på computeren XXX-XXXXXXX for poster med Job-UID e575ba26-9256-417d-86d8-95280e4f66a4.
Solution
Log in to the adminstration area for the PWA with Project Server administrator permission.- 2013: Central Administration
- 2010: PWA->PWA Settings
Go to
- 2013: Central Administration->General Application Settings->PWA Settings->Manage
- 2010: PWA settings (Server settings in 2010).
Go to Administrative Backup.
Backup all the custom fields.
Go to Administrative Restore.
Restore all the custom fields.
As everything in the reporting database someway has a custom field connected this will cause the whole database to get rebuilded.
Follow the restore in the queue.
Comments
Post a Comment