I have an WCF Application using BasicHttpBinding . Application worked successfully when database server was in the same subnet as the development machine. e.x. 192.168.xx.xx but, my network administrator has given given separate ip from another subnet
to database as 172.xxx.xxx.xxx. from then on i am getting
"the MSDTC transaction manager was unable to pull the transaction from the source transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot
find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers. (Exception from HRESULT: 0x8004D02B) "
I searched it , but ,since the only change was the Ip , answers seems to be invalid, is there any restriction such this in WCF ??
You probably do have a firewall issue or the (2) machines cannot legitimately see each other. In the latter case if the machines are on a separate domain this would fall into the hands of infrastructure to add a DNS value so the machines can see each other.
However this kind of stuff is really out of the realm of the ASP.NET forums and more along the lines of the
IIS or
TechNet forums. I think the 1st article below will help you work through all the potential issues and get your problem solved. The others may offer some guidance as well:
On the purely WCF side here are some things to check if the endpoint address ever changes as it may have in your case:
Always re-consumed the service if the endpoint address changes. The proxy files built can have IP address information embedded and if you have not refreshed the reference and recreated the proxy this could be causing you an issue.
Update addresses used for the WCF service. Is it an IP address or are you using a DNS value? If it is an IP based URL and it points to the old IP, make sure to update it and redeploy the service for consumption.
roshan605
Member
38 Points
26 Posts
WCF MSDTC Coordinator
Apr 24, 2012 04:46 AM|LINK
I have an WCF Application using BasicHttpBinding . Application worked successfully when database server was in the same subnet as the development machine. e.x. 192.168.xx.xx but, my network administrator has given given separate ip from another subnet to database as 172.xxx.xxx.xxx. from then on i am getting
"the MSDTC transaction manager was unable to pull the transaction from the source transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers. (Exception from HRESULT: 0x8004D02B) "
I searched it , but ,since the only change was the Ip , answers seems to be invalid, is there any restriction such this in WCF ??
Thanks in advance.
mm10
Contributor
6409 Points
1184 Posts
Re: WCF MSDTC Coordinator
Apr 24, 2012 09:33 AM|LINK
Check this article for how to enable network access: http://technet.microsoft.com/en-us/library/cc753510%28WS.10%29.aspx
roshan605
Member
38 Points
26 Posts
Re: WCF MSDTC Coordinator
Apr 24, 2012 09:40 AM|LINK
Yes . i am ware of this. i have set Network DTC from the very beginning.
atconway
All-Star
16846 Points
2756 Posts
Re: WCF MSDTC Coordinator
Apr 25, 2012 07:23 PM|LINK
You probably do have a firewall issue or the (2) machines cannot legitimately see each other. In the latter case if the machines are on a separate domain this would fall into the hands of infrastructure to add a DNS value so the machines can see each other. However this kind of stuff is really out of the realm of the ASP.NET forums and more along the lines of the IIS or TechNet forums. I think the 1st article below will help you work through all the potential issues and get your problem solved. The others may offer some guidance as well:
Debugging Distributed Transactions: MSDTC network problems:
http://blogs.microsoft.co.il/blogs/idof/archive/2010/07/19/debugging-distributed-transactions-msdtc-network-problems.aspx
Communication with the underlying transaction manager has failed:
http://www.velocityreviews.com/forums/t716594-communication-with-the-underlying-transaction-manager-has-failed.html
Another "Communication with the underlying transaction manager has failed.":
http://social.msdn.microsoft.com/Forums/lv/windowstransactionsprogramming/thread/9e4030f1-bfa8-4d16-9b0b-3604688fe38c
On the purely WCF side here are some things to check if the endpoint address ever changes as it may have in your case:
Hope this helps! :)
roshan605
Member
38 Points
26 Posts
Re: WCF MSDTC Coordinator
Apr 27, 2012 02:55 AM|LINK
Thank you for the feedback.. yeah i will go through mentioned links and try to post in relevant forums.