Error 14261 Sql 2000

(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語)  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 | Quote 0 Sign in to vote I deleted all the jobs using SQL Management Studio and no jobs appear when I review the SQL Serve

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 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 https://social.msdn.microsoft.com/Forums/sqlserver/en-US/66186117-c07e-4c10-867d-b61f5b107961/sql-2012-log-shipping-error-14261?forum=sqldisasterrecovery @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 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 http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=67729 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 resetup log shipping going the other way. We switch 2-3 times per year to ensure that our disaster recovery plan works.Tara Kizeraka tduggan shahab03 Starting Member USA 28 Posts Posted-06/14/2006: 13:48:26 changing Logshipping roles seems easy from BOL...but I ve experienced lots of hurdles in each step....I am not able to execute:EXEC sp_change_secondary_role@db_name = 'test',@do_load = 1,@force_load = 1,@final_state = 1,@access_level = 1,@terminate = 1,@stopat = NULLGOwhen I executed this SP, I got an error:Server: Msg 22029, Level 16, State 1, Line 0sqlmaint.exe failed.Per followinghttp://support.microsoft.com/default.aspx?scid=kb;en-us;294397&Product=sql2kI can resolve the issue above by 1)Ensure that there are no outstand

Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips http://www.tek-tips.com/viewthread.cfm?qid=1514141 Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts http://forums.databasejournal.com/showthread.php?30077-Log-Shipping-Error 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 error 14261 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 error 14261 sql 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 d

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 and Announcements Structured Query Language (SQL) SQL Scripts Database Lounge Feedback Related Sites SQL Course SqlCredit « Previous Thread | Next Thread » Posting Permissions You may not post new threads You may not post replies You may not post attachments You may not edit your posts BB code is On Smilies are On [IMG] code is Off [VIDEO] code is Off HTML code is