Article ID: 298743 - Last Review: February 22, 2007 - Revision: 2.5 BUG: All Changes May Not be Rolled Back when Log Shipping Maintenance Wizard FailsThis article was previously published under Q298743 BUG #: 353349 (SHILOH_BUGS) BUG #: 353719 (SHILOH_BUGS) SYMPTOMS When you set up log shipping through the Database
Maintenance Wizard, and the wizard fails to complete because of an error, not
all of the wizard's changes are rolled back. This may cause the following error message to occur after you fix the original problem, and then re-run the wizard: Error 14261: The specified
primary_server_name.primary_database_name ('N') already exists. Error 14426: A log shipping monitor is already defined (...) CAUSE There are left over jobs on the log shipping monitor server
and on the primary server:
WORKAROUND After you run the Maintenance Wizard and it fails to create
the Log Shipping setup, you must manually clean up the tables before you run
the wizard again. Depending on where the failure is, you must run some of the stored procedures to delete the entry. You may have to run the following stored procedures to clean up log shipping entries and allow the wizard to be re-run:
STATUS Microsoft has confirmed this to be a problem in SQL Server
2000. REFERENCES For more information, visit the following Microsoft Web
sites: Microsoft SQL Server 2000 Resource Kit (http://www.microsoft.com/mspress/books/toc/4939.aspx) ; Chapter 13 Support WebCast: Microsoft SQL Server 2000 Log Shipping (http://support.microsoft.com/kb/325220) SQL Server 2000 Books Online (http://www.microsoft.com/downloads/details.aspx?familyid=a6f79cb1-a420-445f-8a4b-bd77a7da194b)
| Article Translations
|
Back to the top
