Ran into a problem recently where the Workflow Timer Job on our SharePoint 2010 box was stuck at 0% and Paused.
Restarting the Timer Job and trying to kick off again did not provide the fix I was hoping. So after some googling, I finally came across a solution. This appears to happen if your cache is full so the solution is to clear your system cache on every server that the Workflow is trying to run on. In my case that was my one web front end and my one crawl server.
Perform the following steps on each server your workflow is running on:
- Go to Start -> Administrative Tools -> Services
- Find the SharePoint Timer Job Service -> Right Click -> Press Stop to stop the service
- On the computer Central Admin is on, open Windows Explorer and navigate to the following location: Drive (the drive SharePoint is installed on, in my case that is the C drive)UsersApplication DataMicrosoftSharePointConfigGUID (there will be folders named with a GUID, go into each one and perform these steps)
- For Windows Server 2008 the folder location is: Drive:ProgramDataMicrosoftSharePointConfigGUID
- Note: The Application Data folder may be hidden. To show, click Show Hidden Files and Folders through Windows Explorer’s Folder Options Setting
- Delete everything in the GUID Folder EXCEPT the Cache.ini file
- When you empty this folder (the configuration cache) make sure you do not delete the GUID Folder itself and the cache.ini file that is located in the GUID folder.
- Open the Cache.ini file in a text editing program
- Delete everything in the file and type 1
- Save and close the file
- Go to Start -> Administrative Tools -> Services -> Find the SharePoint Timer Job -> Right Click -> Start
- Note: The file system cache is re-created after you perform the previous steps. Make sure that you perform these steps on all servers in the farm that are running your timer job
- Go to Central Admin -> Monitoring -> Find your stalled Timer Job -> Check Job Status -> Find your Timer Job -> Click Run Now and verify that it executes successfully
Do you know if this would work for Sharepoint 2007 as well? Every day or two our incremental search will get paused and halts all future searches until we resume and finish that crawl. Not sure why this is happening and haven't found much online that speaks to this issue. Your post is about the closest. Thanks, Nelson
I haven't tried this on SharePoint 2007 to say for sure but I don't see any reason why it wouldn't work with 2007. Hope this helps!
Hi ,
I deleted the job-delete-timer-job-history accidentally and even the job definition wont show up now.
what is the easiest method to re create/undelete the job without any downtime.
Nicholas
Run the farm configuration wizard during off hours (will reset IIS and give a 503 in the meantime while it runs) that should recreate the job.
A little late in repolying but yeah it does work for 2007 as well.
Hello,
I too have the same problem with Nintex workflow scheduler timer job. But clearing cache is not helping me to resolve the issue. Any other thoughts?
Thanks,
Soni
This could help you:
https://community.nintex.com/docs/DOC-1254
Thank you for this! It was almost like magic. 🙂
nice
Magic – Thank you mucccccccccccccccccccccccccccccccccccccccccccch
This worked.Thanks!
Can you tell me how to tell when the cache is about to be full, to prevent this from happening again?
This comment has been removed by a blog administrator.
I would also be interested in know what the fix would be to prevent this from happening in the future.