Go to your step and see what is the problem, sometimes it be login and others bad synatx. see the error and then change the required change on your step.
I hope this is helpful.
Please Mark it as Answered if it answered your question
OR mark it as Helpful if it help you to solve your problem
Elmozamil Elamir Hamid
- Proposed as answer by Papy NormandModerator Tuesday, April 10, 2012 9:17 PM
You have to check job history as first stop: right click on job in SSMS Object Explorer --> View History .
In addition you may have to check other error logs as well as Event Viewer.
Programmatic control of jobs article:
Since network interruption happened, ideally the job can be just restarted and will finish. The assumption is that the job has been designed to be rerunnable in case of network interruption. Restartability is a very important & desirable feature of production jobs. You don't want to do diagnostics and "repair" each time something happens. You just want to restart so it finishes.