Job stopped running when it is set to automatically execute with no end date

Question

0.00/5 (No votes)

See more:

SQL-Server-2012

Hi. I am having a little problem here and I hope someone can help me.
I created an automatic job in MS SQL Server 2012 R2 and the said job was set to run until NO END DATE.. And in my shock, the job last ran on May 19. It has been almost a month and I just noticed that it did not run. It even does not have a history after May 19 to see the error message in case it failed. Please help.

What I have tried:

I tried viewing the logs but no luck because there is no history of this specific job since it stopped. The last run was successful.
And I dont think it is because of the disk space because other jobs from the same server runs perfectly even the daily back up job.

Posted 5-Jun-17 20:50pm

bjay tiamsic

Updated 22-Jun-17 4:19am

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Debasis_Saha · Answer 1 · 2017-06-22T04:19:00

Solution 1

If other job on the server is running properly as per schedule, then check your job may be in disabled mode. Or either check your SQL Server Agent may stop at the schedule time of the Job.

Posted 22-Jun-17 4:19am

Debasis_Saha