Friday, February 14, 2014

BizTalk: Message is stuck with Ready to run status at Dynamic send port

Problem Statement:

A simple dynamic port in an orchestration that writes a file to a file location. Here is the configuration

MyDynamicSendPort(Microsoft.XLANGs.BaseTypes.Address) = "FILE://c:\\TestFolder\\Out\\Test.xml";

When I run this orchestration, the dynamic port does not write the file to the folder, however It does not show any error either. It is always in "Ready to Run" state where the message is "Queued Awaiting".
 It seems that Message is stuck with Ready to run status at Dynamic send port


It is probably because of following reasons:

1. Default Host instance is not started.
or if started then
2. Default Host is not configured as Send Handler under corresponding Adapter (FILE in this case).

Concept behind BizTalk Dynamic Send Port:

Dynamic ports  in BizTalk always run under the default host instance, this is the internal server level logic as it is the only way BizTalk internals can guarantee that a BizTalk Hosts instance  is actually present.


Wednesday, February 5, 2014

IIS error: reset by peer


Sometimes while calling WCF (.NET WCF or BizTalk schema/orchestration exposed as WCF service) service with hudge / large receives below error.

" reset by peer:socket write error"

It usually happens when sending attachment (base64 format) with SOAP request.

Root Cause :

Web-service which is hosted on Web-Server (IIS) couldn't handle large message.


Need to configure the HTTP Runtime to accept large messages

1. Go to IIS
2. Open the web.config or corresponding web-service.
3. Put below entries.

     <httpRuntime maxRequestLength="2097151" />
Note: maxRequestLength value should be as per your need and below the max limit.