We run numerous scheduled jobs using MS SQL 2005 job scheduler.
Over the past few weeks, we've been witnessing that a running job will simply STOP and will not record any history in the Log File Viewer.
What appears to be happening is that the server will start a job and record these steps into msdb. At a random step during a job, the server will stop running the job and it records no error. This silent failure prevents a "Step 0" record from being created and we won't see anything in the Log File Viewer.
Anyone else experience this?