Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 870609 - Last Review: June 28, 2004 - Revision: 1.4
You cannot resume messages from BizTalk Server 2004 Health and Activity Tracking after Internet Information Services is stopped and then is restarted
You use dynamic ports to send messages through the HTTP transport by using multiple instances of the same orchestrations.
During the execution of the Business Process Execution Language for Web Services (BPEL4WS), Microsoft Internet Information Services (IIS) is restarted and some of these messages are sent to the suspended queue.
Events that are similar to the following are generated:
Uncaught exception terminated service
HTTPMultiIn.Service1(2eb5be0d-6a94-374a-ba72-21fb7336bca6), instance
905dc7e4-b8c6-4b01-be28-9e595b476198
Exception from HRESULT: 0xC0C01B13.
Exception type: COMException
Source: Microsoft.BizTalk.Interop.Agent
Target Site: Microsoft.BizTalk.Agent.Interop.IBTMessage
ReadReferencedMessageByID(System.Guid ByRef)
Help Link:
Additional error information:
The BizTalk HTTP receive location "/WSOPortTest01/BTSHTTPReceive.dll" could not
send the HTTP headers to the client.
The BizTalk HTTP receive location "/WSOPortTest01/BTSHTTPReceive.dll" could not
send the BizTalk correlation token to the client.
The "HTTP" adapter is suspending a outbound message going to destination
URL:"HTTP://localhost/WSOPortTest01/BTSHTTPReceive.dll". Details:"The underlying
connection was closed: An unexpected error occurred on a receive.".
The "HTTP" adapter is suspending a outbound message going to destination
URL:"HTTP://localhost/WSOPortTest01/BTSHTTPReceive.dll". Details:"The remote
server returned an error: (503) Server Unavailable.".
The Messaging Engine has suspended "4" message(s) from adapter "HTTP" due to
failures in message processing. Please refer to Health and Activity Tracking tool
for more detailed information on this failure.
Even though IIS is running again, the messages cannot be resumed by using Microsoft BizTalk Server 2004 Health and Activity Tracking (HAT).
This behavior occurs because you cannot resume response messages when they are suspended. The response is delivered to an adapter on a callback interface. When the adapter terminates for any reason, you lose that callback interface because the interface resided in memory. Additionally, you cannot pass that response back to IIS because the IIS extension control block that holds a reference to the connection will have terminated.
Additionally, you cannot resume all messages that are suspended on the receive side.
This behavior is by design.
APPLIES TO
- Microsoft BizTalk Adapter for FTP
- Microsoft BizTalk Adapter for MQSeries
- Microsoft BizTalk Adapter 1.0 for SAP
- Microsoft BizTalk Adapter for SQL
- Microsoft BizTalk Adapter for Web Services
- Microsoft BizTalk Server 2004 Developer Edition
- Microsoft BizTalk Server 2004 Enterprise Edition
- Microsoft BizTalk Server 2004 Partner Edition
- Microsoft BizTalk Server 2004 Standard Edition
| kbinfo kbbug kbprb KB870609 |
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