Cluster generic script resource %1 timed out. %2 script entry point did not complete execution in a timely manner. This could be due to an infinite loop or a hang in this entry point, or the pending timeout may be too short for this resource. Please review the %2 script entry point to make sure there's no infinite loop or a hang in the script code, and then consider increasing the pending timeout value if necessary. In a command shell, run "cluster res "%1" /prop PersistentState=0" to disable this resource, and then run "net stop clussvc" to stop the cluster service. Ensure that any problem in the script code is fixed. Then run "net start clussvc" to start the cluster service. If necessary, ensure that the pending time out is increased before bringing the resource online again.
Cluster disk resource "%1": Mount point "%2" for clustered target volume "%3" is not acceptable because the target volume ...
Cluster disk resource "%1": Mount point "%2" for target volume "%3" is not acceptable because the target volume is not a ...
Cluster disk resource "%1": The VolGuid list maintained for this disk resource appears to have too many entries. If all the ...
Cluster File Share '%1' could not be made a DFS root share because a DFS root could not be created on this node. This could ...
Cluster generic script resource %1 timed out. %2 script entry point did not complete execution in a timely manner. This could ...
Cluster generic script resource %1: Request to perform the %2 operation will not be processed. This is because of a previous ...
Cluster IP Address resource '%1' cannot be brought online because address %2 is already present on the network. Please check ...
Cluster IP Address resource '%1' cannot be brought online because the adapter name parameter is invalid. Please check your ...
Cluster IP Address resource '%1' cannot be brought online because the Address parameter is invalid. Please check your network ...