Article ID: 925342
Article Last Modified on 10/11/2007
APPLIES TO
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Standard x64 Edition
SYMPTOMS
Consider the following scenario:
- You have a Web page that uses a Common Gateway Interface (CGI) in Microsoft Internet Information Services (IIS) 6.0.
- The Web page in IIS 6.0 is running on a Japanese version of Microsoft Windows Server 2003.
- A client computer sends a request to the Web page. The request includes an HTTP header that contains invalid data in a multibyte character set (MBCS) string.
In this scenario, the W3wp.exe process stops responding.
CAUSE
This problem occurs when a CGI is run on a Japanese version of Windows Server 2003 and when one request includes an HTTP header that contains invalid data in an MBCS string. This problem also occurs on an English version of Windows Server 2003 that has the Language for non-Unicode programs option set to Japanese in Regional and Language Options.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
Hotfix information
Prerequisites
You must install Windows Server 2003 Service Pack 1 (SP1) before you apply this hotfix.
Restart requirement
You must 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 item in Control Panel.
Windows Server 2003 with SP1, 32-bit versions
| File name | File version | File size | Date | Time | Platform | SP requirement |
|---|---|---|---|---|---|---|
| Iisutil.dll | 6.0.3790.2800 | 167,936 | 26-Sep-2006 | 12:28 | x86 | SP1 |
| W3core.dll | 6.0.3790.2800 | 349,184 | 26-Sep-2006 | 12:28 | x86 | SP1 |
Windows Server 2003, x64-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Iisutil.dll | 6.0.3790.2800 | 324,608 | 26-Sep-2006 | 12:02 | x64 | SP1 | Not Applicable |
| W3core.dll | 6.0.3790.2800 | 570,880 | 26-Sep-2006 | 12:02 | x64 | SP1 | Not Applicable |
| Wiisutil.dll | 6.0.3790.2800 | 167,936 | 26-Sep-2006 | 12:02 | x86 | SP1 | WOW |
| Ww3core.dll | 6.0.3790.2800 | 349,184 | 26-Sep-2006 | 12:02 | x86 | SP1 | WOW |
Windows Server 2003 with SP1, Itanium-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Iisutil.dll | 6.0.3790.2800 | 436,736 | 26-Sep-2006 | 12:01 | IA-64 | SP1 | Not Applicable |
| W3core.dll | 6.0.3790.2800 | 1,059,840 | 26-Sep-2006 | 12:01 | IA-64 | SP1 | Not Applicable |
| Wiisutil.dll | 6.0.3790.2800 | 167,936 | 26-Sep-2006 | 12:01 | x86 | SP1 | WOW |
| Ww3core.dll | 6.0.3790.2800 | 349,184 | 26-Sep-2006 | 12:01 | x86 | SP1 | WOW |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.
MORE INFORMATION
After you apply this hotfix, the W3wp.exe process will not stop responding when this scenario occurs. However, you will receive an "HTTP 500" error message in this scenario.
Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver kbwinserv2003presp2fix kbwinserv2003sp2fix KB925342
