May 17, 2013 at 6:51 am
Hi all,
All the jobs were running fine except for the past two days. I don't know what happened. Two days before my server date was changed automatically(from 2013 to 2032) after that it seems to be not working.
Kindly help me . I am not able to find exact reason also.
Thanks,
Devanand.
May 17, 2013 at 7:32 am
Strange things are going on with your DB. Are your jobs have an end date specified?
Have to changed the date back to original?
Are there anything in SQL Server/ Agent error log, which you can post.
May 17, 2013 at 7:42 am
Here is the Service agent log:
Message
Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 198.204.235.42]
Error: 18456, Severity: 14, State: 8.
May 17, 2013 at 7:44 am
Continue to the previous reply. My sa password is correct .I have scheduled the jobs using sa account only.
May 17, 2013 at 7:57 am
First thing.. running SQL Agent service with sa account is not a good practice.
Also this error is not SQL agent error. It is from some application trying to access the DB.
Are you able to run that job manually?
May 17, 2013 at 8:01 am
Yes I can run it manually. Can u guide me where I can check the errors which you are asking.
May 17, 2013 at 8:13 am
SQL Server Agent--> Error Logs.
May 17, 2013 at 8:21 am
LogSQL Server Agent (Current - 5/16/2013 11:45:00 PM)
Message
Error symbol:
[364] The Messenger service has not been started - NetSend notifications will not be sent
Info symbol:
[129] SQLSERVERAGENT starting under Windows NT service control
Warning symbol :
[260] Unable to start mail session (reason: No mail profile defined)
Warning symbol:
[396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
May 17, 2013 at 8:32 am
You can ignore this error. This is not related to you job not running.
Can you try one thing drop and re-create your job and see if it starts running as scheduled. You can create one test job to run in 1 min to test if it is running successfully.
May 17, 2013 at 10:53 am
I have created a test job.It doesn't run. Can I reschedule all of my jobs again to the same time?
May 17, 2013 at 10:58 am
devanandiiway (5/17/2013)
Hi all,All the jobs were running fine except for the past two days. I don't know what happened. Two days before my server date was changed automatically(from 2013 to 2032) after that it seems to be not working.
Kindly help me . I am not able to find exact reason also.
Thanks,
Devanand.
Looking at this again, you say the date got changed to 2032. Was it changed back? Had all the jobs run while the date was 2032? Have you looked at the next schedule date for the jobs? You may just need to reschedule the jobs to get them working again.
May 17, 2013 at 11:02 am
After the date was changed to 2032 , scheduled jobs did run no issues. After changing the date to 2013 it doesn't .How to check the next schedule?
May 17, 2013 at 11:09 am
devanandiiway (5/17/2013)
After the date was changed to 2032 , scheduled jobs did run no issues. After changing the date to 2013 it doesn't .How to check the next schedule?
In the Oject Explorer, expand SQL Server Agent, right click on Job Activity Monitor, clink View Job Activity. Look at the Next Run column.
May 17, 2013 at 11:17 am
Yes the next run is scheduled to 2032. How can I change things back to normal.
May 17, 2013 at 11:22 am
devanandiiway (5/17/2013)
Yes the next run is scheduled to 2032. How can I change things back to normal.
Using the same tool. Go through the properties of each job and reschedule them to when they need to run next.
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply