We have this problem where occasionally, maybe once a month, our sharepoint server stops sending workflow emails and refuses to update solutions through stsadm.With the built inworkflows, feedback and approval, if Istart the workflow on a document I will get a notification that it started; However the person whoit was assigned to will not get the email (they can go to the document and complete it). Oddly enough people added to the CC list get notified. Sometimes they do run properly, except for they wait till the end of the day. I double checked and the timer job is defined to run in minutes not daily.With solutionsif I run the command "stsadm -o upgradesolution -name solution.wsp -filename c:\solution.wsp -immediate" The timer job will be created, but will never run. You can go into central admin in the solution management and see that its scheduled to be updated. Also I cannot retract a solution or anything like that.Restarting the timer service fixes everything; however the problem eventually comes back. Also restarting the service spams everyones email with notifications from workflows and stuff, so that solution is not ideal.Has anyone else heard of problems like this happening? I cannot see any indication of a problem when looking at the system and sharepoint error logs.

Hello, According to the symptom youve met, it seems that the timer service file system cache is the main cause. Then I suggest you the following workaround: 1. Make sure the account running the SharePoint Timer service is the account which has the administrator Full Control permission over the site and the full permission over the content database. 2. Use Windows Explorer to open the 'Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\ <GUID>' folder. 3. Back up the .xml files and then delete the .xml files. 4. Open the Cache.ini file and then change the content of the Cache.ini setting to 1. 5. Click Start, point to Administrative Tools, and then click Services. 6. Restart the following Windows Services in the order shown: 1) Windows SharePoint Services Timer service. 2) Windows SharePoint Services Administration service. Hope it can help you, JerryXing-Bing Yu

Ok Ill give it a try.Should this be a permanent solution or is it more of a bandaid solution?Im wondering if I should keep searching for why the cache is messed up in the first place

Hello, Please first try the method I provide to see whether it will work and confirm cache is the root cause. If it wont work, please feel free to let me know, and I will provide another solution to fix that. Regards, JerryXing-Bing Yu

Ok I actually fixed some other things on the server that may have been causing problems, an old ssp that was corrupted somehow still had jobs setup in the database.So Im going to leave it as is until the problem occurs again. If it occurs I will try the method you mentioned above. If that doesnt fix it I will reopen the thread.Thanks

JerryI have an issue with all SharePoint Jobs are not running at all after I appliedMS hot fix http://support.microsoft.com/default.aspx/kb/939592/en-usAll e-mail alerts for changing doc lib content are notsending from MOSS farm any more. Only initial alert is sent but none of any changes tracked.Ichecked my Central SP Admin settings and all Jobs have records - last successful run was2 days ago just before that Ms Hot Fix was applied. I also noticed that my MOSS farm document libraries stopped to receiveincoming e-mail as they were getting them before .Incoming e-mails are not picked up by SharePoint from "drop" folder since 03/31/2009 - right after I applied this MS hot fix http://support.microsoft.com/default.aspx/kb/939592/en-usI tried your solution above by deleting xml files and changing the .ini file to 1 and restarted services - no avail. Still no any alerts sent after initial one. Could you please direct me to other things which can help me to solve my problems with alerts and incoming emails to SharePoint doc libraries? Thank you very much for your help. - Andrei

Andreich, Did you ever solve your issue?? I'm running into the same problem. Not one job has run on our WFEs since June. The config still hasn't refreshed and it's been a day. I'm lost on what to do, I have no idea what is causing this. Thanks Sike Mullivan