November 2, 2006 at 7:31 am
I have a multi server database backup job. One of the target servers is failing to run the job, and I can't see why. How can I log the output of a target server's job to a file (the log file option is disabled)?
Thanks.
November 2, 2006 at 8:36 am
Right click the job in EM and choose ViewJobHistory
Vasc
November 2, 2006 at 9:20 am
All that tells me is the last step to run, it doesn't give me any details of why it is failing......I need to be able to right the errors to a log file, like I can for single server jobs.
November 2, 2006 at 12:45 pm
To view the job history
Also check in right upper corner ShowStepDetails
Vasc
November 2, 2006 at 2:11 pm
thanks for the suggestion, but this is all that I see "sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed." for the reason.......the job backs up the database fine, but we can't find why it is failing every once in a while.....any suggestions?
November 2, 2006 at 2:24 pm
Normally, the information from the job history is not enough. I would like to recommend you add an output file in your job.
Open the properties of your desired job;
Goto Edit;
Click Advanced tab;
You will not miss it (output file).
November 2, 2006 at 2:55 pm
That's what I was wanting to do originally, but on a job that comes from a multi server job, you can not get it to go to an output file.....the outfile feature is disabled.
November 3, 2006 at 9:53 am
The error: [SQLSTATE 42000] (Error 22029) is kind of generic and kind of not. It may be a login/authentication error. You may want to check the system event logs on the target server for the time to get a better clue as to what is going on.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy