Monica,
Under what account is this job running? And what version of SQL Server?
If the account is not a sysadmin, then the SQL Agent Proxy account will be
used. (In a SQL Server 2000 server that was upgraded to SQL Server 2005, you
may see a proxy named UpgradedProxyAccount that uses UpgradedProxy.)
If this account does not have rights to write to the directory, the job will
run, but you will get the error.
If I remember correctly, a non-sysadmin in SQL Server 2000 cannot write to a
file. (But test it and see.) If that is the case, another option is to
check Append Output to Step History, which would allow you to see the output
using Enterprise Manager, going to the Job Step Advanced tab and pressing
View.
RLF
> Hello,
>
[quoted text clipped - 12 lines]
>
> Can anyone give any ideas to fix this?
Monica - 09 Jul 2008 15:38 GMT
I am using SQL 2000. I changed the user to SA and it worked.
Thanks for your advice.
> Monica,
>
[quoted text clipped - 31 lines]
> >
> > Can anyone give any ideas to fix this?