Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGallery
TechCenter >
> 
> 
Reporting (Project Publish) - Failed But Not Blocking Correlation EPM 2007

Answered Reporting (Project Publish) - Failed But Not Blocking Correlation EPM 2007

  • Tuesday, May 01, 2012 8:24 AM
     
     
    Sign In to Vote
    0

    Morning,

    we recieved the following errors this morning in the Queue, this has happened in the past and we have restarted the Microsoft Office Project Server Queue Service but this hasn't helped. Does anyone know what else i can do?

    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="64f01e43-e7a4-4821-b01d-15d74b5d7713" QueueMessageBody="Project UID='2730e1da-d4b7-47dd-9557-275fcbba03ca'. PublishType='ProjectPublish'" Error="The INSERT statement conflicted with the FOREIGN KEY constraint &quot;FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID&quot;. The conflict occurred in database &quot;PWA_Reporting&quot;, table &quot;dbo.MSP_EpmTask&quot;.&#xD;&#xA;The statement has been terminated." />
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="cdaaf73a-0a14-47df-8734-b9c8d36aa338" QueueMessageBody="Project UID='2730e1da-d4b7-47dd-9557-275fcbba03ca'. PublishType='ProjectPublish'" Error="The INSERT statement conflicted with the FOREIGN KEY constraint &quot;FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID&quot;. The conflict occurred in database &quot;PWA_Reporting&quot;, table &quot;dbo.MSP_EpmTask&quot;.&#xD;&#xA;The statement has been terminated." />
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="1922c5e9-8c3c-4bd1-9c90-76e337082c60" QueueMessageBody="Project UID='2730e1da-d4b7-47dd-9557-275fcbba03ca'. PublishType='ProjectPublish'" Error="The INSERT statement conflicted with the FOREIGN KEY constraint &quot;FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID&quot;. The conflict occurred in database &quot;PWA_Reporting&quot;, table &quot;dbo.MSP_EpmTask&quot;.&#xD;&#xA;The statement has been terminated." />
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="850f18b8-6a4d-4955-86bc-e720565c26f3" QueueMessageBody="Project UID='2730e1da-d4b7-47dd-9557-275fcbba03ca'. PublishType='ProjectPublish'" Error="The INSERT statement conflicted with the FOREIGN KEY constraint &quot;FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID&quot;. The conflict occurred in database &quot;PWA_Reporting&quot;, table &quot;dbo.MSP_EpmTask&quot;.&#xD;&#xA;The statement has been terminated." />
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="32ab1be1-fae1-4a9d-8937-6ff2d47b9a25" QueueMessageBody="Project UID='2730e1da-d4b7-47dd-9557-275fcbba03ca'. PublishType='ProjectPublish'" Error="The INSERT statement conflicted with the FOREIGN KEY constraint &quot;FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID&quot;. The conflict occurred in database &quot;PWA_Reporting&quot;, table &quot;dbo.MSP_EpmTask&quot;.&#xD;&#xA;The statement has been terminated." />
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="a2657597-42c6-4766-989a-696d33a668f5" QueueMessageBody="Project UID='2730e1da-d4b7-47dd-9557-275fcbba03ca'. PublishType='ProjectPublish'" Error="The INSERT statement conflicted with the FOREIGN KEY constraint &quot;FK_MSP_EpmTaskBaseline_ProjectUID_TaskUID&quot;. The conflict occurred in database &quot;PWA_Reporting&quot;, table &quot;dbo.MSP_EpmTask&quot;.&#xD;&#xA;The statement has been terminated." />
        </class>
        <class name="Queue">
          <error id="26000" name="GeneralQueueJobFailed" uid="de9e5f30-1aa9-4dd4-aa5a-801b6833f4d9" JobUID="7c410288-7098-487e-a248-bf70960b4e6a" ComputerName="EH-SPT-D03" GroupType="ReportingProjectPublish" MessageType="ReportProjectPublishMessageEx" MessageId="1" Stage="" />
        </class>
      </general>
    </errinfo>

    .: Lister :.

     

All Replies

  • Tuesday, May 01, 2012 5:04 PM
     
     
    Sign In to Vote
    0

    Hello Mike,

    Above error message indicates that your reporting database is out of sync.

    Are you experiencing this issue with specific project or any project as well as new project?

    Depending on type of the issue we may need to take either of the following steps

    a. Try saving effected project plans using "Save for Sharing" option

    b. Try re-saving each enterprise custom fields and look up tables

    c. Last option is to perform RDB refresh

    Hrishi Deshpande – DeltaBahn Senior Consultant
    Blog | < | LinkedIn

     
  • Friday, May 04, 2012 10:46 PM
     
     Answered
    Sign In to Vote
    0

    Hi Mike,

    this issue occurs when people save a checked out project as local file in some conditions. Due to changes in GUIDs, baseline entries in the PWA databases will become orphaned and the reporting process will fail. The only and actually rather simple solution is to delete these orphaned baselines.

    Detect the error:

    USE ProjectServer_Draft
    SELECT * from MSP_TASK_BASELINES where TASK_UID not in (select TASK_UID from MSP_TASKS)

    USE ProjectServer_Published
    SELECT * from MSP_TASK_BASELINES where TASK_UID not in (select TASK_UID from MSP_TASKS)

    Use "DELETE" instead of "SELECT *" to delete the orphaned records afterwards

    See Brian's Blog for more details, a fix will be coming presumably June 2012. If have used those queries extensively for 3 months now for one of our customers.

    http://blogs.msdn.com/b/brismith/archive/2012/05/01/project-server-2010-orphan-baselines-breaking-the-reporting-publish.aspx

    Kind regards,
    Adrian




     
  • Friday, May 04, 2012 10:50 PM
     
     
    Sign In to Vote
    0

    Brian's blog is related to 2010, but could be worth to test against 2007 as well.

    Hrishi Deshpande – DeltaBahn Senior Consultant
    Blog | < | LinkedIn

     
  • Saturday, May 12, 2012 5:18 PM
     
     
    Sign In to Vote
    0

    Oh, I missed the EPM 2007 in the headline. But the issue had occurred in 2007 as well, and the queries also date back to 2007. Running the SELECT query poses no risk and will quickly tell you whether you're affected by this issue.

    Kind regards,
    Adrian