Jobs Not Firing Due to System Time Having Wrong Time 1

[JohnBates]

hi all,

When I arrived at work this morning, I discovered the time on the server 12 hours ahead of actual time (someone accidentally flipped AM to PM yesterday on that server).

So several jobs ran 12 hours earlier than they should have.

Even after correcting the system time and stopping/restarting the Agent, jobs are not firing at their scheduled times. SQL Server apparently says "hey, I've already ran that job today."

I suppose this situation will automatically correct tonight after 9 pm which was the time it had when I reset the time to 9 AM this morning.

Does anyone know of a way that I can force SQL Server to start running jobs on schedule - or will I have to wait until the time rolls past 9 pm tonight?

As I reread this it hardly makes sense, but I think you get my question.

Thanks, John

 

[ptheriault]

>>Even after correcting the system time and stopping/restarting the Agent, jobs are not firing at their scheduled times. SQL Server apparently says "hey, I've already ran that job today."

That is correct.

You could try deleting the job history in the msdb.dbo.sysjobhistory table.

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[mrdenny]

You would need to change the msdb.dbo.sysjobs table and update the next run time and last run time columns with dates and times which have already past (in the correct format).

Backup msdb first just in case.

And beat who ever made the change.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com