Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mike123
Master Smack Fu Yak Hacker
1462 Posts |
 Posted - 2005-06-30 : 06:09:23
|
| what could be the cause of a job starting to fail seemingly out of nowhere? I haven't made any changes in quite some time and there is no real description of what happened in the event log rather than "job failed"any suggestions?Thanks again!mike123 |
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2005-06-30 : 07:44:50
|
| Look at the job history by right-clicking on the job in the list.-------Moo. :) |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-06-30 : 16:29:35
|
| Then after you are in job history, check the box to show the details. Post the error here.Tara |
|
|
|
mike123
Master Smack Fu Yak Hacker
1462 Posts |
Posted - 2005-06-30 : 19:16:42
|
| Thanks for the tip, didnt know about that option. Here is what I have found. The jobs are database Integrity checks etc (created with wizard)The job failed. The Job was invoked by Schedule 5 (Schedule 1). The last step to run was step 1 (Step 1).sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failedthanks again!mike123 |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-06-30 : 19:47:16
|
| Good old maintenance plans! Don't you love it: "sqlmaint.exe failed"? It's kind of like the Unknown error that you get from DTS packages. Now how am I supposed to troubleshoot it if you (DTS package or maintenance routine) don't give me a clue?What options were selected in the wizard for the Integrity checks page?Check the SQL Server Error Log for the error as to why the Integrity check failed. I betcha you selected the option in the plan to repair minor problems. That option should NEVER be selected. Only a DBA should be performing that task and not some scheduled maintenance job. Anyway, in order for it to do that, it must put the database in single user mode. So someone was probably connected when the job kicked off. If that's not the case, then run DBCC CHECKDB for each of the databases inside Query Analyzer. Does it error? If it does, you've got problems. Post the errors.Tara |
|
|
|
|
|
|
causes of a job failing