Microsoft Knowledge Base Email Alertz
All KB/RSS Links  |  Hot Kb!  |  New Kb!  |  Scott Cate  |  FAQ / KB  |  Web Hosting  |  Unsubscribe  

(843529) - Fixes a problem in BizTalk Server 2004 where the orchestration stops responding and you must restart the BizTalk Server Host because an exception was not handled.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.
Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks
Article ID: 843529 - Last Review: April 7, 2006 - Revision: 3.0

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

View products that this article applies to.

On This Page

SYMPTOMS

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).
Back to the top

RESOLUTION

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  (http://kbalertz.com/Feedback.aspx?kbNumber=888751/ ) How to obtain the latest BizTalk Server 2004 service pack
Back to the top

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.
Back to the top

STATUS

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.
Back to the top

MORE INFORMATION

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://kbalertz.com/Feedback.aspx?kbNumber=824684/ ) Description of the standard terminology that is used to describe Microsoft software updates
Back to the top
APPLIES TO
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Partner Edition
  • Microsoft BizTalk Server 2004 Standard Edition
Back to the top
Keywords: 
kbqfe kbhotfixserver kbbiztalk2004sp1fix kbbtsorchestration kbbtsbam kbfix kbbug KB843529
Back to the top
        

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Copyright © 2002-2007 KBALERTZ.COM.  All Rights Reserved. Terms / Privacy. Discount ASP.NET Hosting