September 25, 2002 at 9:36 am
Setting: Windows 2000, Sql7, Sql Sp 3
One of our developers setup a nightly Sql Job that simply calls a stored procedure (the job was setup directly – it didn’t use the Database Maintenance plan). Last night the job failed and I can’t determine why. The error message is:
“1 of 125 (SQLSTATE 1000) (Message 0) 8010941180 2 of 0 (SQLSTATE 0100) (Message 0) 0810021797……. 9 of 9 (SQL STATE 01000) (Message 0 )……
What?
Jobs setup under the Database Maintenance Plan can send output reports to a selected file. But I don’t think this is an option for custom jobs.
1.How can I further track down the problem?
2.What can I do ahead of time so the next time it happens I can get more meaningful information on the problem?
TIA,
Bill
September 25, 2002 at 11:28 am
I assume this message is coming from "job history" "step details" information. The job history step details, don't always contain the real error. You might be able to use the "event viewer" to find out more information. But normally when I have this problem I modify the job so each step of the job writes output to a file. To do this you need to set an "Output file" under "Operation System Command (CmdExec) Command Options" option on the "Advanced" tab when editing the step.
Gregory Larsen, DBA
If you looking for SQL Server Examples check out my website at http://www.geocities.com/sqlserverexamples
Gregory A. Larsen, MVP
September 25, 2002 at 3:33 pm
If it's happening within a single step your best bet is to add some code to the proc to log its progress. Once you narrow down the failure point you can fix it if its easy to see, or add more debug/logging code to help you see exactly whats going on.
Andy
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply