Hi
I've since tested this with SQL Server now running on another Windows 2000 Professional SP4 computer
In this scenario (i.e. two Windows 2000 Professional computers) I don't get the problem
Something to do with Windows 2003 Server then
Craig
Steven Cheng[MSFT] - 15 May 2004 09:44 GMT
Hi Craig,
Thank you for the response. Regarding on the issue,we're
finding proper resource to assist you and we will update as soon as posible.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security(This posting is provided "AS IS",
with no warranties, and confers no rights.)
Yan-Hong Huang[MSFT] - 17 May 2004 04:47 GMT
Hello Craig,
On Windows Server 2003, DTC has be default network access disabled, so in
order to communicate from a client to a remote DTC or to communicate
between two DTC instance you need to enable network access.
See http://support.microsoft.com/default.aspx?scid=kb;en-us;817064 for
details.
Does that answer your question?
Best regards,
Yanhong Huang
Microsoft Community Support
Get Secure! ?C www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
Craig Nicholas - 17 May 2004 09:36 GMT
Hi Yanhong
I had read the need to do this in another article elsewhere and I have checked this is enabled
I have tried running the PetShop 3 website on an XP Pro box. It also fails but at least I get a more informative message :
i.e. System.Runtime.InteropServices.COMException: The partner transaction manager has disabled its support for remote/network transactions
Perhaps I should have mentioned the following
- Windows Server 2003 (SQL Server) has Project Server installed (which requires SharePoint Services
- It also has Terminal Services running
- All the machines are on the same private network (192.168.0.0) and all are using the TCP/IP protocol
- The Internet Connection Firewall is not enabled on any machin
I hope this may shed some light on the situation
Regard
Craig
Craig Nicholas - 17 May 2004 09:56 GMT
Hi Al
I have found out how to permit Network Transactions in Windows Server 2003
In addition to enabling MS DTC Network Access I did the following extra step
In Admin tools.Component Services or via Component Services MSC Snap-i
- right-click the appropriate computer node and select propertie
- on the MSDTC tab click Security Configuration butto
- in addition to the Network DTC Access being ticked, tick Network Transaction
- restart MSDT
- restart SQL Serve
I think I misunderstood the indented items to be included when Network DTC Access ticked but that is not the case
Thanks everyone for your input
Regard
Craig
Yan-Hong Huang[MSFT] - 18 May 2004 02:10 GMT
Hi Craig,
I am glad to know that the problem is resolved. :)
Thanks very much for participating the community.
Best regards,
Yanhong Huang
Microsoft Community Support
Get Secure! ?C www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
Aside from what Ramesh said, make sure your firewall (if any) is not
blocking the RPC traffic. There's a way in DCOMCNFG to specify port ranges
for protocols.

Signature
Klaus H. Probst, MVP
http://www.vbbox.com/
> Hi
> I have installed MS Petshop 3 sample application and I am getting the following error when OrderProcess.aspx is run:-
>
> "MS DTC is unable to communicate with MS DTC on a remote system. No common RPC protocol is supported between the two systems. Please ensure
that one or more of the following RPC protocols are common to both systems:
TCP/IP, SPX, or NetBEUI. Error Specifics: .\iomgrclt.cpp:203, CmdLine:
C:\WINNT\System32\msdtc.exe, Pid: 1328"
> Database installed on SQL Server 2000 SP3a which is running on Windows 2003 Server Standard.
> Application and Com+ services installed on Windows 2000 Professional SP4.
[quoted text clipped - 7 lines]
> Craig
> PS There doesn't seem to be a 'home' for MSDTC so I've cross-posted
Steven Bagley - 19 Jan 2005 14:14 GMT
This does not just apply to Windows 2003. I have two systems, one a Windows 2000 SP4 system running SQL 7 and the other a Windows 2000 SP4 system running SQL 2000 that just started exhibiting this behavior. I suspect a recent security update but not sure.
The following paragraph is a tangent to thhis areticle ...."It could be the network guys, who, by the way, always do sh.t without admitting anything to anyone. Just the other day I had to make the damn datacom guy attempt a VPN connection from his home to prove that the connction was being routed to their damn checkpoint box. They swore up and down that it was impossible, further, that they had not done anything. Based on their denials and from other experiences I no longer trust them at all. For all systems between firewalls I now run a portqry script to check port availability between systems."
venkat p - 27 Jan 2005 14:16 GMT
We had clustered 2003 box (2 nodes). On active node I'm getting this error....
MSDTC CLIENT
MS DTC is unable to communicate with MS DTC on a remote system. No common RPC protocol is supported between the two systems. Please ensure that one or more of the following RPC protocols are common to both systems: TCP/IP, SPX, or NetBEUI. Error Specifics: .\iomgrclt.cpp:203, CmdLine: C:\WINNT\System32\msdtc.exe, Pid: 1328
As it was said in this thread by diff people -- all Network DTC access was enabled. but still I'm getting error...