- This topic has 9 replies, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
When I send messages to webservices (SOAP), I am receiving the following error:
The adapter failed to transmit message going to send port … It will be
retransmitted after the retry interval specified for this Send Port.
Details:”WebException: The underlying connection was closed: The connection
was closed unexpectedly.How should I solve this ? Please help.
-
Sidhu,
See the Microsoft Support Article: http://support.microsoft.com/kb/924638/en-us; you may also be interested in this MSDN forums thread: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3144339&SiteID=17
Rgds, Nick.
-
I went through the article but I don’t think it is not helpful for soap adapter. when i downloaded and trying to install the hotfix it is throwing error. So, I am not sure if this is helpful for soap adapter.
-
-
Nick,
I am receiving “BTS2006x86 not found or this package does not contain compatible patch.” I have BizTalk server 2006 R2 installed on my machine. Is the error because it’s fixed with R2?
-
You have R2 installed? Why not use the WCF-BasicHTTP adapter? It might immediately fix your issue and it will definitely give you MUCH better debugging capabilities and MUCH more flexibility than the SOAP adapter. Here is a walkthrough: http://msdn.microsoft.com/en-us/library/bb246019.aspx.
-
Thanks ruselw,
I am actually consuming a published web service and not publishing it. Can we use WCF-BasicHttp consuming wizard to communicate with a normal SOAP based web service?
-
Yep. Take a look at the walkthrough I posted above. It explains how to consume a web service with the WCF adapter. The setup is really similar to the SOAP adapter, except you generate a schema instead of adding a web reference. The BasicHttp WCF binding is designed for interoperability with standard (non WS-*) web services. This means the WCF-BasicHttp adapter can do everything the SOAP adapter can do, and then some. You want more info about why the web service call failed? Just enable WCF tracing: http://blogs.msdn.com/madhuponduru/archive/2006/05/18/601458.aspx.
-
-
-
-
-
-
-
-
Sidhu, Have you checked the timeout values on the sender and remote service? I had this issue when connecting to a Apache webservice . (Except that as far as i can remember i saw timeout errors in the logs). Anyway, I found that while my Http timeout is 90 seconds, the tomcat server had set theirs to 20 seconds. Increasing that to 120 seconds helped overcome this exception.
HTH,
Benjy
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.