Server MSDTC Not available solution _ server Other

MSDTC (Distributed Transaction Coordinator) that coordinates transactions across multiple databases, message queues, file systems, and so on. The process name of the service is Msdtc.exe, which calls the system Microsoft Personal WEB Server and Microsoft SQL Server. This service is used to manage multiple servers.

Location: Control Panel--management tools--service--distributed Transaction Coordinator

Dependencies: Remote Procedure Call (RPC) and security Accounts Manager

Recommendation: General household computer is not involved, unless you enable Message Queuing service, you can stop.

Solution:
1.--> Management Tools--> Service-->distributed Transaction coordinator--> properties--> startup in Windows Control Surface edition
2. Under the cmd run "net start MSDTC" opens the service to be normal.

Note: If the 1th step distributed Transaction coordinator fails to start, it is because the log file is lost, the log file is recreated, and then the startup is done. To recreate the MSDTC log and restart the service, follow these steps:

(1) Click "Start", click "Run", enter cmd and press "OK".
(2) Input: Msdtc-resetlog (Note that when you run this command, do not perform a pending transaction)
(3) Finally input: net start MSDTC return, fix!

The following are additional users:

Occurs today when the local machine updates another server data directly in the trigger: MSDTC is not available

Solution:

--> Management Tools--> Service-->distributed Transaction coordinator--> properties--> startup in Windows Control Surface edition

1.
A. Use a SELECT statement without a transaction. Is it possible to distribute queries?
B.linkserver cannot operate on a native computer while doing a distributed update transaction. (Just can't loop back to distributed transactions)
C.DBCC traceon (3604, 7300)--See more detailed error messages with traces.
D. Download MS-provided DTCPing.exe on both machines and follow the readme instructions to run it. Look at the error message.
Http://download.microsoft.com/download/complus/msdtc/1.7/nt45/en-us/DTCPing.exe
2.
Whether the MSDTC for both machines is open.
3.
The MSDTC settings are correct.
1. Open the command prompt, run "net stop msdtc" and run "net start MSDTC".
2). Go to the Component Services administration tool.
3. Browse to the Start administration tool.
4). Select Component Services.
A. Expand the Component Services tree, and then expand My Computer.
B. Right-click My Computer, and then select Properties.
C. In the MSDTC tab, make sure that the following options are selected: Network DTC access network Management network transaction XA transaction
E. In addition, the "DTC login account" must be set to "NT Authority/networkservice".
5). Click OK. This will prompt you to "MS DTC will stop and reboot."
All dependent services will be stopped. Please press ' yes ' to ' continue '. Click "Yes" to continue.
6. Click OK to close the My Computer Properties window.
4.
MSDTC relies on the port used by RPC,RPC to be 135 and test that port 135 is open. Is there a firewall? If there is a firewall turned off first.
Telnet IP 135
If it is turned off, open it.
5.
For a variety of reasons, SQLOLEDB cannot use distributed transactions and change to "MSDASQL" ODBC-mode joins.
Use RRAS instead of RAS. (Control surface--Administrative tools--remote service manager)
Check Whether you are the using remote Access Server (RAS) to Access remote servers.   If So, make sure this you have implemented Routing RAS (RRAS). Linked server does not work on RAS because RAS allows only one way communication.
6. Check to see if your two servers are in the same domain. Whether to establish a trusted join if it is not in the same domain.
7. If it is WIN2000, upgrade to SP4
8. Upgrade MDAC to more than 2.6, preferably 2.8.
9. The latest patch to install SQL: SP3a

It's easy to say. More Online Search