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 |
|
cddot
Starting Member
37 Posts |
 Posted - 2009-05-22 : 04:43:19
|
| I have a CmdExec job setup as an Agent job. The job runs just fine as it is producing the output I am expecting.However, in the Job History, the job is reported as an a FAILED job. The On success/failure action settings are defaults, so it should report success for successful actions.For some reason, it is reporting the jobs as failures. Any suggestions?SQL Server 2005 |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2009-05-22 : 04:51:46
|
| whats the job doing? can you check if all the steps in job were success? |
 |
|
|
cddot
Starting Member
37 Posts |
Posted - 2009-05-22 : 05:00:04
|
| I ran the same job in a command window. It runs successfully and produces the right results. There are no errors. |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2009-05-22 : 05:06:25
|
| what does it show as reason for failure? |
|
|
|
cddot
Starting Member
37 Posts |
Posted - 2009-05-22 : 05:13:48
|
| That's the thing - there is no reason for failure. It simply says: Executed as user: XXX/YYY. The step failed.I think I've found the reason. The executable in the cmd file is returning a non-zero ERRORLEVEL code even when the job is a success. Case closed. :) |
|
|
|
|
|
|
False Agent Job message