Error 14261 The Specified Plan_name

360 games PC games Windows games Windows phone games Entertainment All Entertainment Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States)‎ Terms of use Privacy & cookies Trademarks © 2016 Microsoft

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 Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs 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 a new log shipping plan. I have deleted all log shipping plans https://support.microsoft.com/en-us/kb/298743 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 LVL 38 Best Solution byJim P. Probably something errant is stuck in the MSDB database. And I'm 2k% https://www.experts-exchange.com/questions/23854105/Error-14261-Trying-to-create-log-shipping.html 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 Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. Featured Post Why You Should Analyze Threat Actor TTPs Promoted by Recorded Future After years of analyzing threat actor behavior, it’s become cl

up 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 http://www.sqlservercentral.com/Forums/Topic110758-5-1.aspx 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 http://www.sql-server-helper.com/error-messages/msg-14001-14500.aspx 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 error 14261 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, error 14261 the 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, Visits: 23 Woohoo! That was it! Thank you. Regards, Melissa Post #110764 surya prakashsurya prakash Posted Tuesday, October 26, 2004 6:02 AM Grasshopper Group: General Forum Members Last Login: Friday, April 15, 2011 12:01 PM Points: 15, Visits: 21 Hi,I have problem with log shipping similar one as the above but in different senarioFor testing purpose I have selected 3 servers with names(A,B,C) for log shipping and I am working on pubs database.I have configured A(Primary server) B and C are (Stand By servers)I am successfully to create A(primary server) and B (Stand by server).For the other server the same A as (primary Server) and C as (stand by server) I have encountered the following problemerror 14261: the specified primar

Messages 2001-3000 Messages 3001-4000 Messages 4001-5000 Messages 5001-6000 Messages 6001-7000 Messages 7001-7500 Messages 7501-8000 Messages 8001-8500 Messages 8501-9000 Messages 9001-9500 Messages 9501-10000 Messages 10001-10500 Messages 10501-11000 Messages 11001-11500 Messages 11501-12000 Messages 12001-13000 Messages 13001-13500 Messages 14001-14500 Home>Tips & Tricks> Error Messages 14001 to 14500 SQL Server Error Messages - Errors 14001 to 14500 SQL Server Error Message - Errors 14001 to 14500 A message number uniquely identifies each error message and the error message text describes the problem. The error message text often includes placeholders for information (such as object names) to be inserted in the error message when it is displayed. Unfortunately, the error message text does not tell you how to solve or work around the problem. In this series of Error Messages list, we will try to provide you with ways on how to overcome or work around certain error messages. Some error messages are self-explanatory and can easily be fixed, such as "Invalid object name". Others are harder to fix or work around, especially by those who are new to SQL Server. It is the intent of this page and succeeding pages (to come) to assist you in addressing or working around SQL Server error messages. Error Severity Description 14002 16 Could not find the 'Sync' subsystem with the task ID %ld. 14003 16 You must supply a publication name. 14004 16 %s must be in the current database. 14005 16 Cannot drop the publication because at least one subscription exists for this publication. Drop all subscriptions to the publication before attempting to drop the publication. If the problem persists, replication metadata might be incorrect; consult Books 14006 16 Could not drop the publication. 14008 11 There are no publications. 14009 11 There are no articles for publication '%s'. 14010 16 The remote server '%s' is not defined as a subscription server. Ensure you specify the server name rather than a network alias. 14011 16 Unable to mark server '%s' as a non SQL Server subscriber. 14012 16 The @status parameter value must be either 'active' or 'inactive'. 14013 16 This database is not enabled for publication. 14014 16 The synchronization method (@sync_method) must be '[bcp] native', '[bcp] character', 'concurrent', 'concurrent_c', 'database snap