FIX: The orchestration stops responding (hangs) on an HTTP Send request, and you receive an unhandled exception error message in BizTalk Server 2004

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
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

Hotfix information

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.
  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
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
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:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 843529 - Last Review: 01/17/2015 10:53:34 - Revision: 3.0

Microsoft BizTalk Server 2004 Enterprise Edition, Microsoft BizTalk Server 2004 Developer Edition, Microsoft BizTalk Server 2004 Partner Edition, Microsoft BizTalk Server 2004 Standard Edition

  • kbnosurvey kbarchive kbqfe kbhotfixserver kbbiztalk2004sp1fix kbbtsorchestration kbbtsbam kbfix kbbug KB843529
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)