Microsoft Sql Server Error 7391 Replication
Contents |
360 games PC games ole db provider for linked server was unable to begin a distributed transaction. Windows games Windows phone games Entertainment All Entertainment
Msg 7391, Level 16, State 2
Movies & TV Music Business & Education Business Students & educators
Unable To Begin A Distributed Transaction Linked Server 2012
Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Msg 7391 Distributed Transaction
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 ole db provider sqlncli11 for linked server returned message no transaction is active 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
Get Your Own Blog If you would like to blog on SQLServerCentral.com then send an email to webmaster@sqlservercentral.com. Contact the author Please log in or register to contact the author of this blog ole db provider sqlncli10 for linked server returned message no transaction is active All Blogs All Bloggers on SQL Server Central Feeds Subscribe to this blog Archives the transaction manager has disabled its support for remote/network transactions for this blog June 2016 January 2016 October 2015 May 2015 January 2015 June 2014 April 2014 March 2014 January 2014 September 2013 msg 7391, level 16, state 2, line 3 June 2013 May 2013 April 2013 March 2013 February 2013 October 2012 September 2012 August 2012 July 2012 June 2012 November 2011 September 2011 August 2011 September 2010 August 2010 July 2010 May 2010 September 2009 August https://support.microsoft.com/en-us/kb/306212 2009 April 2009 January 2009 December 2008 November 2008 October 2008 September 2008 August 2008 July 2008 June 2008 April 2008 March 2008 February 2008 January 2008 December 2007 November 2007 September 2005 DBA Philosophy Distributed Transaction Issue Msg 7391 Posted on 21 November 2007 Comments Briefcase Print I solved an "interesting" issue today. It is about distributed transaction. When I set up transactional replication with immediate updating subscription between two SQL Server http://www.sqlservercentral.com/blogs/jeffrey_yao/2007/11/21/distributed-transaction-issue-msg-7391/ 2K5, using EXEC sp_link_publication @publisher = 'Server1', @publication = 'PubUpdate1',@publisher_db = 'Pub_DB',@security_mode = 0,@login = 'sa',@password = 'sa_pwd' on Server2, where the updatable subscribtion is located. I keep on getting this error OLE DB provider "SQLNCLI" for linked server "Server_2" returned message "No transaction is active.". Msg 7391, Level 16, State 2, Line 2 The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "Server_2" was unable to begin a distributed transaction I went to MS support website and found this article: How to troubleshoot error 7391 that occurs when you use a linked server in SQL Server http://support.microsoft.com/kb/306212/en-us But after reading and checking, it seems my environment configuration meets every requirement outlined in the article. After Googl'ed for long time, I still did not get any clue. After sending out an email to system admin group for help, I caught a hint from one of the system admin gurus, the issue is caused by the two servers (Server1 and Server2) are built from a same ghost image and thus they have the same MSDTC credentials. In Windows event log, I find the following message The local MS DTC detected that the MS DTC on Server1 has the same unique identity as the local MS DTC. This means that the two MS DTC will not be able
Performance Tuning SQL Server Administration View All Installation Tools and Utilities Backup and Recovery Availability and Scalability Interoperability Replication Security Stored Procedures T-SQL SQL Server Administration View All Installation Performance Tuning Tools and Utilities Backup http://searchsqlserver.techtarget.com/tip/Troubleshooting-Distributed-Transaction-Coordinator-errors-in-SQL-Server and Recovery Availability and Scalability Interoperability Replication Security Stored Procedures T-SQL SQL Server Development View All .Net Development Database Design and Modeling XML SQL Server Management Issues View http://www.sqldbadiaries.com/ All Consolidation and Virtualization Career Advice Competitors Compliance Migration and Planning SQL Server Platforms View All SQL Server 2000 SQL Server 2005 SQL Server 2008 SQL Server linked server 2008 R2 BI and Data Warehousing View All Data Visualization Analysis Services Integration Services Reporting Services BI Strategies Data Warehousing Topics Archive View All Please select a category SQL Server Administration SQL Server Development SQL Server Management Issues SQL Server Platforms BI and Data Warehousing Section Problem Solve News Get Started Evaluate Manage Problem Solve Sponsored ole db provider Communities Troubleshooting Distributed Transaction Coordinator errors in SQL Server byRoman Rehak Microsoft Distributed Transaction Coordinator enforces transactional consistency over multiple systems in SQL Server. Learn how to solve common errors and properly configure MSDTC. In this Article Share this item with your network: Related Content Demystifying the Microsoft Distributed Transaction ... – SearchSQLServer Transactional replication – SearchSQLServer Fast Guide: Solving SQL Server errors – SearchSQLServer Sponsored News A Threat Intelligence Service Case Study: The Escelar Trojan –Palo Alto Hyper-Convergence Delivers Better Mission-Critical Performance –SimpliVity See More Vendor Resources eGuide: Performance tuning SQL Server via queries, indexes and more –Microsoft High Availability for SQL Server 2005 Using array-based Replication and ... –Hewlett-Packard Company SQL Server's linked server configuration allows you to execute queries or stored procedures and receive data sets... Sign in for existing members Continue Reading This Article Enjoy this article as well as all of our content, including E-Guides, news, tips and more. Step 2 of 2: You forgot to provide an Email Address. T
Servers. They had quite a few Linked Servers setup. After migration any Distributed Transaction like the one below across the linked servers would fail immediately. begin distributed tran
select * from RemoteServer.DBName.dbo.TableName
commit tran Error message OLE DB provider "SQLNCLI11" for linked server "linkedservername" returned message "No transaction is active.".
Msg 7391, Level 16, State 2, Line 2
The operation could not be performed because OLE DB provider "SQLNCLI11" for linked server "linkedservername" was unable to begin a distributed transaction.
The first place I checked for problems was the Component Services (run -> dcomcnfg). The options in the Local DTC Properties were correctly set as seen in this screenshot. Restarting the "Distributed Transaction Coordinator (MSDTC)" service didn't help either. The next step was to look for possible error messages in the Event Log. In the Application Event Log, the following error message was logged. The local MS DTC detected that the MS DTC on ServerName has the same unique identity as the local MS DTC.
This means that the two MS DTC will not be able to communicate with each other.
This problem typically occurs if one of the systems were cloned using unsupported cloning tools.
MS DTC requires that the systems be cloned using supported cloning tools such as SYSPREP. Running 'msdtc -uninstall' and then 'msdtc -install' from the command prompt will fix the problem.
Note: Running 'msdtc -uninstall' will result in the system losing all MS DTC configuration information. The error message in bold indicates that the Unique Identity for the MS DTC (SID) was same on both the local and the destination servers. How is this possible? While the new servers were being built they had syspreped servers. Hence the configuration of MS DTC was also propagated to all the servers where the same image was used. Now that we knew the root cause, the resolution was pretty straight forward. Executed the following steps as explained in this article. Opened the Command Prompt as an Administrator and executed "msdtc -uninstall" Deleted the following registry keys (after exporting them as a precautio