UI Translation
Deutsch (Deutschland)
German (Germany)
Español (España)
Spanish (Spain)
Français (France)
French (France)
italiano
Italian
日本語
Japanese
한국어
Korean
Português
Portuguese
Русский
Russian
English
English (United States)
Windows 8.1
...
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
...
509
Cluster network name resource '%1' was unable to identify any IP addresses to register with a DNS server. Ensure that there ...
Cluster node %1 could not to join the cluster because it failed to communicate over the network with any other node in the ...
Cluster node %1 could not to join the cluster because it failed to establish a TCP connection to node(s) %2. Verify the network ...
Cluster node %1 could not to join the cluster because it failed to establish a TCP connection using Microsoft Failover Cluster ...
Cluster node %1 could not to join the cluster because it failed to establish a UDP connection to node(s) %2. Verify the network ...
Cluster node '%1' lost communication with cluster node '%2'. Network communication was reestablished. This could be due to ...
Cluster node '%1' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. ...
Cluster physical disk resource '%1' cannot be brought online because the associated disk could not be found. The expected ...
Cluster physical disk resource '%1' failed. The Cluster Shared Volume was put in failed state with the following error: '%2' ...
Cluster resource '%1' cannot be brought online because the associated service failed an attempted restart. The error code ...
Cluster resource '%1' cannot be brought online because the associated service failed to start. The service return code is ...
Cluster resource '%1' in clustered role '%2' has exceeded the maximum number of consecutive failures. It has exhausted the ...
Cluster resource '%1' in clustered role '%2' has received a critical state notification. For a virtual machine this indicates ...
Cluster resource '%1' in clustered role '%2' has received a critical state notification. For a virtual machine this indicates ...
Cluster resource '%1' in clustered role '%2' has taken more than one minute to respond to a control code. The control code ...
Cluster resource '%1' in clustered role '%2' has transitioned from state %3 to state %4. Cluster resource '%1' is waiting ...
Cluster resource '%1' in clustered role '%2' rejected a move request to node '%3'. The error code was '%4'. Cluster resource ...
Cluster resource '%1' of type '%3' in clustered role '%2' failed due to an attempt to block a required state change in that ...
Cluster resource '%1' of type '%3' in clustered role '%2' failed. Based on the failure policies for the resource and role, ...
Cluster resource '%1' of type '%3' in clustered role '%2' failed. The error code was '%4'. Based on the failure policies ...
Cluster resource '%1' of type '%3' in clustered role '%2' failed. The error code was '%5' ('%4'). Based on the failure policies ...
Cluster service failed to change the trace log size. Please verify the ClusterLogSize setting with the 'Get-Cluster | Format-List ...
Cluster service failed to create a cluster identity token for Cluster Shared Volumes. The error code was '%1'. Ensure the ...
Cluster service failed to disable Internet Protocol security (IPsec) on the Failover cluster virtual adapter '%1'. This could ...
Cluster Service failed to move the restored cluster hive at '%1' to '%2'. This may prevent the restore operation from succeeding ...
Cluster service failed to retrieve the list of clustered disks while destroying the cluster. The error code was '%1'. If ...
Cluster service failed to set the permissions (ACL) on the Cluster Shared Volumes root directory '%1'. The error was '%2'. ...
Cluster service failed to set the permissions on the cluster computer object '%1'. Please contact your network administrator ...
Cluster service failed to start the cluster log trace session. The error code was '%2'. The cluster will function properly, ...
Cluster service failed to update the cluster configuration data on the witness resource. Please ensure that the witness resource ...
Cluster service on node %1 did not reach the running state. The error code is 2!lx!. For more information check the cluster ...
Cluster settings cannot be modified to use a hardware load balancer. The number of servers currently in the cluster exceeds ...
Cluster Shared Volume '%1' ('%2') backup was turned on. Once the backup application completes the backup process, the Cluster ...
Cluster Shared Volume '%1' ('%2') has entered a paused state because of '%3'. All I/O will temporarily be queued until a ...
Cluster Shared Volume '%1' ('%2') is no longer accessible from this cluster node because of error '%3'. Please troubleshoot ...
Cluster Shared Volume '%1' ('%2') is no longer directly accessible from this cluster node. I/O access will be redirected ...
Cluster Shared Volume '%1' ('%2') maintenance was turned on. This volume will not be accessible by the highly available service ...
Cluster Shared Volume '%1' ('%2') redirected access was turned on. Access to the storage device will be redirected over the ...
Cluster Shared Volume '%1' ('%3') has identified one or more active filter drivers on this device stack that could interfere ...
Cluster Shared Volume '%1' ('%3') has identified one or more active volume drivers on this device stack that could interfere ...
Cluster Shared Volumes redirection performance object consists of counters that show information about block level I/O activity ...
Cluster Shared Volumes root directory '%1' already exists. The directory '%1' was renamed to '%2'. Please verify that applications ...
Cluster to which this Terminal server belongs. Typically, it is a DNS entry which represents the Virtual IP address of computers. ...
Cluster updating has started. When you close the wizard, you can view the progress of the Updating Run on the main console. ...
Cluster validation has completed successfully. The configuration appears to be suitable for clustering. Review any warnings ...
Cluster validation has completed. Review all warnings listed in the validation testing report. Failover clustering is supported ...
Cluster validation testing cannot complete. Unexpected errors were encountered. Review the validation testing report and ...
Cluster validation testing has completed, but one or more tests indicate that the configuration is not suitable for failover ...
Cluster validation testing has completed. One or more tests indicate that the current configuration may not suitable for ...
Cluster validation testing has completed. The current configuration is not suitable for failover clustering. Failover clustering ...
Cluster-Aware Updating (CAU) accesses hotfixes that are stored in a hotfix root folder. CAU chooses the file access method ...
Cluster-Aware Updating (CAU) cannot create the CAU clustered role because a replicated local user resource could not be created. ...
Cluster-Aware Updating (CAU) has detected that Windows Firewall is enabled on node "{0}". However CAU is unable to enable ...
Cluster-Aware Updating (CAU) is not supported on this cluster type. To use CAU, the failover cluster must have an administrative ...
Cluster-Aware Updating cannot perform one or more of the following actions on this failover cluster: 1)Use pre-update or ...
Cluster-Aware Updating cannot update this failover cluster if the Cluster service is not running on all nodes in the cluster. ...
Cluster-Aware Updating cannot update this failover cluster in a deployment scenario where the failover cluster must directly ...
Cluster-Aware Updating has detected that cluster node "{0}" was already suspended. Cluster-Aware Updating will not update ...
Cluster-Aware Updating may not be able to update this failover cluster. An Updating Run that applies updates that require ...
Clustered disk with ID '%2' was not released by the Partition Manager while destroying the cluster. The error code was '%1'. ...
Clustered disks can be added to Cluster Shared Volumes or assigned exclusively to clustered roles. Navigate to Disks to add, ...
Clustered disks have been released by the Partition Manager while destroying the cluster. These disks will be left in an ...
Clustered role '%1' has exceeded its failover threshold. It has exhausted the configured number of failover attempts within ...
Clustered role '%2' was taken offline. This role was preempted by the higher priority clustered role '%1'. The cluster service ...
Clustered service or application '%1' has exceeded its failover threshold. It has exhausted the configured number of failover ...
Clustered storage pools are groups of physical disks that are logically combined and managed as one or more virtual disks ...
Clustering Services have been detected on this node. Certain clustering functionality may be impaired by Internet Connection ...
Clustering Services have been detected on this node. Certain clustering functionality may be impaired by the Network Bridge. ...
Clusters provide high availability for applications and services installed on clustered servers. High availability means ...
CMD.EXE was started with the above path as the current directory. UNC paths are not supported. Defaulting to Windows directory. ...
cmd.exe,"/k echo This environment should only be used to recover from a failed installation. Type EXIT and press Enter to ...
Cmdlet parameters mapped to collection fields need to have a valid non-null type. The following parameters do not have valid ...
Coalesce is either not used properly or this form is not currently supported. Check for possible mixing of grouping with ...
Code integrity determined that a file does not meet the security requirements to load into a process. This could be due to ...
Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification ...
Deutsch (Deutschland)
German (Germany)
Español (España)
Spanish (Spain)
Français (France)
French (France)
italiano
Italian
日本語
Japanese
한국어
Korean
Português
Portuguese
Русский
Russian
English
English (United States)
Search
×