Article ID: 917544 - View products that this article applies to.
Bug #: 352828 (SQL Server 8.0)
When the "Log Shipping Alert Job - Restore" job runs in Microsoft SQL Server 2000, you may receive an error message that resembles the following:
Msg 14421, Sev 16: The log shipping destination SecondaryServerName is out of sync by NumberOfMinutes minutes
This problem occurs when the following conditions are true:
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.Microsoft regularly releases software updates to address specific bugs. If Microsoft releases a software update to resolve this bug, this article will be updated with additional information.
To work around this problem, use a single monitor server for log shipping pairs that have different primary servers but the same secondary servers.
For more information about log shipping, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/292586/ )Backup, copy, and load job information is not updated on the log shipping monitor
(http://support.microsoft.com/kb/314515/ )Frequently asked questions - SQL Server 2000 - Log shipping
(http://support.microsoft.com/kb/323135/ )Microsoft SQL Server 2000 - How to set up log shipping (White paper)
Article ID: 917544 - Last Review: November 2, 2007 - Revision: 1.3