Some problems occur after installing Windows Server 2003 SP2

Source: Microsoft Support

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.

NOTE: This article is to replace the previous Knowledge Base article KB944011.

After applying Service Pack 2 on your Windows Server 2003 computer, you may experience one or more of the following symptoms:

1. If it is an Exchange server, Exchange Queues become clogged in the MAPI delivery queue. Messages get stuck in this queue and cannot be delivered properly.

2. ActiveSync may not work on the Exchange Server 2003.

3. For the IIS server, browsing the Public and/or Default Website in IIS results in error "Page cannot be displayed".

4. Non-Paged Pool (KERNEL) memory becomes exhausted.

5. For a printer server, the printing job may be partially missing.

6. For a SQL server, if you have an application that connects to SQL Server by using TCP/IP, you may intermittently receive one of the following error messages:

Error message 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB] General Network error. Check your network documentation

Error message 2
ERROR [08S01] [Microsoft][SQL Native Client]Communication link failure

Error message 3
System.Data.SqlClient.SqlException: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

The problem may be the result of combining the NIC driver, and the TCP Chimney feature that comes with the Scalable Networking Pack, which is included in Windows 2003 SP2.

The TCP Chimney feature is a stateful offload that is enabled to be the default in Windows Server 2003 Scalable networking Pack. TCP Chimney offload enables TCP/IP processing to be offloaded to network adapters that can handle the TCP/IP processing in hardware.

With TCP Chimney feature, some NIC driver cause high NonPaged pool usage. The tag is MmCm.

Once there is less than 30MB of available non paged pool memory, HTTP.sys starts rejecting connections.

Contact the NIC manufacture to upgrade the NIC driver to the latest version. If the latest driver still does not resolve the issue, use the workaround below.



Workaround:

Disable the TCP Chimney feature on the server using the Netsh.exe tool. Specifically, to turn off TCP Chimney by using the Netsh.exe tool, we followed these steps:

1. Click Start, click Run, type cmd, and then click OK.

2. At the command prompt, type:

Netsh int ip set chimney DISABLED

3. Press the ENTER key.


For more information on the TCP Chimney feature and the Scalable Networking Pack,
see the following article:

912222 The Microsoft Windows Server 2003 Scalable Networking Pack release
http://support.microsoft.com/default.aspx?scid=kb;EN-US;912222


Query words: NetXtreme 2003 SP2 Scalable Networking Pack MmCm Tag TCP Chimney broadcom KB944011 944011

MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.