Article ID: 886810 - View products that this article applies to.
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows Registry
When you access and view the contents of a client certificate by using the Request object’s ClientCertificate collection (Request.ClientCertificate) in Microsoft Internet Information Services (IIS) 6.0, the values in the Request.ClientCertificate object are not displayed correctly. Additionally, the values in the Request.ClientCertificate object may not be the same as the values that are displayed in IIS 5.0.
This problem occurs because of a change in the output format of the Request object’s ClientCertificate collection in IIS 6.0 when compared to the output format in IIS 5.0. In IIS 5.0, binary large object (BLOB) arrays are converted to basic strings (BSTR), and then sent to the client. In IIS 6.0, binary large object arrays are sent to the client as binary large objects. If binary large objects are not read correctly by the client, the values in the Request.ClientCertificate object may not be displayed correctly.
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesNo prerequisites are required.
Restart requirementYou do not have to restart your computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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 tool in Control Panel.
Windows Server 2003
Date Time Version Size File name -------------------------------------------------------------- 19-Oct-2004 22:39 6.0.3790.224 380,416 Asp.dll
Windows Server 2003 64-bit edition
Date Time Version Size File name Platform ----------------------------------------------------------------------- 19-Oct-2004 10:09 6.0.3790.224 983,040 Asp.dll IA-64
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
After you install the hotfix, create the
DisableCertificateBlobAsArrayregistry entry. To do this, follow these steps:
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.