Error 14261 Log Shipping
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 7,2000 » Administration » Log shipping error? 14261 Log shipping error? 14261 Rate Topic Display Mode Topic Options Author Message Melissa KadiriMelissa Kadiri Posted Monday, April 12, 2004 10:22 AM SSC-Enthusiastic Group: General Forum Members Last Login: Saturday, November 15, 2008 1:08 PM Points: 177, Visits: 23 Trying to setup logshipping for one instance/database, and I keepgetting this error: "Error 14261: The specified primary_server_name.primary_db ('C') already exists". The error occurs immediately after the primary database is fully dumped forlog shipping initialization of the target. I am not even prompted for a login and password for the target instance. The database is not named "C".With SQL Enterprise, I have successfully setup logshipping for several databases (different instances) using the Database Maintenance Plan Wizard -- so the point-and-click method is very straightforward, and has been foolproof with this exception. The target instance/database name is definitely NOT the same as the primary instance/database name. I've tried this three times already, with the same error.Anyone have any ideas? Regards, Melissa Post #110758 Nicholas CainNicholas Cain Posted Monday, April 12, 2004 10:29 AM SSCrazy Group: General Forum Members Last Login: Wednesday, October 5, 2016 1:21 PM Points: 2,038, Visits: 6,198 It's a bug, you have to clean up the log shipping tables in msdb. Check out http://support.microsoft.com/default.aspx?scid=kb;en-us;298743&sd=tech Shamless self promotion - read my blog http://sirsql.net Post #110760 Melissa KadiriMelissa Kadiri Posted Monday, April 12, 2004 10:47 AM SSC-Enthusiastic Group: General Forum Members Last Login: Saturday, November 15, 2008 1:08 PM Points: 177,
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: SQL 2012 Log Shipping error 14261 SQL Server > SQL Server High Availability and Disaster Recovery Question 0 Sign in to vote I have two servers and I had log shipping working but could not add any additional databases to the process. I deleted all the log shipping and I am still unable to add the databases back to the log shipping configuration. The process fails while trying to all the Secondary Log shipping configuration. I get the following error: The specified @name ('Log shipping Primary Server Alert.') already exists. http://www.sqlservercentral.com/Forums/Topic110758-5-1.aspx (.Net SqlClient Data Provider) and it specifically refers to my secondary server by name in the error also referencing the stored procedure sp_verify_alert. I have not been able to find a solution. Please help. Thursday, March 19, 2015 4:39 PM Reply | Quote Answers 0 Sign in to vote I sincerely appreciate your help. I found the problem. There were two alerttasks (under the Alerts folder) which were residual to the https://social.msdn.microsoft.com/Forums/sqlserver/en-US/66186117-c07e-4c10-867d-b61f5b107961/sql-2012-log-shipping-error-14261?forum=sqldisasterrecovery process. I just deleted those Alert tasks and the error is gone and I can now recreate all my Log Shipping jobs. Proposed as answer by Michelle LiModerator Friday, March 20, 2015 6:45 AM Marked as answer by RKCLLC Friday, March 20, 2015 12:26 PM Thursday, March 19, 2015 7:24 PM Reply | Quote All replies 0 Sign in to vote Looks like you have to manually clean all log shipping information and also make sure drop all log shipping jobs http://www.databaseskill.com/3011872/ Edited by dave_gona Thursday, March 19, 2015 5:03 PM Thursday, March 19, 2015 4:57 PM Reply | Quote 0 Sign in to vote Thank you for your response. Is this true of SQL 2012 as well? It appears that this article only references SQL 2000. Thursday, March 19, 2015 5:07 PM Reply | Quote 0 Sign in to vote RKCLLC, not sure but looks like log shipping was not removed completely.Do you see any log shipping jobs? Are they removed successfully? Please make sure you have taken all database backups before performing anything. Edited by dave_gona Thursday, March 19, 2015 5:27 PM Thursday, March 19, 2015 5:24 PM Reply | Quote 0 Sign in to vote I deleted all the jobs using SQL Management Studio and no jobs
error 14261 joseph Guest Posts: n/a 11-19-2003 I ran into a problem when attempting to set up http://www.mssqlforums.com/log-shipping-error-14261-a-t270500.html Log Shipping and I aborted the process. Ever since, I cannot http://www.tek-tips.com/viewthread.cfm?qid=1514141 reestablish log shipping for the same database. When it tries to execute the first log shipping plan, it generates an error. The text of the error message is: Error 14261: The primary_server_name.primary_database_name ('C') already exists. Please help. Thanks. Joseph Guest error 14261 Posts: n/a 11-19-2003 You'll have to manually clean up the log shipping tables. I don't have it installed right now or my doc in front of me to tell yo uwhich one, but the uninstall process seems like it didn't clean itself up. >-----Original Message----- >I ran into a problem when attempting to set up error 14261 log Log Shipping >and I aborted the process. Ever since, I cannot >reestablish log shipping for the same database. When it >tries to execute the first log shipping plan, it generates >an error. The text of the error message is: >Error 14261: The primary_server_name.primary_database_name >('C') already exists. > >Please help. Thanks. > >Joseph >. > Luther Miller Guest Posts: n/a 12-08-2003 http://support.microsoft.com/default...b;en-us;298743 "joseph" <(E-Mail Removed)> wrote in message news:<008101c3aeb3$ba4551f0$(E-Mail Removed)>... > I ran into a problem when attempting to set up Log Shipping > and I aborted the process. Ever since, I cannot > reestablish log shipping for the same database. When it > tries to execute the first log shipping plan, it generates > an error. The text of the error message is: > Error 14261: The primary_server_name.primary_database_name > ('C') already exists. > > Please help. Thanks. > > Joseph « tempdb size | rebuild sql services; making an instance the default » Thread Tools
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Microsoft SQL Server: Setup and Administration Forum at Tek-Tips HomeForumsProgrammersDBMS PackagesMicrosoft SQL Server: Setup and Administration Forum Log Shipping error thread962-1514141 Forum Search FAQs Links MVPs Log Shipping error Log Shipping error djj55 (Programmer) (OP) 18 Nov 08 08:57 Hello, With SQL 2000 I am getting an error Quote:Error 14261: The specified plan_name ('DB1.MyDB_logshipping') already exists. One thing that I do not understand is the name I entered was LogShipping_MyDB.This was after I executed CODEexecute msdb..sp_delete_log_shipping_primary @primary_server_name = N'DB1', @primary_database_name = N'MyDB'execute msdb..sp_delete_log_shipping_plan @plan_name = 'MyDb_logshipping'execute msdb..sp_delete_log_shipping_plan @plan_name = 'DB1.MyDb_logshipping'The first said complete the last two said does not exist.I have created other log shipping today and they seem to be working.Any ideas?djj RE: Log Shipping error JayKusch (MIS) 18 Nov 08 21:09 Have you looked in the actual log shipping tables in the MSDB database to see if the plan does indeed exist? ThanksJ. Kusch RE: Log Shipping error djj55 (Programmer) (OP) 19 Nov 08 07:45 Thank you for the reply.I did look into any table that started 'log' or had 'plan' in the name.Nothing out of line, and no MyDB.So after getting your reply, I looked on the destination server and found it there (log_shipping plans).Thank you,djj RE: Log Shipping error JayKusch (MIS) 19 Nov 08 09:14 Great! ThanksJ. Kusch Red Flag This Post Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework. Cancel Red Flag SubmittedThank you for helping keep Tek-Tips Forums f