How To Troubleshoot Error 7391
Contents |
360 games PC games ole db provider sqlncli10 for linked server was unable to begin a distributed transaction Windows games Windows phone games Entertainment All Entertainment
Returned Message No Transaction Is Active
Movies & TV Music Business & Education Business Students & educators ole db provider sqlncli10 for linked server returned message no transaction is active Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet ole db provider sqlncli11 for linked server returned message no transaction is active 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
Msg 7391, Level 16, State 2, Line 3
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
SERVER - Fix: Server: Msg 7391, Level 16, State 1, Line 1 April 6, 2007Pinal DaveSQL, SQL Server, SQL Tips and Tricks7 commentsI have received this error many a nested transaction was required because the xact_abort option was set to off times on different servers in my careers. There is no single sql server distributed transaction linked server fix for this Error. Server: Msg 7391, Level 16, State 1, Line 1 can happen due
Unable To Enlist In The Transaction
to many reasons. I have used various of this reasons with few of my servers. Please refer them and try them one by one. One of them https://support.microsoft.com/en-us/kb/306212 should be applicable to your problem.You may receive a 7391 error message in SQLOLEDB when you run a distributed transaction against a linked server after you install Windows XP Service Pack 2 or Windows XP Tablet PC Edition 200. View Article.INFO: Configuring Microsoft Distributed Transaction Coordinator (DTC) to Work Through a Firewall. View http://blog.sqlauthority.com/2007/04/06/sql-server-fix-server-msg-7391-level-16-state-1-line-1/ Article. Fix/Workaround/Solution: Not all memory is available when AWE is enabled on a computer that is running a 32-bit version of SQL Server 2000 SP4. View Article. You receive a "Server: Msg 7391" error message when you try to perform a distributed transaction by using a Microsoft OLE DB Provider for DB2 linked server in SQL Server. View Article.Once the error happened when I was updating local table from link server table columns. I was able to resolve the error by inserting linked server table columns to local temporary table and update local table from local temporary table.Reference : Pinal Dave (http://blog.SQLAuthority.com) Tags: DBA, SQL Download, SQL Error Messages, SQL Server DBCC, SQL Server Security2Related Articles SQL SERVER - A Timeout (30000 milliseconds) was Reached While Waiting for a Transaction Response from the MSSQLSERVER August 15, 2016Pinal Dave SQL SERVER - 2005 NorthWind Database or AdventureWorks Database - Samples Databases - Part 2 June 15, 2007Pinal Dave SQL
unable to begin a distributed transaction. January 7, 2013 Riteshshah Linked Server, sql server Error Fix: Msg 7391, Level 16, State 2, http://blog.extreme-advice.com/2013/01/07/error-fix-msg-7391-level-16-state-2-line-37-the-operation-could-not-be-performed-because-ole-db-provider-sqlncli10-for-linked-server-linkservername-was-unable-to-begin-a-distributed-transactio/ Line 37 The operation could not be performed because OLE DB provider "SQLNCLI10″ for linked server "LinkServerName" was unable to begin a distributed transaction. This error comes when you are trying execute distributed transaction via linked server. Personally I don't prefer linked server and would always go for other alternatives like SSIS package or something else linked server but one of my friend had a situation where he must had to setup linked server to make distributed transaction. Security wasn't concern for him as his network was just an intranet and under hardware as well as software firewall so I have helped him to setup distributed transaction for linked server so that he can fix ole db provider the error: Msg 7391, Level 16, State 2, Line 37 The operation could not be performed because OLE DB provider "SQLNCLI10″ for linked server "MARSLINK" was unable to begin a distributed transaction For example we have two server named “SATURN” and “MARS” accordingly. We have set link server of MARS in SATURN so that I can access database of MARS from SATURN. I wanted to execute one SP from one of the database of MARS from SATURN and it was working fine after setting up linked server but when I tried to take output of this SP into one temp table, it started popping up the error given above. Let us try to resolve this error. First I will connect to first server which is SATURN in my case. After connecting to it, open “RUN” from Start menu and type down "DcomCnfg" in RUN dialog box and click on “Ok” button so you will get “Component Service” window open. Now move to the Console Root->Component Services->computers->My Computer->Distributor Transaction Coordinator->Loc