Calling Stored procedures via the Job Agent - Please help!

Hi all,
My colleague and I are struggling with a rather annoying problem. The
situation is as follows:
We've two database servers (one primary and one backup) with
SQL-server 2000 installed. We've been trying to implement
"log-shipping" on this server using the example scripts from the SQL
server 2000 resource kit. What happens in these scripts is basically
the following.
Server A: starts the (local) stored procedure (sproc) sp_logship
Server A: sp_logship copies the transactionlog into a shared location,
so Server B is able to reach the transactionlog.
Server A: calls a sproc on Server B.
Server B: The sproc looks for a transactionlogfile in the shared
location and restores Server B's database using this logfile.
This mechanism works fine when we call "sp_logship" from the
Query-analyzer on Server A.
When we try to run start the "sp_logship" using the Job Agent (also on
Server A), we get the following error:
Msg 7410, sev 16: Remote access not allowed for Windows NT user
activated by SETUSER [SQLSTATE 42000]
We tried to solve this problem by creating several other users, even
ones who use SQL server Authentication. It was to no avail.
I hope someone can help me with this problem,
Thank you very much in advance,
Alke WiebengaIs the SQL Server Agent startup account a domain one with permission to
access the shared folder in both servers?
AMB
"A. Wiebenga" wrote:

> Hi all,
> My colleague and I are struggling with a rather annoying problem. The
> situation is as follows:
> We've two database servers (one primary and one backup) with
> SQL-server 2000 installed. We've been trying to implement
> "log-shipping" on this server using the example scripts from the SQL
> server 2000 resource kit. What happens in these scripts is basically
> the following.
> Server A: starts the (local) stored procedure (sproc) sp_logship
> Server A: sp_logship copies the transactionlog into a shared location,
> so Server B is able to reach the transactionlog.
> Server A: calls a sproc on Server B.
> Server B: The sproc looks for a transactionlogfile in the shared
> location and restores Server B's database using this logfile.
> This mechanism works fine when we call "sp_logship" from the
> Query-analyzer on Server A.
> When we try to run start the "sp_logship" using the Job Agent (also on
> Server A), we get the following error:
> Msg 7410, sev 16: Remote access not allowed for Windows NT user
> activated by SETUSER [SQLSTATE 42000]
> We tried to solve this problem by creating several other users, even
> ones who use SQL server Authentication. It was to no avail.
> I hope someone can help me with this problem,
> Thank you very much in advance,
> Alke Wiebenga
>