We see this error semi regularly in our dev environments, its an easy fix, normally caused by the step running against a speficic database that no longer exists (or has been renamed)

The error message you see is like this:

AgentJobError01

And if you open up the job to the Step you’ll see that its Database to run from is empty

AgentJobError02

The solution of course is to re-select the relevant database to run the step against.

Advertisements