reasons why a scheduled job may not have run

the instance is online and the dbs also..

but the job which is scheduled to run has not run..

the schedule is enabled too..
the agent is running...

what else could be wrong?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott PletcherSenior DBACommented:
Is the job enabled?

Was the job already running?  SQL will only run one instance of a given job at a given time.  If the job is already running, the start is ignored.
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
The job is not enabled
The checkbox to 'run only when the user is logged in' is checked, and the user is not logged in
The user that runs the job does not have privs on that job/some object that the job calls
The job timer is set to a time that either hasn't happened yet, or was in the past
The batch file that you're executing has a typo where it is not running whatever you want it to run
The job did run and threw an error (if this is a .bat, add & PAUSE to the end of the bat, and manually execute to view the results)
The job did run and nothing happened, as designed
The job did run and is not leaving any evidence that it ran
The job is pointing to a different server / database / folder / whatever that you are expecting
Are the credentials correct?  Any information in the event logs?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
25112Author Commented:
thanks for the helpful pointers..

it helped to revisit every step..

what it was that even though the agent 'seemed' to be running.. it was (had) stopped somehow.. (that is another issue)..
i restarted the agent and the scedhuled job picked up..

thanks again.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.