Microsoft KB Archive/895081

= FIX: SQL Server 2000 may load an incorrect certificate when the ClusterName value is longer than the ClusterIpAddr value =

Article ID: 895081

Article Last Modified on 11/2/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Personal Edition
 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition 64-bit

-



BUG #: 472970 (SQL Server 8.0)



SYMPTOMS
In Microsoft SQL Server 2000, the ClusterName value and the ClusterIpAddr value are in the following registry subkey:

When the ClusterName value is longer than the ClusterIpAddr value, SQL Server 2000 may load an incorrect certificate.



RESOLUTION
To resolve this problem, obtain the latest service pack for SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 How to obtain the latest SQL Server 2000 service pack



WORKAROUND
To work around this problem, use a shorter cluster name.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section. This problem was first corrected in SQL Server 2000 Service Pack 4.



MORE INFORMATION
A SQL Server 2000 cluster reads information from the registry on startup to determine the cluster name. Then, the SQL Server 2000 cluster searches for certificates with that cluster name in the subject so that the SQL Server 2000 cluster can perform encryption.

Keywords: kbtshoot kbprb KB895081

-

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

© Microsoft Corporation. All rights reserved.