Error Id 26000 Name Generalqueuejobfailed
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) Investigation The only other time I had seen this before was when the RTM update had failed leading to binaries being at a patch level different to the databases. Not this time! I checked the patch levels of each database and also the client apps. This was confusing! How can a project publish perfectly well as many as 10 times and then suddenly fail! The inconsistency was worrying and hard to troubleshoot. - the SharePoint Config Wizard (SCW) indicated no problems with the farm - projects were saving and checking in fine. On closer examination of the ULS logs (throttled for verbose) I determined that there was a possible issue with a procedure in the Published SQL DB. This was not a good sign. (click picture to enlarge) I then ran the database integrity check on the Published database and this pointed to database corruption! Error 8967 is not a good sign! but, at least I knew what the cause of the issue was. This error was somewhat similar to another SQL issue http://support.microsoft.com/kb/960791/en-us. It did not, however, cover my exact scenario, but, was an indicator of the type of issue I was facing. (click picture to enlarge) Resolution To resolve the issue the options were; Repair the SQL database (REPAIR_ALLOW_DATA_LOSS, REPAIR_FAST, REPAIR_REBUILD). Note: use the first
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: errorid="26000"name="GeneralQueueJobFailed for GroupType="ReportWorkflowProjectDataSync" Project , Project Server > Project Server General Questions and Answers Question 0 Sign in to vote HI All, getting error whenever any of the my user want to publish http://microsoftepmsolution.blogspot.com/2009/08/project-publish-error-26000-database.html project on PWA 2010. They are able to publish project via Project Pro 2010 and WEB APP but at the same time getting error mail and at queue to .Below is the error DESC. Your ReportWorkflowProjectDataSync job failed.Its current state is https://social.technet.microsoft.com/Forums/projectserver/en-US/e4321b99-24b8-4eb1-907a-f01d92c69135/errorid26000namegeneralqueuejobfailed-for-grouptypereportworkflowprojectdatasync?forum=projectserver2010general FailedNotBlocking.It was 0% complete.It entered the queue at ...... The errors returned from the queue are as follows: Error ID:26000 Detailed error below - You can do the following: 1. Try troubleshooting using the error IDs, error XML. 2. Contact administrator with your jobID (78ed474f-93a2-4e20-be28-8460533ca3da) and error XML. Edited by Kirteshtiw Friday, September 23, 2011 7:01 AM Friday, September 23, 2011 5:51 AM Reply | Quote Answers 0 Sign in to vote Hi all, I got the solution for the problem i opened all of the EPT and save them again, and restarted the workflow and now i am not getting any error. Marked as answer by Kirteshtiw Tuesday, October 04, 2011 9:5
2010, Troubleshooting | It's not often these days I come across what seems to be a new Project Server 2010 error! Having said that, I http://nearbaseline.com/2014/01/queue-error-creating-project-site-or-synchronizing-site-permissions/ would expect the same error to occur on either 2007 or 2013 as it relates to AD sync. Anyway while working with a customer recently I came across the following issue that had started occurring for all new projects being created as well as on any attempt to synchronize the site permissions from Server Settings - Project Sites. The effect of error id the error was that users cannot access any of the affected sites. Notably though the AD sync was not experiencing any errors. Error Messages GeneralQueueJobFailed (26000) - SynchronizeMembershipForWssSite.SynchronizeMembershipForWssSiteMessage. Details: id='26000′ name='GeneralQueueJobFailed' uid='677df8c5-7409-4e20-8a05-e98395aa2af3′ JobUID='3ca3af00-2e08-49aa-b693-f1314fc09b96′ ComputerName='…' GroupType='SynchronizeMembershipForWssSite' MessageType='SynchronizeMembershipForWssSiteMessage' MessageId='1′ Stage=" And in the ULS log we see some more details: 01/14/2014 15:43:07.23 Microsoft.Office.Project.Server (0x1694) 0x1558 SharePoint Foundation General 8kh7 High Access denied. You do error id 26000 not have permission to perform this action or access this resource.0x810200ce 237e539d-3835-4ec0-84d3-383759fccdb6 01/14/2014 15:43:07.23 Microsoft.Office.Project.Server (0x1694) 0x1AAC Project Server Queu cf0l Critical Standard Information:PSI Entry Point: Project User: …. Correlation Id: 237e539d-3835-4ec0-84d3-383759fccdb6 PWA Site URL: http://server/PWA SSP Name: Project Server Service Application PSError: GeneralQueueJobFailed (26000) A queue job has failed … Investigation and Resolution I've highlighted the interesting bits of the logs above, and on searching for this specific issue the only references relate to Search Service indicating one of the following causes: The FarmAdmin account is not a local admin on the servers. One or more AD accounts has been deleted and recreated with the same name. So after speaking with the AD team it turns out the customer was in the middle of an Active Directory restructure (alarm bells start ringing!) and specifically about the same time when this issue was first reported the AD team had moved a group of PWA users into a new sub-domain in the same AD forest. Reverting that change immediately corrected the isssue! Phew. Not completely done yet though, as that change will need to be