Reporting (Project Publish) Failed but not blocking correlation

P

ProjectAnalyst

Recently a user was getting errors in the queue like this. The details
indicated a "Reporting message processor failed".

Turns out he attempted to copy resources from one task to another using the
Excel-like method of grabbing the bottom right corner of the resource field
and dragging it down.

What he didn't know was that the contents of the resource field exceeded 255
characters, and resource names were being truncated during the copy and paste
operation.

Once the truncated resources were removed and replaced properly with valid
ones, the errors ceased.
 
G

Gary Chefetz

Tip: It is very bad practice to use that field for any type of data
manipulation at all. Train your users that this should be used for view-only
purposes and that proper resource tools should be used for adding, changing
or modifying resource assignments.
 

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

Reporting(Project Published) Failed But Not Blocking Correlation 2
Failed But Not Blocking Correlation Error 3
Failed but not blocking correlation 3
Cannot Publish Plans - Failed and Blocking Correlation 2
Project Publish Notifications Failed 3
My queued jobs-PWA: Failed but not blocking correlation. Timesheet 2
Project - Failed but not blocking correlation 3
Queue Error - Failed but not blocking correlation 4

Top