xo55ox (xo****@hotmail.com) writes:
We did set up a separated account as the standby server for the
production box. But my job is still failing. This time, in my log, it
reported
'Logon failure: unknown user name or bad password'.
I tried to use the sql server user account as well as the OS user
account to run the job. Both are failing.
Am I missing something on the user account configuration, on the
linked server configuration or something else?
I have to admit that I don't have full knowledge how this works, and I
don't really have good playground to test things on myself. But I try to
work from common sense.
1) You never said as what kind of job step you ran the xcopy command.
I assume that you use CmdExec and not a T-SQL job?
2) First of all the service account for SQL Server Agent must have
access to that other partition. I don't really know whether know
whether the job owner has any importance for CmdExec, but if the
service account does not have access to the disk itself, it should
not be able to get there through impersonation either, methinks.
3) Rather than referring to c$, set up a real sbare, and grant permissions
to that share to the user(s) involved.
This may be more of a Windows networking issue than an SQL issue.
--
Erland Sommarskog, SQL Server MVP,
so****@algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp