Job fails when run automatically, succeeds manually

Last Post 26 Mar 2003 11:48 PM by FMR. 1 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
FMR
New Member
New Member

--
24 Mar 2003 11:49 PM
I have two nightly jobs that always show up as 'failed' after they have run automatically the night before (1 AM), but when I run them by hand they succeed. In più, when successful they each take between 15 and 20 seconds, but they run for slightly over a minute when they fail.

In the job history one is failing with this message

SQL Server does not exist or access denied. [SQLSTATE 42000] (Error 17). The step failed.

Does this refer to a remote server? I hope not because the stored procedure doesn't reference any remote server objects.

The other is failing, but the error message is unintelligible. It's comprised of the PRINT statements in the sp, with '... The step failed.' At the end.

An ideas about what might be happening here?

Thanks, Jason.
FMR
New Member
New Member

--
26 Mar 2003 11:48 PM
Thanks Rich for the reply. After following up a few fruitless leads, I stumbled across what was going wrong. Deep in the job (about 6 or 7 levels down) we were calling an extended stored procedure on a test box that was being shut down at night. Now it makes perfect sense why it didn't work at 1 AM, but worked fine at 9 AM!

Thanks again for your help, Jason.
You are not authorized to post a reply.

Acceptable Use Policy