Link to home
Create AccountLog in
Windows Server 2003

Windows Server 2003

--

Questions

--

Followers

Top Experts

Avatar of bd9000
bd9000

Network access for Distributed Transaction Manager (MSDTC) has been disabled
I'm getting the following error when trying to do a transaction to a remote server.

System.Transactions.TransactionManagerCommunicationException: Network access for Distributed Transaction Manager (MSDTC)
has been disabled. Please enable DTC for network access in the security configuration for MSDTC using the Component Services Ad...

I've tried numerous things to resolve this problem with no luck.

Here is the scenario:
I have a windows application that is running from either Windows XP SP2, Windows Vista 64, or Windows 2003 Server (all get the same error message).
The application connects to a SQL 2005 Server running on a remote W2K3 SP1 server.
MSDTC is running on both the client AND the server (so the error message is useless as it MSDTC service is IN FACT running).
Both client and server allow both incoming and outgoing connections.
Firewalls have been disabled on both Client and Server.
I set up authentication to NONE on both client and server.
Same error...
The application works fine on a local computer with a local database (and the transactions work wonderfully)

I'm stumped on this one.
I've attached a couple of server settings screenshots for clarity.



Settings1.jpg
Settings2.jpg

Zero AI Policy

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


Avatar of Jim P.Jim P.🇺🇸

Make sure that the COM Security is set to everyone and anonymous login.


COM-Security.jpg

Avatar of bd9000bd9000

ASKER

on the client or the server?

Avatar of bd9000bd9000

ASKER

I uninstalled and reinstalled MSDTC on both the server and client and rebooted twice each.
I get the new message:

system.transactions.transactionpromotionException: Failure while attempting to promote transaction -->

Is there any step-by-step instructions out there that show how to get MSDTC to ACTUALLY work between a REMOTE server and a client - the most common situation for 10million+ Windows developers?
Microsoft's help is useless.  Keeping systems wide-open and vulnerable seems to defeat MS's intent on securing Windows without tellings us how to disable all the "security" patches so we can get actual work done!

Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.


Avatar of Jim P.Jim P.🇺🇸

Basically M$ has abandoned DCOM & DTC in favor of the .NET versions of the same crap. My experience with it has been the minimal of getting a specific vendor app working in our environment. If you ending up understanding it, "You're a better man than I am, Gunga Din!".

Chapter 11  Building Secure Serviced Components
http://msdn.microsoft.com/en-us/library/aa302427.aspx

SAMPLE: A Simple DCOM Client Server Test Application
http://support.microsoft.com/kb/259011/

How to configure COM Internet Services (CIS) on the client side
http://support.microsoft.com/kb/265340

ASKER CERTIFIED SOLUTION
Avatar of bd9000bd9000

ASKER

Link to home
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Create Account

Avatar of bd9000bd9000

ASKER

Here's the real answer to this problem.
 It can't be done without a VPN.   REPEAT, you MUST have a VPN or a STATIC IP ADDRESS!
MSDTC can't work at all over the Internet without a VPN tunnel and will never work with NAT routers (as per Microsoft).
I can't figure what the "D" in DTC stands for, certainly not "Distributed"! :)
Windows Server 2003

Windows Server 2003

--

Questions

--

Followers

Top Experts

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).