Article ID: 843529 - View products that this article applies to.
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
Time: 4:57:12 AM
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.ConnectStream.WriteCallback(IAsyncResult asyncResult)
at System.Net.Sockets.OverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped).
Service pack informationTo 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:
(http://support.microsoft.com/kb/888751/ )How to obtain the latest BizTalk Server 2004 service pack
Hotfix informationThe 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.
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Date Time Version Size File name -------------------------------------------------------------------------------------- 24-Jun-2004 21:21 3.0.5316.0 144,896 BTSHTTPReceive.dll 24-Jun-2004 21:21 3.0.5316.0 1,024,512 BTSMsgCore.dll 24-Jun-2004 21:21 3.0.5316.0 32,768 Microsoft.BizTalk.CachingService.dll 24-Jun-2004 21:21 3.0.5316.0 720,896 Microsoft.BizTalk.GlobalPropertySchemas.dll 24-Jun-2004 21:21 3.0.5316.0 69,632 Microsoft.BizTalk.HttpTransport.dll 24-Jun-2004 21:21 3.0.5316.0 49,152 Microsoft.BizTalk.Messaging.dll 24-Jun-2004 21:21 3.0.5316.0 217,088 Microsoft.BizTalk.Pipeline.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was corrected in BizTalk Server 2004 Service Pack 1.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 843529 - Last Review: April 7, 2006 - Revision: 3.0