Error GeneralQueueJobFailed (26000) - UpdateSRA.UpdateSRAMessage when publishing a project

[Jean-Francois_G]

Hello,

For several days now we have been receiving errors when publishing a project, errors that can be found in the configuration part of project online (queue management). An example of an error is shown below:

General

• Queue:

  • GeneralQueueJobFailed (26000) - UpdateSRA.UpdateSRAMessage. Details: id='26000'
    name='GeneralQueueJobFailed'
    uid='c06fe63b-5a3d-ed11-a540-00155d20fb18'
    JobUID='d0739d19-5a3d-ed11-a540-00155d20fb18'
    ComputerName='6be77fc4-76f0-41f2-8238-63fb8bb36f01'
    GroupType='UpdateSRA'
    MessageType='UpdateSRAMessage'
    MessageId='1'
    Stage=''
    CorrelationUID='46a668a0-d092-5000-6063-230534fb827c'
    For more details, check the ULS logs on machine 6be77fc4-76f0-41f2-8238-63fb8bb36f01 for entries with JobUID d0739d19-5a3d-ed11-a540-00155d20fb18.

How can we get the details of the ULS logs?

What does this type of error mean? Apparently it comes from resources and assignements but how can we get more detailed information? Is there any data corrupted in the DB here?

Thank you very much.

[#2]

Hi Jean, I had the same issue with a few customers.

- First make sure there are no processes waiting to be executed on the queue, navigate there, and check all the pages, if you have the same project if something is running cancel everything.

- After that, you can try to publish the project again and see what happens. If does not work I would suggest deleting the published version and republish the draft one, that will force the recreation of the information for the publish table and typically this step works.

MS will not share the log with us, they can tell what is about if you open a ticket

[#3]

A couple things to check on this:
1. Open the schedule and verify there are NO blank lines in your schedule
2. Verify that all of the enterprise resources STILL exist in your enterprise resources
3. No assignments to summary tasks
4. Look at your default Gantt chart view and fix any start/finish dates with the red squiggly lines.

If all of those are good and still have errors, let us know and we can go down the list of other culprits.