Unable to open the Timer Job Definition in the Central Administration "Unknown Error"

Issue :

Unable to open the Timer Job Definition in the Central Administration "Unknown Error".

Cause:

Was able to browse through the Job History and the status. Found that there were couple of timer jobs stuck from 2 months and causing this issue. 

Fix:

Ran the "stsadm -o exeadmsvcjobs", but still the error was persist and the jobs were not getting removed.

Ran the following commands and removed the stuck jobs:


Get-SPTimerJob | ? {$_.Displayname -like “Name”}
$job = Get-SPTimerJob -id ""
$job.Delete()
Location: India

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

MORE CACHE HOSTS ARE RUNNING IN THIS DEPLOYMENT THAN ARE REGISTERED WITH SHAREPOINT

Image
So, I’ve just installed SharePoint Foundation 2013 on a clean Windows 2012 server yet the Health Analyzer is complaining about a few things.  I’ll work my way through fixing them and the first one I’ll tackle is “More Cache hosts are running in this deployment than are registered with SharePoint”. The clue for fixing this one is in the explanation: “This operation uses the SharePoint Administration service (spadminV4), which could not be contacted”.  I don’t know why this is stopped by default but starting the service (and setting it to automatic) has stopped this being flagged as a problem. More details of the Windows Server AppFabric Caching features can be found here: http://msdn.microsoft.com/en-us/library/ff383731(v=azure.10).aspx
Continue Read