ReportingSummaryPublish job failed RRS feed

  • Question

  • Hi All,

    I have a server configuration which leverages SSRS reporting to produce reports from project metadata.

    When I "Edit" and "Save" some projects I recieve the following error "

    ReportingSummaryPublish job failed.  Its current state is FailedNotBlocking.  It was 0% complete.  It entered the queue at 09/16/2013 08:32:50."

     which essentially places my project in "No man's land" and prevents that project's data from being displayed in my reports.

    We are currently in development and the only fix has been to restart the workflow but this is not feasible in production one many project will be loaded onto the server.

    Please provide assistance at your earliest convenience as this is a time senstitve issue.


    Edan Golomb

    Monday, September 16, 2013 1:21 PM

All replies

  • Hi Edan --

    I am guessing that your issue somehow lies with your custom developed workflow. If so, then it is not something that we can troubleshoot in this forum.

    Please contact me directly if you would like help troubleshooting the issue.

    Good luck!

    -- tz

    Tony Zink | Vice President, EPMA | | Blog: | Training:

    Monday, September 16, 2013 1:30 PM
  • Hello,

    What error details do you see in the queue? Check the ULS logs also as this may give more details.

    Many thanks


    Paul Mather | Twitter | | CPS

    Monday, September 16, 2013 1:39 PM
  • Paul,

    I recieve a "Failed but Not Blocking Correlation" error when I go to my Que Jobs and look at the Job State column.

    Any help would be appreciated.

    Monday, September 16, 2013 9:49 PM
  • Hey there,

       Usually there is a click for more information link:

    This usually yields a correlation id that can be looked up in the ULS logs that Paul was referring to above.  If you error doesn't have this information, look in the ULS logs at that exact time to collect additional information.

    Good Luck,


    James Boman - Software Consultant for IPMO -

    Tuesday, September 17, 2013 2:25 AM
  • Does this help explain the error?


    • Reporting message processor failed:
      • ReportingProjectChangeMessageFailed (24006) - Object reference not set to an instance of an object.. Details: id='24006'


    • GeneralQueueJobFailed (26000) -

    Tuesday, September 17, 2013 12:53 PM
  • Yes - it does help.

    This looks like a known issue when your Project has a baseline that contains a task with a zero duration like a milestone. 

    More info here.



    James Boman - Software Consultant for IPMO -

    Wednesday, September 18, 2013 12:43 AM