Evicting a Node in a Cluster Can Cause Problems in SQL 6.5 or 7.0

This article was previously published under Q225092
This article has been archived. It is offered "as is" and will no longer be updated.
It may seem easy to troubleshoot a node in a cluster by evicting the node and reinstalling the cluster service. This process can be disastrous to the SQL Virtual Machine and make you reinstall SQL 6.5 or 7.0.
Normally evicting a cluster node is not a problem. Reinstalling the cluster and joining the other node typically replicates the proper entries. However, when an SQL virtual machine is involved, it becomes complex.

Before you evict a Cluster Node running SQL, you must uninstall the SQL Virtual Machine first. The process is to run the cluster Wizard for SQL Virtual machine (not the SQL install) and uncluster SQL on both nodes. The path on the SQL CD-ROMs are:
SQL 6.5 = \i386\cluster
SQL 7.0 = \x86\cluster
For Alpha computers, it would be in the Alpha folders.

Changing the name of the computer forces an eviction and has a similar effect because after the computer name is changed, it does not communicate with the other node.

The evict a node, follow these steps:
  1. In Cluster Administrator, right-click the node name.
  2. Click Evict Node.
NOTE: If you evict a node like this while running an SQL Virtual cluster, you need to completely reinstall SQL.
MSCS SQL 6.5 7.0

Article ID: 225092 - Last Review: 10/20/2013 22:44:22 - Revision: 1.1

Microsoft Windows NT Server 4.0 Enterprise Edition

  • kbnosurvey kbarchive kbenv kbfaq kbinfo kbinterop kbnofix KB225092
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)