An operation that was part of destroying the cluster did not succeed. Try restarting the server to see if this resolves the error. If not, use commands to force cleanup on former cluster nodes, and to force the clearing of persistent reservations on disks formerly used by the cluster. These commands help ensure that the cluster configuration has been completely removed.
If you do not currently have Event Viewer open, see 'Opening Event Viewer and viewing events related to failover clustering.' If the event contains an error code that you have not yet looked up, see 'Finding more information about error codes that some event messages contain.'
To perform the following procedures, you must be a member of the local Administrators group on the server, or you must have been delegated the equivalent authority.
To force cleanup on a former cluster node after the cluster has been destroyed:
To force the clearing of persistent reservations on a disk formerly used by the cluster:
To open Event Viewer and view events related to failover clustering:
To find more information about the error codes that some event messages contain:
On the former cluster node that you want to clean up, open an elevated Command Prompt window. To do this, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Type:
CLUSTER NODE /FORCECLEANUP
On one or more nodes in the cluster, open Disk Management (which is in Server Manager under Storage) and see if any disks formerly used by the cluster are visible from one of the nodes. If they are, note the node and the number that Disk Management uses to refer to that disk. For example, if the disk is listed as Disk 4 in Disk Management, note the number 4.
On a node from which a formerly-clustered disk is visible in Disk Management, open an elevated Command Prompt window. To do this, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Type:
CLUSTER NODE /CLEARPR:disknumber
where disknumber is the number of the disk as it appeared in Disk Management.
If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click System.
To filter the events so that only events with a Source of FailoverClustering are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources box, select FailoverClustering. Select other options as appropriate, and then click OK.
To sort the displayed events by date and time, in the center pane, click the Date and Time column heading.
View the event, and note the error code.
Look up more information about the error code in one of two ways:
Search System Error Codes ( http://go.microsoft.com/fwlink/?LinkId=83027).
Click Start, point to All Programs, click Accessories, click Command Prompt, and then type:
NET HELPMSG errorcode
Home
ENU