Hi,
We are using a sql job to copy log files to a standby server using
robocopy. Often times the sql job status reports a failure however
robocopy itself reports the file copy was successful.
Has anyone run into this before. I would like to find out why these jobs
are reporting failures as they a sending out an aweful lot of notifications.
Thanks
DilanI assume you are using Agent and CmdExec jobsteps? Agent uses the return cod
e from the process you
start to determine whether the execution was successful or not. If the proce
ss (RoboCopy) returns
anything different from 0, you will get failure of that job step. So you nee
d to determine why
RoboCopy returns such a return code. I presume that RoboCopy returns proper
error messages, so just
define an output file for the job step and check there for the error message
s from RoboCopy.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Dilan A" <dilan.a@.youtelus.net> wrote in message news:GnXTf.8832$A4.8081@.clgrps12...seagreen">
> Hi,
> We are using a sql job to copy log files to a standby server using robocop
y. Often times the sql
> job status reports a failure however robocopy itself reports the file copy
was successful.
> Has anyone run into this before. I would like to find out why these jobs a
re reporting failures as
> they a sending out an aweful lot of notifications.
> Thanks
> Dilan
No comments:
Post a Comment