Error 14261 The Specified

(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)  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. (.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 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 | Quot

SQL Server experts to answer whatever question you can come up with. Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums. SQL Server Forums Profile | ActiveTopics | Members | Search | ForumFAQ Register Now and get your question answered! Username: Password: Save Password Forgot your Password? All Forums Old Forums CLOSED - General SQL Server Error while setting https://social.msdn.microsoft.com/Forums/sqlserver/en-US/66186117-c07e-4c10-867d-b61f5b107961/sql-2012-log-shipping-error-14261?forum=sqldisasterrecovery up Log Shipping Forum Locked Printer Friendly Author Topic shahab03 Starting Member USA 28 Posts Posted-06/13/2006: 17:13:33 I am getting following error when setting up log shippingError 14261: The specified @name ('Log Shipping copy for NIMMAIN.vanxdb_logshipping') already exists. I have cleaned up all the log shipping related tables in msdb database on primary, secondary http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=67729 and monitoring sql server instances but I am still getting this error.Where else do I need to l look? or do? tkizer Almighty SQL Goddess USA 38200 Posts Posted-06/13/2006: 17:43:35 Was the maintenance plan deleted as well as the jobs?Each time the wizard fails, you must manually clear out the tables, so go back and make sure that all log_shipping* tables have been cleared out of all 3 instances.Tara Kizeraka tduggan shahab03 Starting Member USA 28 Posts Posted-06/14/2006: 09:23:50 Hello TaraThere were couple of jobs which were not deleted. Didnt have any problem after deleting them.By the way have you successfully performed a Log Shipping Role Change? Documentation is doesnt cover every aspect. ThanksShahab tkizer Almighty SQL Goddess USA 38200 Posts Posted-06/14/2006: 13:09:52 I have never successfully performed a log shipping role change. We tried it quite a few times in our tests. When we switch between our primary and disastery recovery site, switching is done manually. We then have to re

for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to https://www.experts-exchange.com/questions/23854105/Error-14261-Trying-to-create-log-shipping.html Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs http://forums.databasejournal.com/showthread.php?30077-Log-Shipping-Error Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Error 14261 - Trying to create log shipping Want to Advertise Here? Solved Error 14261 - Trying to create log shipping Posted on 2008-10-28 MS SQL Server 1 Verified Solution 2 Comments 824 Views Last Modified: 2012-05-05 I am trying to create error 14261 a new log shipping plan. I have deleted all log shipping plans from both servers, primary and secondary. However when I finish creating the plan, and click finish, I get the error message 'The Specified plan_name ('MTUKDB4.proddta_logshipping') already exists. However there are no plans. Can you please help? The primary server is MTUKDB4 The seconday server is MTUKDB7 The Database name is proddta 0 Question by:tajinderpal Facebook Twitter LinkedIn Google error 14261 the LVL 38 Best Solution byJim P. Probably something errant is stuck in the MSDB database. And I'm 2k% so this is partly from memory. Go the MSDB database and see if you have any tables like log_shipping_% and or publishers and/or Go to Solution 2 Comments LVL 38 Overall: Level 38 MS SQL Server 19 Message Accepted Solution by:Jim P.2008-10-29 Probably something errant is stuck in the MSDB database. And I'm 2k% so this is partly from memory. Go the MSDB database and see if you have any tables like log_shipping_% and or publishers and/or subscribers. See if something is stuck in there. 0 LVL 1 Overall: Level 1 Message Expert Comment by:SactoCal2008-10-30 I had a very similar problem also and ran across this post. Using the tip left by jimpen, I went into the msdb...log_shipping_* tables on the secondary server and remove all references the said database/logshipping plan I was working on. THAT problem solved =) Thanks P.S. I could not delete the old references, so I simply changed the name of the database it was referencing. 0 Write Comment First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. Comment

New? Advanced Search Forum Database Discussions MS SQL Server 7/MS SQL Server 2000 Log Shipping Error If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 3 of 3 Thread: Log Shipping Error Tweet Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 01-24-2003,02:18 PM #1 sdives View Profile View Forum Posts Registered User Join Date Nov 2002 Location Chesapeake, VA Posts 104 Log Shipping Error I received the following Error message when attempting to setup LogShipping on a database. 14261: The specified plan_name('SEA2KS27.CorporatePortal_logshipping') already exists. I'm experimenting with log shipping. This occurred on the third time I tried to recreate the plan on the primary server. Other attempts worked fine. There are no plans by that name on any related server. I even checked sysdbmaintplans on all servers. Any input would be appreciated. Sidney Ives Reply With Quote 01-24-2003,02:48 PM #2 rmiao View Profile View Forum Posts Moderator Join Date Sep 2002 Posts 5,938 Check kb article q298743. If it's on sql2k, try apply sp3. Reply With Quote 01-24-2003,03:23 PM #3 sdives View Profile View Forum Posts Registered User Join Date Nov 2002 Location Chesapeake, VA Posts 104 It's resolved. I reviewed the article, found the tables that were trashed and then cleared them out. I'm now able to create my maint.plan. Thanks for your help. Saved me a lot of time and heartache. Sidney Ives Reply With Quote Quick Navigation MS SQL Server 7/MS SQL Server 2000 Top Site Areas Settings Private Messages Subscriptions Who's Online Search Forums Forums Home Forums Database Discussions IBM DB2 Informix Microsoft Access Microsoft SQL Server 2008 Microsoft SQL Server 2005 MDX and Analysis Services Reporting Services MS SQL Server 7/MS SQL Server 2000 MySQL Oracle PostgreSQL Sybase Miscellaneous General Database Discussions Ask an Expert Database Design Database Programming Database News