Microsoft KB Archive/289107

= BUG: Incorrect Reference to the Second Virtual Server Instance Name =

Article ID: 289107

Article Last Modified on 2/22/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Enterprise Edition

-



This article was previously published under Q289107



BUG #: 352249 (SHILOH)



SYMPTOMS
In Microsoft SQL Server Books Online, in the &quot;Failover Clustering Example&quot; topic, there is an incorrect reference to the second virtual server instance name in the illustration that is shown.

SQL Server 2000 Book Online states:

&quot;Run the Setup program again on CLUSTERNODEB. Create a new virtual server named &quot;SQLCLUSTB&quot; (in a different Microsoft Cluster Service (MSCS) cluster group) and install an instance named &quot;Inst1&quot; that can run on both CLUSTERNODEA and CLUSTERNODEB. From this point forward, connect to the server by specifying SQLCLUSTB\Inst1 as the connection string.&quot;

Correction

In the illustration that is shown in the example, the clients are instructed to connect to &quot;SQLCLUSTB&quot; as the second virtual server instance, which is incorrect. The correct second virtual server instance is SQLCLUSTB\INST1.



STATUS
Microsoft has confirmed this to be a problem in SQL Server 2000.

Additional query words: Books Online Failover Clustering

Keywords: kbbug kbpending KB289107

-

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

© Microsoft Corporation. All rights reserved.