Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

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?

share|improve this question
    
Can you give more details about the steps? –  ggponti Jul 2 '10 at 13:43
    
Afraid I cannot. It is random and we haven't experienced this in several weeks. I thought server load was contributing to this, but cannot find a repeatable pattern. –  Brett Veenstra Jul 10 '10 at 19:31
add comment

3 Answers 3

Try this method to get some more details on what the job is doing:

In SQL Server Management Studio:

  1. Connect to the instance
  2. Expand SQL Server Agent
  3. Expand Jobs
  4. Right-click on the job and view properties
  5. In the Advanced window, specify an output file
  6. Run the job and post the file contents (if any)
share|improve this answer
add comment

Never experienced this behavior.

Is this any running job under SQL Agent or a particular one? Anything remarkable in the SQL log or application or system event logs? You can see the recorded steps in msdb? What about starting Profiler, starting your job and examining the Profiler output?

share|improve this answer
add comment

I always always always (get the idea :) ) ...always direct the output of each step of every job to a text file somewhere on the server. This is ideal for these kind of scenarios.

step 1 I set for the output file to overwrite and every subsequent step I step to append to that same file.

...and I ensure this is done on each and every job to a standard output location. There is stuff that is outputted that sometimes doesnt usually make it into job history but will into a text file.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.