SharePoint Job Timer Problems
Hi Forum,
I have created a SharePoint job that is supposed to run on a daily basis, it runs ok on our Development Machines but not on the Test Server.
When I tried deploying to the test server, everything deployed ok and the timer was set to run daily, I usually just check that the time actually ran but it didn’t this time. After many hassles trying to get it to run I noticed that none of the SharePoint jobs were running these included Workflow, content management, and statistics. In fact the last job that ran was on the 28th of March.
I have checked that the OWSTIMER service is running (Windows SharePoint timer service) as this is the service that actually runs the scheduled jobs.
Do you know how I can get the Jobs to start running again? Has anyone ever come across this problem before, maybe the service has become corrupt.
Thanks,
Robert
I am having a similar problem,
My sharepoint timer jobs have not run since 31/03/2007
The only thing I did on the server this day was to deploy SP2 for windows
2003,
Deployed SP2 to both Development Server and Live Server,
Development Timer jobs are unafected so may be a coincidence.
Any help would be appreciated.
Best Regards,
Daniel.
Sorry I won't give you a solution to your problem, but maybe you can give me some advice about job programming in SharePoint. By the object model, where can I find :
- the job list in SharePoint (i know there is the SPRunningJobCollection, but can i get it?)
- the definition of the profile import schedules
Thanks a lot for your help
jerome
For the first two, have you had any problems with DST? I can't imagine that would be affecting it now, but that would be my first thought. Is anything happening in the logs concerning the jobs?
For Jerome, check out Andrew Connell's blog for an intro to Job programming (www.andrewconnell.com/blog).
I am seeing the same problem on a test server. I checked the Windows SharePoint timer service and it is running (even tried restarting the service).The last job that ran was on the 28th of March. I can't seem to figure out how to get the timer service to process jobs again so the test server can handle incoming email/backups/etc.
Ok Just got off the phone from Microsoft Tech Support,
They have fixed it on my server after a couple of days trouble shooting and reviewing my server logs.
they got me to do the following:
from command prompt change directory to the following:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN
Then run the following command:
psconfig -cmd configdb -connect -server YourSQLServerHere -database SharePoint_Config -user DOMAIN\YourSystemAccountHere -password "YourPasswordHere"
That run 3 tasks.
Then I ran the "SharePoint Products and Technologies Configuration Wizard" from the AdminTools folder on the Server.
Accepted Warnings about services being stopped and and clicked next a couple of times, this ran a wizzard that did 8 tasks, afterwards gave a message saying successful.
Then Re-Started the "Windows SharePoint Services Timer" service on the server.
and Hurray!!!!!! Alerts and other Server jobs are working once again 
Thank you to the Microsoft Support Team that talked me through it, hope it helps you other guys with same problem.
Thanks for the information. Did they give you any information on why the issue occured/how to prevent it from occuring again?
I was able to get the timer service working again yesterday by going into the SharePoint logs, determing when the issue occured and delecting the job that had hung the timer. All of the other jobs that were backed up then processed. I still have no idea why the issue occured.
Apparently something happened on my SP2 installation, something to do with the Database connection was not being triggered when the jobs, the command re-maps the triggers. It was alittle over my head as am abit of a SharePoint newbie.
Will post the resolution and tech explanation when I recieve it from Microsoft Support, I have agreed my support case as closed so should get the summary in next couple of days.
