Error: "Your queue job ReportingProjectPublished failed. Pleasecontact your administrator..."

A

anovak

Anyone have the fix for this?? What causes it?

The other day, I did delete a handful of project-level custom fields
that we were not using anymore.

Does this have something to do with OLAP? When custom fields are
deleted, do you have to create a different OLAP database?

This error message came from one of my PMs who I had helped import a
project from an *mpp, save to the database, and publish. But the
OLAP build job hasn't run yet.

Thanks,
Andy Novak
UNT


Your ReportingProjectPublish job failed. Its current state is
FailedNotBlocking. It was 0% complete. It entered the queue at
09/17/2008 11:28:59.

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="135a0a95-6ac6-4f8b-935b-4cd82f0cb07c" QueueMessageBody="Project
UID='c3ca246e-0659-459c-9369-f77c360d4e88'.
PublishType='ProjectPublish'" Error="One or more custom field metadata
mismatch were detected while transfering project
'c3ca246e-0659-459c-9369-f77c360d4e88'" />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="c2fad990-1a0f-4528-9d39-63f5a00e0f5f" QueueMessageBody="Project
UID='c3ca246e-0659-459c-9369-f77c360d4e88'.
PublishType='ProjectPublish'" Error="One or more custom field metadata
mismatch were detected while transfering project
'c3ca246e-0659-459c-9369-f77c360d4e88'" />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="6525fadd-7695-493e-affb-89df9d889b36" QueueMessageBody="Project
UID='c3ca246e-0659-459c-9369-f77c360d4e88'.
PublishType='ProjectPublish'" Error="One or more custom field metadata
mismatch were detected while transfering project
'c3ca246e-0659-459c-9369-f77c360d4e88'" />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="54956073-38f7-4233-a1dc-91ccf14b68d5" QueueMessageBody="Project
UID='c3ca246e-0659-459c-9369-f77c360d4e88'.
PublishType='ProjectPublish'" Error="One or more custom field metadata
mismatch were detected while transfering project
'c3ca246e-0659-459c-9369-f77c360d4e88'" />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="79ae7d14-7d9b-4875-913b-0f66980b1a3b" QueueMessageBody="Project
UID='c3ca246e-0659-459c-9369-f77c360d4e88'.
PublishType='ProjectPublish'" Error="One or more custom field metadata
mismatch were detected while transfering project
'c3ca246e-0659-459c-9369-f77c360d4e88'" />
<error id="24006" name="ReportingProjectChangeMessageFailed"
uid="32bbeade-8eca-4c79-bd7d-89a807901590" QueueMessageBody="Project
UID='c3ca246e-0659-459c-9369-f77c360d4e88'.
PublishType='ProjectPublish'" Error="One or more custom field metadata
mismatch were detected while transfering project
'c3ca246e-0659-459c-9369-f77c360d4e88'" />
</class>
<class name="Queue">
<error id="26000" name="GeneralQueueJobFailed"
uid="0b840bbc-10d2-4bbe-a298-19314671410b"
JobUID="d5a33d10-416c-4520-8a2b-6f81a7e9747d" ComputerName="PROJECT"
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
(d5a33d10-416c-4520-8a2b-6f81a7e9747d) and error XML.
 
R

Ravi

Anyone have the fix for this??   What causes it?

The other day, I did delete a handful of project-level custom fields
that we were not using anymore.

Does this have something to do with OLAP?   When custom fields are
deleted, do you have to create a different OLAP database?

This error message came from one of my PMs who I had helped import a
project from an *mpp, save to the database, and publish.   But the
OLAP build job hasn't run yet.

Thanks,
Andy Novak
UNT

Your ReportingProjectPublish job failed.  Its current state is
FailedNotBlocking.  It was 0% complete.  It entered the queue at
09/17/2008 11:28:59.

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="135a0a95-6ac6-4f8b-935b-4cd82f0cb07c" QueueMessageBody="Project
UID='c3ca246e-0659-459c-9369-f77c360d4e88'.
PublishType='ProjectPublish'" Error="One or more custom field metadata
mismatch were detected while transfering project
'c3ca246e-0659-459c-9369-f77c360d4e88'" />
      <error id="24006" name="ReportingProjectChangeMessageFailed"
uid="c2fad990-1a0f-4528-9d39-63f5a00e0f5f" QueueMessageBody="Project
UID='c3ca246e-0659-459c-9369-f77c360d4e88'.
PublishType='ProjectPublish'" Error="One or more custom field metadata
mismatch were detected while transfering project
'c3ca246e-0659-459c-9369-f77c360d4e88'" />
      <error id="24006" name="ReportingProjectChangeMessageFailed"
uid="6525fadd-7695-493e-affb-89df9d889b36" QueueMessageBody="Project
UID='c3ca246e-0659-459c-9369-f77c360d4e88'.
PublishType='ProjectPublish'" Error="One or more custom field metadata
mismatch were detected while transfering project
'c3ca246e-0659-459c-9369-f77c360d4e88'" />
      <error id="24006" name="ReportingProjectChangeMessageFailed"
