Error Id 26000 Name Generalqueuejobfailed Project.server
across an issue whereby some projects where publishing fine for some users and others where failing. After say a few tries, the same project would fail to publish with the dreaded 26000 error! (click picture to enlarge)
PWA, the below error message will be received via email: Your Project Update job failed. Its current state is failed. It was 50% complete. It entered the queue Error ID: 9133 Error ID: 26000 Detailed error below – send it to the administrator for more detailed troubleshooting.
Online and Microsoft Planner Project Server Queue - When is an error not an error? ★★★★★★★★★★★★★★★ Brian Smith - MSFTJanuary 17, 20089 0 0 0 When it is a status message? One of the challenges when interacting with an asynchronous queue is error handling. In a connected https://blogs.msdn.microsoft.com/brismith/2008/01/17/project-server-queue-when-is-an-error-not-an-error/ application it is easy to interact with the user and tell them what went wrong - but https://badalratra.wordpress.com/2013/08/18/error-id-9133-or-26000-project-server-2010/ if they have submitted a timesheet and something about it isn't quite right then it is harder to return this information. In the Manage Queue screen the problem will show as a failed job, and an error will display, but in many cases it isn't really that anything broke - just that something about the timesheet wasn't right. You may experience this more using the PSI web error id services directly from a custom application than if you are using the normal timesheet interface, as we are aware of the various states and will not let you try and submit something that isn't going to go through. However, there could be timing issues that would even make our timesheet jobs fail - and generally this information will display with the timesheet.. If you are developing a timesheet application you should consider the best way to get this information back to the resource through error id 26000 your application - as they may not see their queue jobs if they don't generally use PWA. Technorati Tags: Project Server 2007
Comments (9) Cancel reply Name * Email * Website Martin Winzig says: January 17, 2008 at 5:56 pm Nice theory, When anyone developing TS application biggest problem is that this PSI methods and datasets aren't documented well. For examle it's pretty tricky get information that I'm can't update timesheet because there is same blocking job is in the Queue: if (tsDataSet.Headers[0].ItemArray[tsDataSet.Headers.Columns["TS_QUEUE_JOB_STATUS"].Ordinal].ToString() != "0") { continue; } There isn't anything about property TS_QUEUE_JOB_STATUS in project server SDK. Martin Winzig Reply Brian Smith - MSFT says: January 18, 2008 at 5:26 pm I agree we could do better here Martin. Perhaps one approach is to build your application with access to the queue errors for the specific users - as if they are using your own timesheet they may not have ready access to their personal queue jobs that they would see from PWA. From the SDK (TimesheetEnum.QueueJobStatus Enumeration) Member name Description Failed Value=2. The job failed. Passed Value=0. The job passed. Pending Value=1. The job is pending. Reply Ed says: October 7, 2008 at 5:08 pm Hi Brithe below error message will be received via email – Your Project Update job failed. Its current state is failed. It was 50% complete. It entered the queue Error ID: 9133 Error ID: 26000 Detailed error below - send it to the administrator for more detailed troubleshooting.