on the client or the server?
Main Topics
Browse All TopicsI'm getting the following error when trying to do a transaction to a remote server.
System.Transactions.Transa
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.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I uninstalled and reinstalled MSDTC on both the server and client and rebooted twice each.
I get the new message:
system.transactions.transa
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!
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/
SAMPLE: A Simple DCOM Client Server Test Application
http://support.microsoft.c
How to configure COM Internet Services (CIS) on the client side
http://support.microsoft.c
I'm using DotNet 3.5 SP1, ADO.NET still uses DCOM, apparently wrapped up inside managed code (thus making it unmanaged again -sigh!).
The app is entirely managed code, written in VS2008 - works fine on a LAN - fails when one of the SQL Servers in the transaction is off-site.
This code worked fine just a year ago (on DotNet3.5) running on W2K3 (no SP) and XP SP2.
What joke! Oracle, here we come!
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"! :)
Business Accounts
Answer for Membership
by: jimpenPosted on 2009-04-05 at 14:25:17ID: 24073038
Make sure that the COM Security is set to everyone and anonymous login.
COM Security