BUG: The second cluster node is not listed as a possible owner in Cluster Administrator (319601)

The information in this article applies to:

Microsoft SQL Server 2000 Developer Edition SP1
Microsoft SQL Server 2000 Developer Edition SP2
Microsoft SQL Server 2000 Enterprise Edition SP1
Microsoft SQL Server 2000 Enterprise Edition SP2

This article was previously published under Q319601

BUG #: 356856 (SHILOH_BUGS)

SYMPTOMS

When you run the SQL Server Setup program, and you remove one of the nodes from the Configured Nodes list, and you then run Setup again to add the removed node back to Configured Nodes list, you may see (in Cluster Administrator) that all the SQL Server Resources except the Disk resource have only the first node displayed as a possible owner. This behavior can occur in both SQL Server 2000 Service Pack 1 (SP1) and SQL Server 2000 Service Pack 2 (SP2).

WORKAROUND

To work around this problem, apply the respective SQL Server service pack (SQL Server 2000 SP1 or SQL Server 2000 SP2) after you add the node back to the Configured Nodes list.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

If you do not use the workaround, the group that hosts the SQL Server resources does not fail over.

REFERENCES

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

295589 BUG: Correcting Mismatched Binaries on SQL Clustered Virtual Server

Modification Type:	Major	Last Reviewed:	3/14/2006
Keywords:	kbbug kbpending KB319601 kbAudDeveloper