The distributed transaction could not be started because the OLE DB provider "SQLNCLI" of the linked server "IP"

Preface: A server and B server good link, can query, but use to distributed transaction error:

an unhandled "System.Exception" type of exception appears in Mes.exe.

Additional information: System.Data.SqlClient.SqlException: MSDTC on server ' Yichangmes ' is not available.
The operation cannot be performed because the OLE DB provider "SQLNCLI" of the linked server "" Could not start the distributed transaction

According to the online steps, add the host file, set MSDTC is not a line

Test with the DTCPing tool to see if the ping pass is possible, but there are warnings:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/6F/C7/wKioL1WoemHQpqitAAH_UqLVuaE452.jpg "title=" Dtc3.png "alt=" Wkiol1woemhqpqitaah_uqlvuae452.jpg "/>

After query

Workaround: A bug that belongs to a. Net 2.0, hit hotfix:ndp20-kb916002-x86

3. Symptom: A warning appears when using DTC ping "warning:the CID values for both test

Machines is the same "

4. Symptom: The distributed error cannot be started on Win 2000

Cause: The cloned operating system causes the FIX: Add/Remove

WORKAROUND: Open the registry, HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSDTC

Modify the following two items:

Allowonlysecurerpccalls=0

Turnoffrpcsecurity=1

The registry has not been modified and the system has been re-installed!

Because Server B is cloned from Server A, first hit the patch error, directly re-installed the next system, done!!!

Summary: In the future even the test server can not be lazy!

This article is from "one van" blog, please be sure to keep this source http://1336014.blog.51cto.com/1326014/1675592

The distributed transaction could not be started because the OLE DB provider "SQLNCLI" of the linked server "IP"