Microsoft Knowledge Base Email Alertz

TCP settings that can impact BizTalk Server

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: 970406 - Last Review: March 10, 2011 - Revision: 4.0

TCP settings that can impact BizTalk Server

On This Page

Source: Microsoft Support

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Symptoms

On a BizTalk server, you may notice the following symptoms:
  • The following events may be logged in the Application Event logs:
Event ID: 6913
Description: SQL Server, BizTalkMsgBoxDb, [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.

Event ID: 5410
Description: [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.

Event ID: 6912
Description: DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.
  • The BizTalk Server fails to restart or shutdown. When rebooting the computer, it may just hang and the mouse may not move. These symptoms may occur for an extended period of time and the computer may not shut down. There are no errors in the event log.

Cause

These issues can occur because of TCP/IP changes in Windows Server 2003 and later.

Resolution

There are several items to implement to stop the errors from occurring:
  1. On the SQL server running on Windows Server 2003, set the SynAttackProtect registry key using the steps in Microsoft Knowledge Base (KB) article 899599:

    899599 (http://support.microsoft.com/?id=899599) 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

    Note
    The SynAttackProtect registry key is not applicable on Windows Server 2008 and Windows Server 2008 R2. For a list of the registry keys on these operating systems, visit the following link:

    TCP/IP Registry Values for Microsoft Windows Vista and Windows Server 2008 (http://www.microsoft.com/downloads/en/details.aspx?familyid=12AC9780-17B5-480C-AEF7-5C0BDE9060B0&displaylang=en)
  2. On all the BizTalk and SQL servers running on Windows Server 2003, use the steps in KB article 948496 to disable the Scalable Networking Pack (SNP) features:

    948496 (http://support.microsoft.com/?id=948496) An update to turn off default SNP features is available for Windows Server 2003-based and Small Business Server 2003-based computers

    To disable TCP Chimney Offload feature of the Scalable Networking Pack (SNP), you can also install the hotfix in KB article 940202:

    940202 (http://support.microsoft.com/?id=940202) A Windows Server 2003-based computer may stop responding during shutdown after you install the Scalable Networking Pack

    On all the BizTalk and SQL servers running on Windows Server 2008, use the steps in KB article 951037 to disable Receive Side Scaling (RSS) and the TCP Chimney Offload features of the Scalable Networking Pack (SNP):

    951037 (http://support.microsoft.com/?id=951037) Information about the TCP Chimney Offload, Receive Side Scaling, and Network Direct Memory Access features in Windows Server 2008
  3. On all BizTalk servers running on Windows Server 2003, increase the ephemeral ports and reduce the TCP reuse timeout setting by modifying the MaxUserPort and TCPTimedWaitDelay registry keys documented at the link below:

    BizTalk Server Database Optimization (http://msdn.microsoft.com/en-us/library/bb743398.aspx)

    You can modify these settings at the HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters registry key. The table below lists the recommended values:

    Collapse this tableExpand this table
    Value nameValue Comment
    MaxUserPort 0xFFFE (65534) Prevents port exhaustion
    TcpTimedWaitDelay 0x1E (30) Release unused ports as quickly as possible

    On all BizTalk servers running on Windows Server 2008, we recommend not modifying the dynamic port range. If you determine that additional dynamic ports are needed, refer to KB article 929851:
    929851  (http://kbalertz.com/Feedback.aspx?kbNumber=929851/ ) The default dynamic port range for TCP/IP has changed in Windows Vista and in Windows Server 2008

    The TCP reuse timeout setting can also be reduced by modifying the TCPTimedWaitDelay registry key. For more information on this registry key in Windows Server 2003, refer to the following site:

    TCP TIME-WAIT Delay (http://msdn.microsoft.com/en-us/library/ms819739.aspx)

    For more information on this registry key on Windows Server 2008, refer to the following site: 

    TCP/IP Registry Values for Microsoft Windows Vista and Windows Server 2008 (http://www.microsoft.com/downloads/en/details.aspx?familyid=12AC9780-17B5-480C-AEF7-5C0BDE9060B0&displaylang=en)
  4. On all the BizTalk and SQL servers running on Windows Server 2003, use the steps in KB article 906736 to disable Privilege Attribute Certificate (PAC) verification. On all BizTalk and SQL servers running on Windows Server 2008, refer to KB article 906736 for more information on Privilege Attribute Certificate (PAC) verification.
    906736  (http://kbalertz.com/Feedback.aspx?kbNumber=906736/ ) You experience a delay in the user-authentication process when you run a high-volume server program on a domain member in Windows 2000 or Windows Server 2003

RESTART REQUIREMENT

You must restart your computer after implementing the changes above.

More Information

TCP/IP settings can also be configured using the Network shell (netsh) command-line utility at a Windows command prompt with administrator-level permissions. Refer to the following link for more information:

Netsh Technical Reference (http://technet.microsoft.com/en-us/library/cc725935(WS.10).aspx)

The KB articles below also reference General Network Errors:

328476 (http://support.microsoft.com/?id=328476)  Description of TCP/IP settings that you may have to adjust when SQL Server connection pooling is disabled
319502 (http://support.microsoft.com/?id=319502)  PRB: "WSAEADDRESSINUSE" Error Message When You Try to Connect Through an Anonymous Port After You Increase the IMAP Connection Limit

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

APPLIES TO
  • Microsoft BizTalk Server Branch 2010
  • Microsoft BizTalk Server Developer 2010
  • Microsoft BizTalk Server Enterprise 2010
  • Microsoft BizTalk Server Standard 2010
  • Microsoft BizTalk Server 2009 Branch
  • Microsoft BizTalk Server 2009 Developer
  • Microsoft BizTalk Server 2009 Enterprise
  • Microsoft BizTalk Server 2009 Standard
  • Microsoft BizTalk Server 2006 R2 Branch Edition
  • Microsoft BizTalk Server 2006 R2 Developer Edition
  • Microsoft BizTalk Server 2006 R2 Enterprise Edition
  • Microsoft BizTalk Server 2006 R2 Standard Edition
  • Microsoft BizTalk Server 2006 Developer Edition
  • Microsoft BizTalk Server 2006 Enterprise Edition
  • Microsoft BizTalk Server 2006 Standard Edition
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Partner Edition
  • Microsoft BizTalk Server 2004 Standard Edition
Keywords: 
kbrapidpub kbnomt KB970406
       

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