THE SHAREPOINT 2010 TIMER SERVICE TERMINATED WITH SERVICE-SPECIFIC ERROR %%-2147467259

Today I have been dealing with lots of errors being logged in the System event log in a SharePoint 2010 development environment.  The error is Event ID 7024:
The SharePoint 2010 Timer service terminated with service-specific error %%-2147467259
EventID_7024
I tried restarting the Timer Service and restarting the Windows 2008 server but this didn’t stop the messages being logged.  While looking around Central Administration I could see that there were no scheduled jobs:
Scheduled_Jobs
I couldn’t really see anything obvious in the ULS logs but after various troubleshooting steps I fixed this by adding the service account used by the SharePoint Timer Service to the local Administrators group and restarting the Timer Service.

Comments

Post a Comment

Popular posts from this blog

SharePoint 2013 and InfoPath 2013 - Creating Web Enabled Forms

Image
In this article, you will learn how to create web enabled InfoPath forms. InfoPath is an information gathering tool and is used to create XML forms. People have always been trying to come up with a standard for creating electronic forms. Before InfoPath, companies created electronic forms in different formats. InfoPath has helped companies to adhere to a standard. Coding XML manually may not be an interesting job but creating XML forms with InfoPath has really made this job quite easier. All clients must have InfoPath installed on their machines in order to open the forms. It could be a problem for smaller companies to provide InfoPath client to all the users. What can be the solution then? Solution is to create web enabled forms that can be opened in web browser without having to install InfoPath client on user machines. Following is a step-by-step guide that will show you how to create and deploy a web enabled form: 1.Open InfoPath (Start > All Programs > Microsoft Offic...
Continue Read

"There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word." Office WebApp Error

Problem: When Opening a word document I get the following error when Office Web Apps tries to render the document " There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word. " Initial Hypothesis: Check the ULS logs on the Web Front End (SharePoint Server) as this doesn't tell me much.  I found the following issue in my UL S: WOPI (CheckFile) - Invalid Proof Signature for file SandPit Environment Setup.docx url: http://web-sp2013-uat.demo.dev/Docs/_vti_bin/wopi.ashx/files/6d0f38c0d5554c87a655558da9cedcad?access_token... Resolution: Run the following PS> Update-SPWOPIProofKey -ServerName "wca-uat.demo.dev" More Info: http://technet.microsoft.com/en-us/library/jj219460.aspx
Continue Read

Search stops working and Central admin Search screens error

Image
Problem: In my redundant Search farm, search falls over.  It was working, nothing appears to of changed but it suddenly stops working.  This problem has caused itself to surface in several places: 1. In  Central Admin going to "Search Administration" displays the following error message:  Search Application Topology - Unable to retrieve topology component health states. This may be because the admin component is not up and running. 2. Query and crawl stopped working. 3. Using PowerShell I can't get the status of the Search Service Application PS> $srchSSA = Get-SPEnterpriseSearchServiceApplication PS> Get-SPEnterpriseSearchStatus -SearchApplication $srchSSA Error: Get-SPEnterpriseSearchStatus : Failed to connect to system manager. SystemManagerLocations: net.tcp://sp2013-srch2/CD8E71/AdminComponent2/Management 4. In the "Search Administration" page within Central Admin, if I click " Content Sources " I get the error mes...
Continue Read