none
Decoding MessageID/MsgID in Errors RRS feed

  • Question

  • Hi all,

    If I see a message like:

    ProjectPublishFailure (23000). Details: id='23000' name='ProjectPublishFailure' uid='2e48524d-a448-4e92-bf32-8f8f56ed980f' projectuid='c5d2823b-860e-4015-948f-a4e4d19c2e85' messagetype='Microsoft.Office.Project.Server.BusinessLayer.QueueMsg.PublishProjectMessage' messageID='131' stage='' blocking='Block'.

    Can I use the error codes defined in http://msdn.microsoft.com/en-us/library/ms508961(v=office.12).aspx to decode the MessageID?

    Thanks,

    Erik


    Erik RHS

    Wednesday, June 18, 2014 11:27 PM

All replies

  • Hi Erik

    Yes you can use the values but the Project server error code will give you high level information as to which functional area this code belongs to for further understanding the error you will need to review the ULS log for the detailed error message as to what might be causing this


    Thanks | epmXperts | http://epmxperts.wordpress.com


    Thursday, June 19, 2014 1:26 PM
    Moderator
  • Thanks for the response! I see basically the same info in the ULS logs. I have "Project Save from Project Professional" jobs that fail from time to time. In the ULS logs, I can see the job go through the 5 retry attempts and then ultimately fail with something like "ACProjectSave aborted at Message 131". I am trying to get an understanding what this Message ID means.

    Erik RHS

    Thursday, June 19, 2014 4:36 PM
  • Hi Erik

    There should be something before retry like some WCF operation or something you will need to look between begin group message and end message in between wherever its failing you might see something in the description which would say what its waiting on

    Typically retry attempt would tell me that there could either be a network or a DB issue, 5 retries are the settings defined in the queue settings, which means while trying to process the job its not able to reach the DB (typically) or DB has locks and is waiting and retrying and if it still can't process the Job with 5 retries it would abort the processing  


    Thanks | epmXperts | http://epmxperts.wordpress.com

    Thursday, June 19, 2014 4:47 PM
    Moderator
  • Thanks! We have seen I/O issues on SQL Server cause jobs to fail in the past, and usually they are accompanied by errors in the Windows and ULS logs that indicate a timeout. Not seeing that here, but I appreciate your comments and experience.

    Cheers,

    Erik


    Erik RHS

    Thursday, June 19, 2014 5:08 PM