Log Shipping not Loading TRN file

I cannot get Log Shipping to work. It does not give any outward
errors. Everything seams to work correctly except the secondary server
is not picking up the Transaction logs and applying them. The TRN
files are being written to a shared directory on the primary server as
scheduled.
I tracked down the following error on the scecondary server from the
Log Shipping copy job.
Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
Copyright (C) Microsoft Corporation, 1995 - 1998
Logged on to SQL Server 'DATABASE2\Dev'
as 'NT AUTHORITY\SYSTEM' (trusted)
[Microsoft SQL-DMO (ODBC SQLState: 28000)] Error 18452:
[Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user '(null)'. Reason: Not associated with
a trusted SQL Server connection.
Starting copy for plan DATABASE1\Dev.CMX_Dev_logshipping
Source database - CMX_Dev
Copied 0 files
Finished copy for plan DATABASE1\Dev.CMX_Dev_logshipping
I have two Enterprise SQL Server 2000 machines (Database1 &
Database2). They are not part of any domain. They both are running
SQL Server and Agent under the identical user which has Administration
priviledges. Both machines can see the shared drive and have full
access. The shared drive is on Database1 and Database1 is also
currently the monitoring server.
Any suggestions would be appreciated...
ThanksCalvin,
I have a related problem (the destination server is in a disaster site
without any domain)
It seems the Windows account who creates and runs the logshipping has
sa access on the destination server
The error suggest you were able to create a login on the destination
server for the user SYSTEM on local domain (=machine) NT AUTHORITY
(this is what a plan to do, but since I cannot browse the domain of
the primary server I plan to fiddle with the host file
Did you assign administrator role to this login ?
HTH
Jan Waumans
On 6 Apr 2004 13:46:10 -0700, CalvinNSlater@.Hotmail.com (Calvin
Slater) wrote:

>I cannot get Log Shipping to work. It does not give any outward
>errors. Everything seams to work correctly except the secondary server
>is not picking up the Transaction logs and applying them. The TRN
>files are being written to a shared directory on the primary server as
>scheduled.
> I tracked down the following error on the scecondary server from the
>Log Shipping copy job.
> Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
> Copyright (C) Microsoft Corporation, 1995 - 1998
> Logged on to SQL Server 'DATABASE2\Dev'
> as 'NT AUTHORITY\SYSTEM' (trusted)
> [Microsoft SQL-DMO (ODBC SQLState: 28000)] Error 18452:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login
> failed for user '(null)'. Reason: Not associated with
> a trusted SQL Server connection.
> Starting copy for plan DATABASE1\Dev.CMX_Dev_logshipping
> Source database - CMX_Dev
> Copied 0 files
> Finished copy for plan DATABASE1\Dev.CMX_Dev_logshipping
>
>I have two Enterprise SQL Server 2000 machines (Database1 &
>Database2). They are not part of any domain. They both are running
>SQL Server and Agent under the identical user which has Administration
>priviledges. Both machines can see the shared drive and have full
>access. The shared drive is on Database1 and Database1 is also
>currently the monitoring server.
>Any suggestions would be appreciated...
>Thanks