May 28, 2013 at 12:09 pm
One of my jobs stopped running. The job is enabled but the next run date in the Job Activity Monitor is in the past. The next run date is 5/20/2013 11:58:00 PM
The schedule has no end date. The frequency is daily every 5 minutes between 1:08 AM and 11:59:59 pm.
I did notice the owner was my account. I switched this to sa. Could this have been the problem? I believe the password on the account was expiring sometime in that time frame.
Mysterious. I almost expect that if I create a new schedule the job will start running. I am on
Version is Microsoft SQL Server 2005 - 9.00.4060.00 which I believe is SP3.
Any thoughts?
May 28, 2013 at 10:09 pm
Possible i faced one with same scenario as my account locked that time.
I changed it to a service account it is fine now but you have to run once manually.
Regards
Durai Nagarajan
May 28, 2013 at 10:22 pm
durai nagarajan (5/28/2013)
Possible i faced one with same scenario as my account locked that time.I changed it to a service account it is fine now but you have to run once manually.
That is because it was past its scheduled run time. This is what can also happen when the clocks go from 01:59:59.9999999 to 03:00:00.0000000 when shifting to day light savings time. It never hits 02:00:00.00000000.
May 28, 2013 at 10:35 pm
perfect lynn, i got it and i never faced it during daylight savings shift.
Regards
Durai Nagarajan
May 29, 2013 at 8:21 am
I deleted and recreated the schedule and its running fine now. It may have been my account nearing its password expiration but I have other jobs with the same account and had no problems with them. I still should change the owner of these jobs over to sa.
May 30, 2013 at 9:18 am
Create separate account without PW policy applied, use this account as owner of all the jobs will fix these issue. Make sure OS updated with daylight savings. Hope this helps
May 30, 2013 at 2:07 pm
Although the job was enabled, perhaps the schedule was not enabled ? Since you deleted the schedule, you cannot find the answer now.
May 30, 2013 at 3:45 pm
I took a screenshot before deleting. Attached.
May 30, 2013 at 4:23 pm
I am seeing this in my logs.
I wonder if ConnUpdateStartExecutionDate is the process which updates the next run date, it failed and thus my next run date was in the past...
05/30/2013 12:02:12,,Error,[382] Logon to server '(local)' failed (ConnUpdateStartExecutionDate)
05/30/2013 12:02:12,,Error,[165] ODBC Error: 0<c/> Unable to complete login process due to delay in opening server connection [SQLSTATE 08001]
05/30/2013 12:02:07,,Error,[382] Logon to server '(local)' failed (ConnUpdateStartExecutionDate)
05/30/2013 12:02:07,,Error,[382] Logon to server '(local)' failed (ConnUpdateStartExecutionDate)
05/30/2013 12:02:07,,Error,[165] ODBC Error: 0<c/> Unable to complete login process due to delay in opening server connection [SQLSTATE 08001]
05/30/2013 12:02:07,,Error,[165] ODBC Error: 0<c/> Unable to complete login process due to delay in opening server connection [SQLSTATE 08001]
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply