log shipping not working

hello, on the destination server he says the restore job has failed
and my log shipping databases are then out of sync. where do i begin
to find out why my log shipping is no longer working? my two servers
are in differnet locations but i can ping and returns are under 50ms.
help?
thanks
APAP
Is it one log it has failed to apply or several? Sometimes
one log may fail to apply for a number of reasons. Next
time the target server tries to apply the logs it should
try to apply all logs since it last applied one. Quite
often it can catch up.
One common reason for log shipping failure is having the
restore on the target run too soon after the backup on the
source. Occasionally the restore tries to run before the
backup finishes. This may be because a big work load on
the source has caused a larger than normal log. It may be
the servers have got out of sync time wise.
Hope this helps
John|||thanks you john, it looks to me that the log shipping has never worked
since the backup was restored in the destincation server. these is a
small database like 63 mb so backup times is quick. each site has a
t1 or faster.
how do i get them back to sync?
AP
"John Bandettini" <anonymous@.discussions.microsoft.com> wrote in message news:<0ec801c3aa02$82d32cc0$a401280a@.phx.gbl>...
> AP
> Is it one log it has failed to apply or several? Sometimes
> one log may fail to apply for a number of reasons. Next
> time the target server tries to apply the logs it should
> try to apply all logs since it last applied one. Quite
> often it can catch up.
> One common reason for log shipping failure is having the
> restore on the target run too soon after the backup on the
> source. Occasionally the restore tries to run before the
> backup finishes. This may be because a big work load on
> the source has caused a larger than normal log. It may be
> the servers have got out of sync time wise.
> Hope this helps
> John|||Antonio
You will need to copy a recent full backup to your standby
server, to re-establish the log shipping.
I don't have a copy of Enterprise edition that I can look
at at the moment to see exactly how you do it. There
should be an option somewhere to re-establish it.
The fact that it has never worked suggests there is a
problem anyway. Permissions on the share on the target
server is quite a common problem. Use 'xp_cmdshell' on
your source database to check the permissions work. (Do
a 'dir' on it).
Also worth having a look at this link.
http://support.microsoft.com/default.aspx?scid=kb;en-
us;323135
Hope this helps
John|||thank you again. i did check permissions. i see on teh source and
destination server where the transaction logs are that all are on both
servers so i see this to mean that the logs are baccking up on the
source server good and they are being transmisssion to the destination
server good. it looks to me that the logs are shipping ok but not
being replayed on the destination server.
this probably changes your recommentations.
what do you think about it now?
thanks
AP
"John Bandettini" <anonymous@.discussions.microsoft.com> wrote in message news:<0adc01c3aac4$4e192ad0$a501280a@.phx.gbl>...
> Antonio
> You will need to copy a recent full backup to your standby
> server, to re-establish the log shipping.
> I don't have a copy of Enterprise edition that I can look
> at at the moment to see exactly how you do it. There
> should be an option somewhere to re-establish it.
> The fact that it has never worked suggests there is a
> problem anyway. Permissions on the share on the target
> server is quite a common problem. Use 'xp_cmdshell' on
> your source database to check the permissions work. (Do
> a 'dir' on it).
> Also worth having a look at this link.
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;323135
> Hope this helps
> John|||Antonio
Last thing I can think of suggesting is to try running the
SQL Server agent as a local domain account with the same
name and password on both servers.
I have seen this work.
Regards
John