Transaction Manager has disabled its support for remote/network transactions. This partner Transaction Manager has disabled remote/network transactions.

Recently, we used SSIS for data archiving and used distributed transactions. In the development phase, it is okay to run on a computer as long as the distributed service is started. But when I deployed it to UAT yesterday, the error message is:

Finally, find the solution:

1. Make sure that the "Distribute Transaction Coordinator" service is running both on the server and locally. (If the transaction fails, enter MSDTC-resetlog. (do not execute the suspended transaction when running this command)
2. Open component services on the server. Control Panel-> system and security-> Administrative Tools-> component services.
3. Expand to component services> computers> my computer> Distributed Transaction Coordinator> Local DTC, right-click and select Properties. In the pop-up dialog, select the tab "security" and select Network DTC Access and other options. The specific settings are shown in.
   
4. The above is on Win8. If your system is XP or 2003, there are some changes. Right-click component services> computers> my computer and select Properties. In the displayed dialog box, select "MSDTC"-> Security configuration, and select "Network DTC Access", "allow remote client ",
   "Allow inbound/outbound", "enable tip" (some options may not benecessary, have a try to get your configuration) and other options, specific settings as shown in.
   
5. After confirmation, you are required to restart the service. Note: If the problem persists after the subsequent steps, you may need to restart your computer.
6. Make sure that the DTC will not be blocked by your firewall.

Please note that if your environment is not in the domain like me, please select and do not require verification. Otherwise, when running a distributed transaction, the remote computer prompts "the transaction has been confirmed or terminated explicitly or implicitly ".(The computer name must be pingable, otherwise the same error will be returned .)

The firewall disables ICMP packets.
For details, see:
Start-control panel-firewall-advanced-ICMP-settings

PS:

1. A problem is also found. The database also needs to enable support for distributed transactions: Right-click the "server connection" attribute, select "connection" in the Open Properties window, and on the right of the window, select "you need to use distributed transactions for server-to-server communication" and click OK.

2.20.specify the distribution port number, which is the exception of msdtc.exe (netsh firewall set allowedprogram % WINDIR %/system32/msdtc.exe MSDTC enable) under ).

The above is in XP, and the following is firewall settings in Win8 (both inbound and outbound rules need to be set)

If the transaction has been identified or terminated explicitly or implicitly, you can refer to the following settings:

To get rid of this error just follow these steps to configure the registry key and reboot the machine.

1. Click Start, click Run, type regedit, and then click OK.

2. Locate and then click the following registry key:
HKEY_LOCAL_MACHINE \ SOFTWARE \ Policies \ Microsoft \ Windows NT

3. On the edit menu, point to new, and then click Key.
Note if the RPC registry key already exists, go to Step 5.

4. Type RPC, and then press Enter.
5. Click RPC.
6. On the edit menu, point to new, and then click DWORD Value.

7. Type restrictremoteclients, and then press Enter.
8. Click restrictremoteclients.
9. On the edit menu, click Modify.
10. In the value data box, type 0, and then click OK.
Note to enable the restrictremoteclients setting, type1.
11. Close Registry Editor and restart the computer.

Restricting the DCOM port range

1. Go to Start-> Run. Type in dcomcnfg.
2. Go to the properties of the my computer node under the Computers folder underneath component services.

3. Under the my computer Properties look under the default protocols tab.

4. Over there make sure that connection-oriented TCP/IP is selected and then click on properties.

5. You will see a window like this

If you don't see a range above and the window looks exactly like the one above, that wowould mean that the DCOM port range is not configured on the machine.

You can click Add in the above window and type the range (let's say as 5000-5100) and say OK. make sure it looks like this. (both the radio buttons shoshould be selected for Internet range)

Reference address http://www.cnblogs.com/nzperfect/archive/2011/11/03/2234595.html

3. In a transaction, even if nested data exists, all database connections in the same transaction are accessible to the data.