Reason why Projects are Stuck in a "Queued" State for Publishing

Patrick Ng November 05, 2021 02:44

Overview

You would like to know the reason for why published projects are stuck in the queued state.

Solution

Aggressive multithreading depletes the DB connections of the connection pool causing jobs to fail

Please contact EPM Support to get the issue resolved

Our teams will reset the status of failing jobs to be re-picked for execution restart the timer service and repeat this multiple times until the jobs queue is empty

<supportagent>

Please escalate the issue to the SaaS Ops team who will perform the next steps (reset status, restart service, until the job queue is empty)

</supportagent>

Patrick Ng November 05, 2021 02:44

Sections

Other articles in this section

Troubleshooting and FAQs Slow response time with the EPM Live system Reason why Projects are Stuck in a "Queued" State for Publishing Processes or Timesheets Stuck in Queued/Processing State Project Stuck in the Security Queue Timesheet Settings Access for Users/Resources Resource has Incorrect Role for a Time Period Unable to add new resource to resource pool Unable to access Microsoft Project from EPM Live MS Project not updating project hours from EPM Timesheets C: Drive filled with logs risking an EPM server crash

Comments

0 comments

Please sign in to leave a comment.

Was this article helpful?

0 out of 0 found this helpful