Windows 8

  1. The Cluster API Calls/sec performance counter shows the number of new cluster API calls made against the cluster per second. ...
  2. The Cluster API Handles performance object consists of counters that show information about open handles against the cluster ...
  3. The Cluster Checkpoint Manager performance object consists of counters that show information about cluster Checkpoint Manager. ...
  4. The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class. ...
  5. The cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource. ...
  6. The Cluster Database performance object consists of counters that show information about cluster database and operations ...
  7. The Cluster detected that this node is slower than others and degrade Cluster performance. If the condition persists, check ...
  8. The cluster disk driver (clusdisk.sys) startup type on node {0} is set to SERVICE_DISABLED (0x4). The recommended value is ...
  9. The cluster does not use shared storage. A cluster must use a hardware solution based either on shared storage or on replication ...
  10. The Cluster Global Update Manager Messages performance object consists of counters that show information about cluster Global ...
  11. The cluster has an even number of nodes. Consider changing to the Node and Disk Majority quorum configuration to improve ...
  12. The cluster has an odd number of nodes and a disk witness. A disk witness in this scenario can decrease cluster availability. ...
  13. The cluster IP address and dedicated IP address cannot be identical. Type a different cluster IP and dedicated IP addresses. ...
  14. The cluster IP addresses are shared by every member of the cluster for load balancing. The first IP address listed is considered ...
  15. The cluster key protection password is not available. The imported trusted publishing domain contains an AD RMS internally ...
  16. The cluster key protection password is not available. The imported trusted publishing domain contains an AD RMS internally ...
  17. The cluster management item is no longer available. A possible cause is that the connection to the cluster is no longer available. ...
  18. The cluster management name "{0}" is not a valid NetBIOS name. NetBIOS names must contain only alphanumeric characters. The ...
  19. The cluster management name "{0}" is not in a valid DNS format. DNS names must contain only alphanumeric characters. The ...
  20. The Cluster Multicast Request-Response Messages performance object consists of counters that show information about cluster ...
  21. The Cluster Name and Domain Join Wizard has successfully completed. You must restart both nodes after closing the wizard. ...
  22. The cluster network address is not valid. The address must be of the form xx-xx-xx-xx-xx-xx or xx:xx:xx:xx:xx:xx. Type valid ...
  23. The cluster network is not valid for an IPv6 Tunnel resource. Check the configuration of the IP Address resource on which ...
  24. The cluster network is the only one configured for internal cluster communication between two or more active cluster nodes. ...
  25. The Cluster Network Messages performance object consists of counters that show information about cluster messages sent and ...
  26. The Cluster Network Reconnections performance object consists of counters that show information about cluster reconnects ...
  27. The cluster node '{0}' was evicted from the cluster, but was not fully cleaned up. Please see the Failover Clustering application ...
  28. The cluster node was evicted from the cluster successfully, but the node was not cleaned up. To determine what cleanup steps ...
  29. The cluster node {0} cannot access the hotfix file share. This might be caused by a misconfiguration of the security settings ...
  30. The cluster node {0} was evicted from the cluster successfully, but the node was not cleaned up. To determine what cleanup ...
  31. The cluster or computer specified may not be running a supported Windows Server version. The following error was encountered: ...
  32. The cluster or computer you specified could not be found. Please make sure the cluster or computer is accessible and that ...
  33. The cluster property "ClusterLogLevel" is set with a value of {0}. The default level is {1}. A value less than {1} is not ...
  34. The cluster property "ClusterLogLevel" is set with a value of {0}. The default level is {1}. The value of {0} causes verbose ...
  35. The cluster property "ClusterLogSize" is set with a value less than default value of {0}. This value specifies the size of ...
  36. The cluster property QuorumArbitrationTimeMax value is set to {0}. The default value is {1}. This value specifies the number ...
  37. The Cluster Resource Control Manager performance object consists of counters that show information about cluster resources ...
  38. The cluster Resource Hosting Subsystem (RHS) stopped unexpectedly. An attempt will be made to restart it. This is usually ...
  39. The Cluster Resources performance object consists of counters that show information about cluster resources grouped by resource ...
  40. The Cluster service cannot be started. An attempt to read configuration data from the Windows registry failed with error ...
  41. The Cluster service cannot identify node '%1' as a member of failover cluster '%2'. If the computer name for this node was ...
  42. The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node ...
  43. The cluster service detected that the witness disk designation has changed - usually indicating that the current node has ...
  44. The Cluster service encountered an error during node cleanup. You may be unable to create or join a cluster with this machine ...
  45. The Cluster service encountered some storage errors while trying to bring storage pool online. Run cluster storage validation ...
  46. The Cluster service failed to bring clustered service or application '%1' completely online or offline. One or more resources ...
  47. The Cluster service failed to bring clustered service or application '%1' completely online or offline. One or more resources ...
  48. The cluster service failed to properly cleanup a clustered disk with ID '%2' while destroying the cluster. The error code ...
  49. The Cluster service failed to start because it was unable to register interface(s) with the RPC service. The error code was ...
  50. The cluster service failed to start. This was because the failover cluster virtual adapter failed to initialize the miniport ...
  51. The Cluster service failed to update the cluster database (error code '%1'). Possible causes are insufficient disk space ...
  52. The cluster service has detected that the failover cluster virtual adapter has stopped. This is expected when hot replace ...
  53. The cluster service has determined that this node does not have the latest copy of cluster configuration data. Therefore, ...
  54. The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between ...
  55. The Cluster Service that the Microsoft iSCSI Software Target service depends on is either disabled or not running. Use the ...
  56. The Cluster Service was unable to access network adapter '%1'. Verify that other network adapters are functioning properly ...
  57. The Cluster Shared Volumes feature is only supported for use with {0} Hyper-V role. Creation, reproduction and storage of ...
  58. The Cluster Shared Volumes performance object consists of counters that show information about I/O activity at the CSV volume ...
  59. The cluster storage pool is not in the correct state to perform validation. In order to perform validation on the storage ...
  60. The cluster subnet mask is required. Network Load Balancing has automatically generated a subnet mask. If you do not want ...
  61. The cluster that this computer is joining uses a different cryptographic provider (CSP) than the one specified. Install Active ...
  62. The cluster to which you are attempting to connect is not a version of the cluster supported by this version of Failover ...
  63. The cluster to which you are trying to join this server is not currently provisioned as either a root or licensing-only cluster. ...
  64. The cluster URL is either empty or mal-formatted. It must in the form of http(s)://domain/_wmcs/licensing or http(s)://domain/_wmcs/certification. ...
  65. The Cluster-Aware Updating clustered role has been moved or failed over {0} times during the Updating Run, which indicates ...
  66. The clustered disks could not be enumerated or could not be put into cluster maintenance mode. Check the System event log ...
  67. The clustered RD Connection Broker server for the cluster {0} is not a part of the server pool. Add the server {1} to the ...
  68. The clustered role will not be started because the resources may need additional configuration. Finish configuration, and ...
  69. The clustered role {0} has a value other than NULL for the property "AntiAffinityClassNames." The value of this property ...
  70. The clustered virtual machine '{0}' is no longer available on computer '{1}'. The virtual machine may have been moved, taken ...
  71. The cmdlet "{0}" or the alias "{1}" cannot be present when "{2}","{3}","{4}" or "{5}" keys are specified in the session configuration ...
  72. The cmdlet cannot be run because the required migration manifests are missing. Verify that the dlmanifests folder exist at ...
  73. The cmdlet cannot be run because the required migration manifests are missing. Verify that the replacementmanifests folder ...
  74. The cmdlet cannot configure the {0} specific settings for the network adapter with physical address {1} because the protocol ...
  75. The cmdlet cannot connect to the destination server. For more information, see "Data Migration Connectivity" in the Troubleshooting ...