BUG: You receive Cluster Administrator error messages and any subsequent attempt to move the SQL Server Resource Group to the newly rebuilt node fails

View products that this article applies to.

This article was previously published under Q295589

BUG #: 353091 (SHILOH_BUGS)

Expand all | Collapse all

SYMPTOMS

If either of the following conditions is true

You apply SQL Server 2000 service pack to a local (non-clustered) instance of SQL Server, and then you upgrade that local instance to a virtual instance. And you do this by following SQL Server Books Online topic "How to upgrade from a default instance to a default clustered instance of SQL Server 2000 (Setup)"

-or-
You upgrade a virtual instance to SQL Server 2000 with any SQL Server released SQL Server service pack, and then you rebuild a node in the cluster (in other words, remove it and then add it back) or remove a participating node for any other reason and add it back later. And you do this by following the SQL Server Books Online topic "How to recover from failover cluster failure in Scenario 1"

any subsequent attempt to move the SQL Server Resource Group to the newly rebuilt node fails, and you receive one of the following Cluster Administrator error messages:

An error occurred attempting to read properties for the 'SQL IP Address1(virtual_server_name)' resource:
The specified node does not support a resource of this type. This may be due to version inconsistencies or due to the absence of the resource DLL on this node.
Error ID: 5079 (000013d7)
Do you want to ignore this error and continue?

An error occurred attempting to move the 'SQL Group' group: A cluster node is not available for this operation. Error ID: 5005 (0000138d).

If you ignore the error message, a failover is not permitted.

An inspection of the original node's SQL Server binn folder reveals that it contains a version of the Sqlservr.exe file that is numerically higher than the original released version of the Sqlservr.exe file. When you run the following query against the virtual server that you are maintaining, a product version of 8.00.194 is returned:

Select @@version

An inspection of the second (or rebuilt) node's SQL Server binn folder reveals that it contains a Sqlservr.exe file that has the following properties:

Product Version: 8.00.194
Size: 7.09 MB (7,442,493 bytes)
Modified: Sunday, August 06, 2000, 1:50:20 AM

Back to the top

CAUSE

This behavior occurs if you use the SQL Server compact disc to upgrade the virtual server (or to add a new node). Under these circumstances, the SQL Server binaries are copied from that compact disc (instead of from the service pack folder, if it exists) onto the new or second node.

Back to the top

WORKAROUND

To work around this issue, run the service pack setup against the virtual instance after you rebuild a node, or run the service pack setup after you upgrade from a default instance to a virtual instance.

Back to the top

STATUS

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

Back to the top

MORE INFORMATION

If you use the steps in the "How to add nodes to an existing virtual server (Setup)” SQL Server Books Online topic to add the node, the Setup program checks for an existing instance of SQL Server 2000 instance on the new node. If the Setup program finds an existing instance of SQL Server 2000, the Setup program removes it before it installs the new node. This change causes the binaries for that instance to be restored to the original released version of the file. During setup, you receive the following error message:

Setup has detected that pre-install cleanup operations are necessary on the node(s), <Node Name>, that you have chosen to add to your cluster. This may be because some of the nodes are waiting for a Service Pack to be applied as part of a pending Add Node operation. This will require that the Cluster Service be stopped on the affected node(s) during cleanup, and will cause any clustered applications running on them to fail over. The Cluster Service will be restarted once the pre-install cleanup is complete. Do you wish to continue?

There are other causes of the error message described in the "Symptoms" section of this article, for which this article's workaround are not applicable.

Back to the top