This article has been archived. It is offered "as is" and will no longer be updated.
In Microsoft BizTalk Server 2004, the orchestration stops responding (hangs) on a HTTP Send request and you must restart the BizTalk Server Host. Then, you receive a Business Activity Monitoring (BAM) error message in the event log that is similar to the following:
Event Type: Error Event Source: BAM EventBus Service Event Category: None Event ID: 16 Date: 5/21/2004 Time: 4:57:12 AM User: N/A Computer: SVARIBZAP01 Description: Unhandled exception caught, exception details: System.IO.IOException: Unable to write data to the transport connection. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.Socket.EndMultipleSend(IAsyncResult asyncResult) at System.Net.Sockets.NetworkStream.EndMultipleWrite(IAsyncResult asyncResult) --- End of inner exception stack trace --- at System.Net.ConnectStream.EndWrite(IAsyncResult asyncResult) at Microsoft.BizTalk.HttpTransport.HttpAsyncTransmitter.OnWriteComplete(IAsyncResult result) at System.Net.LazyAsyncResult.InvokeCallback() at System.Net.ConnectStream.WriteCallback(IAsyncResult asyncResult) at System.Net.Sockets.OverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped).
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
888751 How to obtain the latest BizTalk Server 2004 service pack
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.