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 |
|
patshaw
Posting Yak Master
177 Posts |
 Posted - 2007-10-29 : 07:33:29
|
| For the last 4 days an automated job has been failing with the following error:'Unable to open Step output file. The step failed.'Does anyone know what this means? |
|
|
patshaw
Posting Yak Master
177 Posts |
Posted - 2007-10-29 : 08:12:31
|
| I've sorted this out. If you open the job step and go to Edit you can specify the output file for the job. By default this is blank but a rogue path had found it's way into this one. As the path couldn't be found it failed the job (typical Microsoft).Pat. |
 |
|
|
KenW
Constraint Violating Yak Guru
391 Posts |
Posted - 2007-10-30 : 14:09:35
|
quote:
Originally posted by patshaw
I've sorted this out. If you open the job step and go to Edit you can specify the output file for the job. By default this is blank but a rogue path had found it's way into this one. As the path couldn't be found it failed the job (typical Microsoft).Pat.
What "typical Microsoft"? Do you mean that the job failed because some dumbass at your machine added an invalid path, and so SQL Server (correctly) didn't run because it couldn't use the configuration provided by that dumbass?Typical /. post, Pat. Bashing MS because you couldn't do something right. |
|
|
|
|
|
|
ERROR: Unable to open Step output file.