Microsoft KB Archive/933343

= The Web browser may stop responding when you try to view a Web page that is hosted in IIS 6.0 on a computer that is running an x64-based version of Windows Server 2003 =

Article ID: 933343

Article Last Modified on 3/6/2007

-

APPLIES TO


 * Microsoft Internet Information Services 6.0

-



SYMPTOMS
When you try to view a Web page that is hosted in Microsoft Internet Information Services (IIS) 6.0 on a computer that is running an x64-based version of Microsoft Windows Server 2003, the Web browser may stop responding. Additionally, a warning message that resembles the following may be logged in the System event log:

Event Type: Warning

Event Source: W3SVC

Event Category: None

Event ID: 1009

Description:

A process serving application pool 'DefaultAppPool' terminated unexpectedly. The process id was '4152'. The process exit code was '0xc0000005'.



CAUSE
This issue occurs if the following conditions are true:
 * IIS 6.0 starts a 32-bit worker process (W3wp.exe).
 * The Web site requires Secure Sockets Layer (SSL).
 * Client certificate mapping is enabled for the Web site.
 * Two or more rules are enabled on the Many-to-1 tab in the Account Mappings dialog box.



RESOLUTION
To resolve this issue, follow these steps.

Note The following steps remove the certificate matching rules for the Web site.  Back up the IIS metabase. To back up the IIS metabase, follow these steps:  Click Start, click Run, type Inetmgr.exe, and then click OK. Right-click the server that you want to configure, point to All Tasks, and then click Backup/Restore Configuration. Click Create Backup, type a name for the backup, and then click OK.

Note If you want to encrypt the backup file, click to select the Encrypt backup using password check box, and then type the password that you want two times.  Stop the IIS Admin Service service. To do this, follow these steps:  Click Start, click Run, type Services.msc, and then click OK.</li> Right-click IIS Admin Service, and then click Stop.</li></ol> </li> Open the Metabase.xml file in Notepad.

Note By default, the Metabase.xml file is located in the System32\Inetsrv folder.</li>  Locate and then delete each node in the Metabase.xml file in which the Name attribute is UnkknownName_2088. For example, you should delete the following node if it appears in the Metabase.xml file: <Custom Name=&quot;UnknownName_2088&quot; ID=&quot;2088&quot; Value=&quot;496344625800000010000000400000009319afe91d1f526d8b613799884407c574c15810b257aff93c6b8c1c8e587247851&quot; Type=&quot;BINARY&quot; UserType=&quot;IIS_MD_UT_SERVER&quot; Attributes=&quot;SECURE&quot; /> Note Only delete nodes that have the <Custom> tag and the Name attribute is UnkknownName_2088. Do not delete any other text in the Metabase.xml file. </li> Click File, and then click Save.</li> Exit Notepad.</li> Click Start, click Run, type MMC /32, and then click OK.</li> On the File menu, click Add/Remove Snap-in.</li> Click Add, click Internet Information Services (IIS) Manager, click Add, click Close, and then click OK.</li> Expand Internet Information Services (IIS) Manager, expand the computer that you want to configure, and then expand Web Sites.</li> Right-click the Web site that you want to configure, and then click Properties.</li> On the Directory Security tab, click Edit under Secure communications.</li> Click to select the Enable client certificate mapping check box, and then click Edit.</li> On the Many-to-1 tab, add the certificate mapping rules that you want, and then click OK three times.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
After you follow the steps that are listed in the &quot;Resolution&quot; section, you must use the 32-bit Microsoft Management Console (MMC) to view the certificate mapping rules. If you configure IIS 6.0 to start a 64-bit worker process, you must repeat steps 1-6 in the &quot;Resolution&quot; section. Then, re-create the certificate mapping rules in the 64-bit version of IIS Manager.

Keywords: kbtshoot kbprb KB933343

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.