Article ID: 912504
Article Last Modified on 11/15/2007
APPLIES TO
- Microsoft BizTalk Server 2004 Standard Edition
- Microsoft BizTalk Server 2004 Partner Edition
- Microsoft BizTalk Server 2004 Enterprise Edition
- Microsoft BizTalk Server 2004 Developer Edition
SYMPTOMS
Consider the following scenario:
- Multiple two-way isolated host adapters run under the same isolated host in Microsoft BizTalk Server 2004. Examples of the two-way isolated host adapters are HTTP adapters, SOAP adapters, or WSE adapters.
- An isolated host adapter is configured to call an orchestration that is published as a Web service. This orchestration sends a response message to the client.
- Multiple HTTP worker processes are configured for an application pool in Microsoft Internet Information Services (IIS).
- A Microsoft SQL Server cluster resource that provides failover support hosts the BizTalkMsgBoxDb database.
In this scenario, after a failover of the SQL Server cluster resource that hosts the BizTalkMsgBoxDb database, new messages are submitted to the orchestration as expected. However, response messages are suspended by the isolated host adapter. Additionally, negative acknowledgement (NACK) messages are generated for the suspended response messages.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Warning You cannot roll back this hotfix from the BizTalk Server environment. Therefore, make sure that you fully test this hotfix in a test environment before you apply this hotfix to a production environment. Do not try to use Add or Remove Programs to remove this hotfix because this does not roll back the database changes, and leaves the BizTalk Server environment in an inconsistent state.
Prerequisites
You must have Microsoft BizTalk Server 2004 Service Pack 1 installed to apply this hotfix.
Restart requirement
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File 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.
| File name | File version | File size | Date | Time |
|---|---|---|---|---|
| Btsmessageagent.dll | 3.0.6172.0 | 592,384 | 06-Jan-2006 | 20:09 |
| Btsmsg.dll | 3.0.6172.0 | 143,872 | 06-Jan-2006 | 20:09 |
| Btsmsgcore.dll | 3.0.6172.0 | 1,042,432 | 06-Jan-2006 | 20:09 |
| Microsoft.biztalk.interop.agent.dll | 3.0.6172.0 | 45,056 | 06-Jan-2006 | 19:32 |
| Microsoft.biztalk.messaging.dll | 3.0.6172.0 | 53,248 | 06-Jan-2006 | 19:40 |
| Microsoft.biztalk.streaming.dll | 3.0.6172.0 | 45,056 | 06-Jan-2006 | 19:32 |
| Microsoft.xlangs.biztalk.engine.dll | 3.0.6172.0 | 221,184 | 06-Jan-2006 | 19:44 |
| Microsoft.xlangs.engine.dll | 3.0.6172.0 | 221,184 | 06-Jan-2006 | 19:44 |
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
WORKAROUND
To work around this problem, run the iisreset command at a command prompt.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more 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
Keywords: kbbug kbfix kbqfe kbpubtypekc kbbtsorchestration kbbtsmessaging kbhotfixserver KB912504
