Webservice call from BizTalk 2010 to IIS7 fails. The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.


i need investigate more on issue related keep alive settings in iis 7 mentioned in link http://seroter.wordpress.com/2007/08/06/troubleshooting-canceled-web-request/

in our case have orchestration in biztalk 2010 (windows server 2008 r2 standard , iis7) calls webservice (asmx) hosted in iis 7. checked configuration [the "ping maximum responser time (seconds)" under "process model" settings] in iis on both server [biztalk hosting , web service hosting server] , settings same. don't option set keepalive=false, since need use connection pooling feature. have mentioned below exact error message in biztalk server.

webexception: underlying connection closed: connection expected kept alive closed server.
ioexception: unable read data transport connection: existing connection forcibly closed remote host.
socketexception: existing connection forcibly closed remote host

most of our webservice calls orchestration working expected, 5% of webservice calls fails.
please point me right direction trouble shoot issue.

thanks , regards, vikram

it network issue. actual network problem not detected, resolved our issue.

we looked @ iis logs on web server (where web service hosted) , see request coming web server not completed. there error in iis log while sending request (sc-win32-status 121 , 1236). looks network connection between these 2 servers terminate. (something related way snat works)

to resolve our issue, had keep web service , biztalk on same network. 

once did that, resolved our issue.

thanks , regards, vikram



BizTalk Server  >  BizTalk Server General



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

BizTalk Server 2013 Azure VM Log Shipping and HA for hosts

hi , background: for our customer, having a  2 biztalk , 1 sql setup of environment. [biztalk server 2013 azure vms provisioned azure gallery, sql server 2012 azure vm ]. in current configuration, there no high availability or disaster recovery plan set. want implement dr , possibly ha configuration on these servers. i have few questions regarding same. please let me know thoughts on same. currently writing log files (log shipping files) mounted/attached drive same sql server. how move these log files across secondary site since shared storage not supported. in case of sql server crash, losing log files since reside on same server. please share options on how can move these periodically between datacenters. for hosts pop3, ftp need host clustering (which requires biztalk machines present on windows cluster traditionally), please let know how achieve in azure scenario thanks , regards, ujjwal devarapalli -ujjwal you can refer article, issue azure vm lo...
Read more

How to send non-standard Content-Type header ?

hello, my custom client developed send custom content-type header "xyz" (with out "/"). message gone in lcs 2005. after have upgrade lcs 2005 ocs 2007 r2 in test environment. custom client not able send same custom content-type in ocs 2007 r2 used possible send in lcs 2005. below cut ocs 2007 r2 accessedge log file. tl_warn(tf_component) [0]0f68.0bb4::11/08/2010-06:02:51.546.00000de7 (sipstack,ccontenttypeheader::parse:contenttypeheader.cpp(118))( 00000000036249f0 ) exit - media-type syntax error in getting "/" tl_error(tf_component) [0]0f68.0bb4::11/08/2010-06:02:51.546.00000de8 (sipstack,csipmessage::parseallheaders:sipmessage.cpp(6408))( 0000000003566a50 ) exit. failed while parsing header. tl_error(tf_component) [0]0f68.0bb4::11/08/2010-06:02:51.546.00000de9 (sipstack,csiprequest::validateinboundheaders:siprequest.cpp(1391))( 0000000003566a50 ) exit - failed while parsing header. returned 0xc3e93f51(sipproxy_e_invalid_content_type_header)...
Read more