Skip to main content

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:
 •     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

Popular posts from this blog

Install DLL in GAC - Windows 2008/2012 (Using Powershell, No GacUtil.exe)

If you want to install a DLL in the GAC and do not have the GACUtil.exe available. Powershell is properly the easiest way to procede.

Before Powershell you would properly just drag the DLL file into the C:\Windows\Assembly but this option is usually not available anymore.

Powershell - Add DLL to GAC So to install a DLL file in the GAC simply execute the below Powershell script. Remember you migth want to run the Powershell prompt as an administrator.
[System.Reflection.Assembly]::Load("System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")$publish=New-ObjectSystem.EnterpriseServices.Internal.Publish$publish.GacInstall("c:\temp\MyDllFile.dll")iisreset
The first line adds a reference to the assembly we need to be able to mange the GAC.
The second and third lines retrives the GAC object and publish a new DLL file to it.
The last line resets the Internet Information Services. This is only needed if your DLL file is used in a websi…

Error occurred in deployment step 'Add Solution': Attempted to perform an unauthorized operation.

Received this error today when trying to create a SharePoint solution against a newly created site.


My first problem was the site was configured to use a port which was already used by another web site. Therefore the site could not start at all.

In my case both Default Web Site and SharePoint - 2000 was both using port 2000. Changing the port of Default Web Site and I was able to start the site.

However now I still received the same error message. When browsing the site I realized I did not have access to the site.

Giving access to my user and I was able to deploy the solution.

To sum up this post:
 - Check the site can start
 - Check the site can be browsed
 - Check your user have access to the site

SharePoint 2013 : Cannot connect to the targeted site.

On my Contoso environment I was trying to create a sandboxed solution. I have already configured my app domain and app management services. But when I tried to validate the site I got the following error message.
Error

Cannot connect to the targeted site. This error can occur if the specified site is not hosted on the local system. SharePoint solutions work only with locally-installed versions of SharePoint Foundation or SharePoint Server. Remote development is supported only for apps for SharePoint 2013.
If you search around the internet you will find many people suggesting to change your host file from 127.0.0.1 to the actual IP.

Solution However the solution, at least on a Contoso environment, is to type in the actual IP address in the host file.
(the IP 192.168.150.1 is the special IP for Contoso, I have 2 network adapters)
And do not forget to clear/flush the DNS cache. Now the solution can be created and validates.