A BizTalk Server Host instance fails, and a "General Network" error is written to the Application log when the BizTalk Server-based server processes a high volume of documents (899599)
The information in this article applies to:
- Microsoft BizTalk Server 2004 Enterprise Edition
- Microsoft BizTalk Server 2004 Partner Edition
- Microsoft BizTalk Server 2004 Developer Edition
- Microsoft BizTalk Server 2004 Standard Edition
- Microsoft Windows Server 2003 SP1
- Microsoft SQL Server 2000 (all editions) SP3a
Important This article contains information about how to modify the registry. Make sure to 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 SYMPTOMSA Microsoft BizTalk Server Host instance fails and then restarts itself, and errors that are similar to the following are written to the BizTalk Server Application log: Event Type: Error
Event Source: BizTalk Server 2004
Event Category: (1)
Event ID: 6913
Computer: BizTalkServer
Description:
SQLServer, BizTalkMsgBoxDb, [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation..
Event Type: Warning
Event Source: BizTalk Server 2004
Event Category: (1)
Event ID: 5410
Computer: BizTalkServer
Description:
An error has occurred that requires the BizTalk service to terminate. The most common causes are an unexpected out of memory error and an inability to connect or a loss of connectivity to one of the BizTalk databases. The service will shutdown and auto-restart in 1 minute. If the problematic database remains unavailable, this cycle will repeat.
Error message: [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.
Error source:
BizTalk host name: BizTalkHost
BizTalk
Windows service name: BTSSvc$BizTalkHost. This issue typically occurs when the BizTalk Server-based server processes a high volume of documents. CAUSEThis issue occurs because Microsoft Windows Server 2003 Service Pack 1 (SP1) implements a security feature that reduces the size of the queue for concurrent TCP/IP connections to the server. This feature helps prevent denial of service attacks. Under heavy load conditions, the TCP/IP protocol in Windows Server 2003 SP1 may incorrectly identify valid TCP/IP connections as a denial of service attack. This behavior could lead to the issue that is described in the "Symptoms" section.RESOLUTIONWarning 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 your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. To resolve this issue, turn off this new functionality in Windows Server 2003 SP1 by adding the SynAttackProtect entry to the following registry key on the computer that is running Microsoft SQL Server that houses your BizTalk Server databases. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters Set the SynAttackProtect entry to a DWORD value of 00000000. To do this, follow these steps: - Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters - On the Edit menu, point to New, and then click DWORD Value.
- Type SynAttackProtect, and then press ENTER.
- On the Edit menu, click Modify.
- In the Value data box, type 00000000. Click OK.
- Quit Registry Editor.
Note To complete this registry change, you must restart the computer that is running SQL Server. STATUS
This behavior is by design.
| Modification Type: | Major | Last Reviewed: | 9/1/2005 |
|---|
| Keywords: | kbprb KB899599 kbAudDeveloper |
|---|
|