'The operation could not be performed because OLE DB provider "SQLNCLI11" for linked server was unable to begin a distributed transaction
I'm trying to run a distributed transaction from my machine (SQL Server 2012) to a client server (SQL Server 2008).
I'm trying to run:
begin distributed transaction
select * from [172.01.01.01].master.dbo.sysprocesses
Commit Transaction
and I get:
OLE DB provider "SQLNCLI11" for linked server "172.01.01.01" 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 "172.01.01.01" was unable to begin a distributed transaction.
I can run a SELECT to that server with data coming back, so at least I know the servers can see each other, and the Linked Server exists and is operating
Now, there are multiple posts on the web for this, but I can't get it to work. This is what I have tried so far:
Set DTC properties to the following (on both server)

Restarted the Distributed Transaction Coordinator (MSDTC) from Control Panel -> Services (on both servers).
Uninstalled and installed DTC (on both servers).
Restarted the remote server.
Turned off the firewall on both servers.
Enabled sp_configure 'Ad Hoc Distributed Queries', 1 (on both servers).
I ran DTCPing and it pinged successful.
What else are there to try?
UPDATE: Running the transaction from another server to 172.01.01.01 works. Therefore the issue is not on the destination server, but on my machine which is the source.
Solution 1:[1]
Setting "Enable promotion of distributed transaction" flag to false (in Linked Server Properties Window) solved my similar problem.
Solution 2:[2]
I faced a similar problem and I resolved it as follows. There is a node in tree structure of object explorer in SQL Server. There you will find Serverobjects ? LinkedServers ? below that there is a list of IP addresses of distributed servers.
Right click on it, select properties, a window will pop up. Select server options in the left pane; you will get list of properties. Set the flag value false to the property "Enable promotion of distributed transaction".
Solution 3:[3]
try this SQL above your begin distributed transaction
set XACT_ABORT on
Solution 4:[4]
I had a similar problem. Went through all the things listed to no avail. We have a cluster environment and it turns out our DBA was doing the services work on the cluster and not the main server. Worth keeping that in mind if all else fails :-)
Solution 5:[5]
Condition like this may cause same error:
1- Run a transactional script like this and read from linked server:
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
Begin Tran
... (select command from linked server)...
Commit
2- Open a new connection in code and run a non-transactional script
Result: Error will raised!
Solution: Remove SET TRANSACTION ISOLATION LEVEL SERIALIZABLE.
Solution 6:[6]
Fix: Make sure the “Enable Promotion of Distributed Transaction” is set to “False” on the linked server property.
EXEC master.dbo.sp_serveroption @server=N'yourlinkedservername', @optname=N'remote proc transaction promotion', @optvalue=N'true'
“remote proc transaction promotion” is a new option on SQL Server 2008, which allows you to control whether or not you want to enlist remote stored procedure call in a distributed transaction. When this option is off (FALSE), the local transaction will not be promoted to distributed transaction. This is how we are able to separate outer and inner transactions in a “autonomous transaction” fashion.
Source: https://www.eugenechiang.com/2020/09/17/linked-server-error-no-transaction-is-active/
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | A.K. |
| Solution 2 | TT. |
| Solution 3 | AZ Chad |
| Solution 4 | |
| Solution 5 | AhmadYo |
| Solution 6 | Franut |

