log shipping error message

hi,
We set up a log shipping job on our control server for one
of our sql servers and its fail-over server. We keep
getting these kind of job failures from time to time:
'The job failed. The Job was invoked by Schedule 12 (Log
Shipping Alert Job - Restore). The last step to run was
step 1 (Log Shipping Alert Job - Restore).
Executed as user: domainName\ControlServerName. The log
shipping destination fail_overServerName.databaseName is
out of sync by 30 minutes. [SQLSTATE 42000] (Error 14421)
Associated statement is not prepared [SQLSTATE HY007]
(Error 0). The step failed.'
What does this 'Associated statement is not prepared' mean?
many thanks.
JJJJ,
You might experience these symptoms if you configured primary or secondary
servers (or both) to connect to the monitor server by using SQL Server
Authentication on a computer that is running SQL Server 2000 Service Pack 2
(SP2)
To resolve this problem, obtain the latest service pack for Microsoft SQL
Server 2000.
SQL Server 2000 Service Pack 3a (SP3a) is available from the following
Microsoft Web site: http://www.microsoft.com/sql/downloads/2000/sp3.asp
To work around this problem, click the Use Windows Authentication option in
the Specify the Log Shipping Monitor Server Information dialog box during
log shipping Setup.
Background info for Error 14421 follows:
By definition, message 14421 does not necessarily indicate a problem with
Log Shipping. This message indicates that the difference between the last
backed up file and last restored file is greater than the time selected for
the Out of Sync Alert threshold.
There are serveral reasons why the alert message is raised. The following
list includes some of these reasons:
1.. The date or time (or both) on the primary server is modified such that
the date or time on the primary server is significantly ahead between
consecutive transaction log backups.
2.. The log shipping Restore job that is running on the secondary server
cannot connect to the monitor server msdb database to update the
log_shipping_secondaries table with the correct value. This may be the
result of an authentication problem between the secondary server and the
monitor server.
3.. You may have set an incorrect value for the Out of Sync Alert
threshold. Ideally, you must set this value to at least three times the
frequency of the slower of the Copy and Restore jobs. If the frequency of
the Copy or Restore jobs is modified after log shipping is set up and
functional, you must modify the value of the Out of Sync Alert threshold
accordingly.
4.. Problems either with the Backup job or Copy job are most likely to
result in "out of sync" alert messages. If "out of sync" alert messages are
raised and if there are no problems with the Backup or the Restore job,
check the Copy job for potential problems. Additionally, network
connectivity may cause the Copy job to fail.
5.. It is also possible that the Restore job on the secondary server is
failing. In this case, check the job history for the Restore job because it
may indicate a reason for the failure.
--
Keith Wilson
This posting is provided "AS IS" without express or implied warranty,
guarantee, or rights.
"JJ Wang" <anonymous@.discussions.microsoft.com> wrote in message
news:05b001c3b2f4$44286c10$a501280a@.phx.gbl...
> hi,
> We set up a log shipping job on our control server for one
> of our sql servers and its fail-over server. We keep
> getting these kind of job failures from time to time:
> 'The job failed. The Job was invoked by Schedule 12 (Log
> Shipping Alert Job - Restore). The last step to run was
> step 1 (Log Shipping Alert Job - Restore).
> Executed as user: domainName\ControlServerName. The log
> shipping destination fail_overServerName.databaseName is
> out of sync by 30 minutes. [SQLSTATE 42000] (Error 14421)
> Associated statement is not prepared [SQLSTATE HY007]
> (Error 0). The step failed.'
> What does this 'Associated statement is not prepared' mean?
> many thanks.
> JJ
>