Article ID: 922543
Article Last Modified on 10/31/2007
APPLIES TO
- Microsoft BizTalk Server 2006 Standard Edition
- Microsoft BizTalk Server 2006 Enterprise Edition
- Microsoft BizTalk Server 2006 Developer Edition
- Microsoft BizTalk Server 2006 R2 Branch Edition
- Microsoft BizTalk Server 2006 R2 Standard Edition
- Microsoft BizTalk Server 2006 R2 Enterprise Edition
- Microsoft BizTalk Server 2006 R2 Developer Edition
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
SYMPTOMS
Consider the following scenario:
- You install Microsoft BizTalk Server 2006 on a computer that is running Microsoft Windows Server 2003 Service Pack 1 (SP1).
- In BizTalk Server 2006, you create an orchestration.
- The orchestration uses a request/response port to receive messages from an HTTP client application and to send messages to the HTTP client application.
- The HTTP client application sends a message to the BizTalk Server receive location.
- BizTalk Server starts to processes the message as expected.
- The HTTP client application times out or stops responding.
- BizTalk Server tries to send a response message to the HTTP client application.
In this scenario, messages may not be sent to the HTTP client as expected. When you view the messages in the Health and Activity Tracking (HAT) tool, the messages have a status of "Suspended (Resumable)," and the error "Send port not started" is displayed. Additionally, the BizTalk orchestration incorrectly continues to the next shape.
When this issue occurs, you do not receive an error message.
CAUSE
This issue occurs because the Http.sys file in Microsoft Internet Information Services (IIS) 6.0 does not notify BizTalk Server 2006 that the connection to the HTTP client application was lost.
RESOLUTION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To resolve this issue, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters
- On the Edit menu, point to New, and then click DWORD Value.
- Type EnableFastIo, and then press ENTER.
- Right-click EnableFastIo, click Modify, type 0 (zero) in the Value data box, and then click OK.
- Exit Registry Editor, and then restart the computer.
MORE INFORMATION
After you follow the steps that are mentioned in the "Resolution" section, the first response message will be suspended. After the first response message is suspended, BizTalk Server does not send any response messages. To have BizTalk Server send response messages, run the iisreset command.
Notes
- You should use the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameterskey only as a last resort. This method causes a performance regression on send throughputs. - This registry key affects all applications on the computer that use Http.sys.
- This key is not supported in the Windows Server Code Name "Longhorn" operating system.
Keywords: kbtshoot kbbts kbprb kbbug KB922543
