Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
ReportingProjectPublish job failed RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am receiving the following message when publishing my projects to Project Server.  Any ideas how to correct this?

    Your ReportingProjectPublish job failed.  Its current state is FailedNotBlocking.  It was 0% complete.  It entered the queue at 08/20/2010 10:25:45.

    To get more information about the job failure, please go to Project Web Access.  Select Personal Settings from the left menu.  Then select My Queued Jobs.

    The errors returned from the queue are as follows:
     Error ID: 24006
     Error ID: 26000

    Detailed error below - send it to the administrator for more detailed troubleshooting.

    <?xml version="1.0" encoding="utf-16"?>
    <errinfo>
      <general>
        <class name="Reporting message processor failed">
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="8a4a1fd0-37eb-4d57-84fa-d17587b876c8" QueueMessageBody="Project UID='7157ed29-a1ee-4d62-b9b7-9de41de7e9b3'. PublishType='ProjectPublish'" Error="One or more custom field metadata mismatch were detected while transfering project '7157ed29-a1ee-4d62-b9b7-9de41de7e9b3'" />
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="79458140-9e68-449d-b1f6-272c33fed451" QueueMessageBody="Project UID='7157ed29-a1ee-4d62-b9b7-9de41de7e9b3'. PublishType='ProjectPublish'" Error="One or more custom field metadata mismatch were detected while transfering project '7157ed29-a1ee-4d62-b9b7-9de41de7e9b3'" />
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="9de382ee-f27f-4a38-bf93-6d9cf3e636bb" QueueMessageBody="Project UID='7157ed29-a1ee-4d62-b9b7-9de41de7e9b3'. PublishType='ProjectPublish'" Error="One or more custom field metadata mismatch were detected while transfering project '7157ed29-a1ee-4d62-b9b7-9de41de7e9b3'" />
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="e2e16cc7-5522-476d-9fde-22991ea2a433" QueueMessageBody="Project UID='7157ed29-a1ee-4d62-b9b7-9de41de7e9b3'. PublishType='ProjectPublish'" Error="One or more custom field metadata mismatch were detected while transfering project '7157ed29-a1ee-4d62-b9b7-9de41de7e9b3'" />
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="ff500880-1c6e-4cf4-9ec3-eff1c67dff5b" QueueMessageBody="Project UID='7157ed29-a1ee-4d62-b9b7-9de41de7e9b3'. PublishType='ProjectPublish'" Error="One or more custom field metadata mismatch were detected while transfering project '7157ed29-a1ee-4d62-b9b7-9de41de7e9b3'" />
          <error id="24006" name="ReportingProjectChangeMessageFailed" uid="deed819a-3d2c-4840-a71f-f767fc482564" QueueMessageBody="Project UID='7157ed29-a1ee-4d62-b9b7-9de41de7e9b3'. PublishType='ProjectPublish'" Error="One or more custom field metadata mismatch were detected while transfering project '7157ed29-a1ee-4d62-b9b7-9de41de7e9b3'" />
        </class>
        <class name="Queue">
          <error id="26000" name="GeneralQueueJobFailed" uid="01c89368-23ae-4d8b-b4e5-1113d06cd33c" JobUID="598690ab-6cf3-43c6-bd5a-94369f695c37" ComputerName="RCAWINPRJSRV" GroupType="ReportingProjectPublish" MessageType="ReportProjectPublishMessageEx" MessageId="1" Stage="" />
        </class>
      </general>
    </errinfo>

    You can do the following:
    1. Try troubleshooting using the error IDs, error XML.
    2. Contact administrator with your jobID (598690ab-6cf3-43c6-bd5a-94369f695c37) and error XML.

    Thanks,

    DP

    Tuesday, August 24, 2010 2:27 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Has anyone modified the Project Workspace, specifically the metadata on the
    Risks, Issues, Deliverables or Project Documents lists?
     
    - Andrew Lavinsky
     
    > One or more custom field metadata mismatch were detected while
    > transfering project
    >
     
     
    Tuesday, August 24, 2010 3:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I do not believe so.  This happens on initial and subsequent publishes of a project.  The workspaces have not been modified.  I do not believe these have been filled out yet.

    Thanks,

    DP

    Tuesday, August 24, 2010 3:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I think this problem is stemming from some of the enterprise Custom fields. Did you change anything on th Enterprise Custom fields?

    I would suggest the following two checks (if feasible)

    1. Check your project to see if you have a wrong "type" of data in the enterprise Custom fields (text in a number column etc.,
    2. Remove all data from the custom fields for this project and try republishing. and then add data one by one into the Enterprise Custom Fields, and see if you can publish. This should probably give you the Culprit.

     

    Tuesday, August 24, 2010 3:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I did try this, but it is still failing.  I noticed that one of the custom field values is showing in RED (the rest are in black).  I'm guessing that this is the bad field, but through Custom Fields in PWA, it doesn't look like there is anything wrong with it.
    Monday, September 13, 2010 4:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Is this happening fro every project or just one dp26?  If it is happening for every project then perhaps it is the CF data that is incorrect in the reporting databsse and not the CF data in the project.

    Best regards,

    Brian.

    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    Monday, September 13, 2010 10:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm pretty sure this is happening for every project that is published.  Any ideas how to correct the issue if it is the CF data in the reporting DB?

    Thanks,

    DP

    Monday, September 20, 2010 1:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi dp26 - Backing up and then restoring your Custom Fields and Lookup tables through Server Settings, Administrative Backup and Restore options will initiate a rebuild of the reporting database which hopefully would correct any mis-match.  The job can take a while and it can look as though little is happening, but you should eventually see all queue jobs complete.

    Best regards,

    Brian.

    Blog | Facebook | Twitter | Posting is provided "AS IS" with no warranties, and confers no rights.
    Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page
    Monday, September 20, 2010 8:23 PM