uid="54956073-38f7-4233-a1dc-91ccf14b68d5" QueueMessageBody="Project
UID='c3ca246e-0659-459c-9369-f77c360d4e88'.
PublishType='ProjectPublish'" Error="One or more custom field metadata
mismatch were detected while transfering project
'c3ca246e-0659-459c-9369-f77c360d4e88'" />
      <error id="24006" name="ReportingProjectChangeMessageFailed"
uid="79ae7d14-7d9b-4875-913b-0f66980b1a3b" QueueMessageBody="Project
UID='c3ca246e-0659-459c-9369-f77c360d4e88'.
PublishType='ProjectPublish'" Error="One or more custom field metadata
mismatch were detected while transfering project
'c3ca246e-0659-459c-9369-f77c360d4e88'" />
      <error id="24006" name="ReportingProjectChangeMessageFailed"
uid="32bbeade-8eca-4c79-bd7d-89a807901590" QueueMessageBody="Project
UID='c3ca246e-0659-459c-9369-f77c360d4e88'.
PublishType='ProjectPublish'" Error="One or more custom field metadata
mismatch were detected while transfering project
'c3ca246e-0659-459c-9369-f77c360d4e88'" />
    </class>
    <class name="Queue">
      <error id="26000" name="GeneralQueueJobFailed"
uid="0b840bbc-10d2-4bbe-a298-19314671410b"
JobUID="d5a33d10-416c-4520-8a2b-6f81a7e9747d" ComputerName="PROJECT"
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
(d5a33d10-416c-4520-8a2b-6f81a7e9747d) and error XML.
Click to expand...

Hi Anovak,

Are you still getting this error message on publishing?

Thanks,
Ravi.
 
A

anovak

Andy:

If any of those custom fields were included in your Cube configuration, you
must remove them from the cube.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting:http://www.msprojectexperts.com
Project Server Training:http://www.projectservertraining.com
Project Server FAQS:http://www.projectserverexperts.com
Project Server Help Blog:http://www.projectserverhelp.com
Click to expand...

Gary, I checked the Cube configuration and none of the custom fields I
had deleted previously are included in the cube. As a matter of fact,
I reverted to a new database "OLAP6" when I created the new cube.
Now, I do have OLAP1-OLAP5 databases sitting out there that are no
longer being refreshed, but I assume that those don't have anything to
do with current operations. I wonder if dropping those old reporting
databases would have any impact on this issue?
Thanks,
Andy
 
G

Gary L. Chefetz

Andy:

Rereading the original post again, this appears to be a problem with writing
to the reporting database, which is the source for the OLAP data. So, the
OLAP cube doesn't appear to be the problem. When you removed the fields, did
you open old projects that contained values for the fields and remove the
values? I'll bet that's the source of the problem.


----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com


Andy:

If any of those custom fields were included in your Cube configuration,
you
must remove them from the cube.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting:http://www.msprojectexperts.com
Project Server Training:http://www.projectservertraining.com
Project Server FAQS:http://www.projectserverexperts.com
Project Server Help Blog:http://www.projectserverhelp.com
Click to expand...

Gary, I checked the Cube configuration and none of the custom fields I
had deleted previously are included in the cube. As a matter of fact,
I reverted to a new database "OLAP6" when I created the new cube.
Now, I do have OLAP1-OLAP5 databases sitting out there that are no
longer being refreshed, but I assume that those don't have anything to
do with current operations. I wonder if dropping those old reporting
databases would have any impact on this issue?
Thanks,
Andy
 
A

anovak

Andy:

Rereading the original post again, this appears to be a problem with writing
to the reporting database, which is the source for the OLAP data. So, the
OLAP cube doesn't appear to be the problem. When you removed the fields, did
you open old projects that contained values for the fields and remove the
values? I'll bet that's the source of the problem.

----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting:http://www.msprojectexperts.com
Project Server Training:http://www.projectservertraining.com
Project Server FAQS:http://www.projectserverexperts.com
Project Server Help Blog:http://www.projectserverhelp.com







Gary, I checked the Cube configuration and none of the custom fields I
had deleted previously are included in the cube.  As a matter of fact,
I reverted to a new database "OLAP6" when I created the new cube.
Now, I do have OLAP1-OLAP5 databases sitting out there that are no
longer being refreshed, but I assume that those don't have anything to
do with current operations.  I wonder if dropping those old reporting
databases would have any impact on this issue?
Thanks,
Andy
Click to expand...

Gary, do you mean remove the field values BEFORE I deleted the fields?
I didn't do anything to the old projects before or after I deleted the
fields. If I open an old
project now and bring up the Project Information... dialog box, none
of the old
fields display at all. If I Google this error, several other folks
have seemed to
run into this. This may call for an open ticket to Microsoft.
 
C

Chirlu

Check for inactive ressources. I had the problem with a project and
re-activating the ressources temporarily solved the problem.
 

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 2007 Publishing Fails: Report Job, Failed But Not Blocking 1
Error=Cannot transfer project, A FK constraint was thrown 3
Project Failing in the Reporting(Project Publish) Step 0
Master Project Publishing Error + Alerts†1
Project Fails in the "Reporting(Project Publish) Step 2
Projects not finishing the publish process. 1
Queue Error - Failed but not blocking correlation 4
Publishing Project Plan Error 2

Top