Ran into a problem recently where the Workflow Timer Job on our SharePoint 2010 box was stuck at 0% and Paused.
Delete everything in the GUID Folder EXCEPT the Cache.ini file
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
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
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)\Users\Application Data\Microsoft\SharePoint\Config\GUID (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:\ProgramData\Microsoft\SharePoint\Config\GUID
- Note: The Application Data folder may be hidden. To show, click Show Hidden Files and Folders through Windows Explorer's Folder Options Setting
- 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.
- 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