UI Translation

Windows Server 2003

  1. Cluster disk resource "%1" is corrupt. Run 'ChkDsk /F' to repair problems. The volume name for this resource is "%2". If ...
  2. Cluster disk resource "%1" is full or nearly at capacity. Move some of the unnecessary files from this disk to another volume ...
  3. Cluster disk resource "%1" quorum is full or nearly at capacity. The cluster service will attempt to start, but may fail ...
  4. Cluster disk resource "%1" unknown is full or nearly at capacity. Cluster service will attempt to start, but may fail because ...
  5. Cluster disk resource "%1": Mount point "%2" for clustered target volume "%3" cannot be verified as acceptable because the ...
  6. Cluster disk resource "%1": Mount point "%2" for clustered target volume "%3" cannot be verified as acceptable because the ...
  7. Cluster disk resource "%1": Mount point "%2" for clustered target volume "%3" cannot be verified as acceptable because the ...
  8. Cluster disk resource "%1": Mount point "%2" for clustered target volume "%3" cannot be verified as acceptable because the ...
  9. Cluster disk resource "%1": Mount point "%2" for clustered target volume "%3" is not acceptable as the source and target ...
  10. Cluster disk resource "%1": Mount point "%2" for clustered target volume "%3" is not acceptable because the cluster dependencies ...
  11. Cluster disk resource "%1": Mount point "%2" for clustered target volume "%3" is not acceptable because the source volume ...
  12. Cluster disk resource "%1": Mount point "%2" for clustered target volume "%3" is not acceptable because the target volume ...
  13. Cluster disk resource "%1": Mount point "%2" for target volume "%3" is not acceptable because the target volume is not a ...
  14. Cluster disk resource "%1": The VolGuid list maintained for this disk resource appears to have too many entries. If all the ...
  15. 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 ...
  16. Cluster generic script resource %1 timed out. %2 script entry point did not complete execution in a timely manner. This could ...
  17. Cluster generic script resource %1: Request to perform the %2 operation will not be processed. This is because of a previous ...
  18. Cluster IP Address resource '%1' cannot be brought online because address %2 is already present on the network. Please check ...
  19. Cluster IP Address resource '%1' cannot be brought online because the adapter name parameter is invalid. Please check your ...
  20. Cluster IP Address resource '%1' cannot be brought online because the Address parameter is invalid. Please check your network ...
  21. Cluster IP Address resource '%1' cannot be brought online because the configured role of cluster network '%2' does not allow ...
  22. Cluster IP Address resource '%1' cannot be brought online because the subnet mask parameter is invalid. Please check your ...
  23. Cluster IP Address resource '%1' has been moved to cluster network '%2' because its IP address and subnet mask match. To ...
  24. cluster name | cluster primary IP address - host within the cluster (default - ALL hosts): dedicated name | IP address | ...
  25. Cluster network '%1' is down. None of the available nodes can communicate using this network. If the condition persists, ...
  26. Cluster network '%1' is operational (up). All available server cluster nodes attached to the network can communicate using ...
  27. Cluster network '%1' is partitioned. Some attached server cluster nodes cannot communicate with each other over the network. ...
  28. Cluster Network Name '%1' could not be instantiated on its associated cluster network. No DNS servers were available and ...
  29. Cluster Network Name resource '%1' cannot be brought online because it is either configured to have no associated name service ...
  30. Cluster Network Name resource '%1' cannot be brought online because the name %2 is already present on the network. Please ...
  31. Cluster Network Name resource '%1' cannot be brought online because the name could not be added to the system for the following ...
  32. Cluster Network Name resource '%1' cannot be brought online because the name could not be added to the system. The associated ...
  33. Cluster Network Name was changed even though the core Cluster Network Name resource could not perform all the related changes. ...
  34. Cluster node %1 failed a critical operation. It will be removed from the active server cluster membership. Check that the ...
  35. Cluster node %1 was not able to obtain a multicast address from a MADCAP server for network %2 or to select one automatically. ...
  36. Cluster node %1 was removed from the active server cluster membership. Cluster service may have been stopped on the node, ...
  37. Cluster resource %1 timed out. If the pending timeout is too short for this resource, consider increasing the pending timeout ...
  38. Cluster resource '%1' failed to go online because its associated computer account (%2) exists in Active Directory and the ...
  39. Cluster resource monitor detected a deadlock possibly caused by invoking the '%4' entry point of resource DLL '%1', resource ...
  40. Cluster service could not join an existing server cluster and could not form a new server cluster. Cluster service has terminated. ...
  41. Cluster service could not write to a file (%1). The disk may be low on disk space, or some other serious condition exists. ...
  42. Cluster service did not find any network adapters with valid IP addresses installed in the system. The node will not be able ...
  43. Cluster service did not start because the current version of Windows is not correct. Cluster service runs only on Windows ...
  44. Cluster service discovered that the node is attached to a new network by adapter %1. A new network and a network interface ...
  45. Cluster service discovered that the node is now attached to cluster network '%1' by adapter %2. A new cluster network interface ...
  46. Cluster service encountered a fatal error. The vital quorum log file '%1' could not be found. If you have a backup of the ...
  47. Cluster service encountered a fatal error. The vital quorum log file '%1' is corrupt. If you have a backup of the quorum ...
  48. Cluster service failed to access the Cluster Network driver. The error code was %1. Please check Cluster service installation. ...
  49. Cluster service failed to delete an unused network interface from the server cluster configuration. The error code was %1. ...
  50. Cluster service failed to initialize due to an invalid file specification in the CLUSTERLOG environment variable. Please ...
  51. Cluster service failed to initialize the Windows Sockets interface. The error code was %1. Please check the network configuration ...
  52. Cluster service failed to obtain information about the network configuration of the node. The error code was %1. Check that ...
  53. Cluster service failed to register the interface for node '%1' on network '%2' with the server cluster network provider. ...
  54. Cluster service failed to restore a registry key for resource %1 when it was brought online. This error code was %2. Some ...
  55. Cluster service failed to save the registry key %1 when a resource was brought offline. The error code was %2. Some changes ...
  56. Cluster service failed to set the priority for cluster network %1. The error code was %2. Communication between server cluster ...
  57. Cluster service has successfully restored the cluster database to the quorum disk. Please verify that the restored configuration ...
  58. Cluster service is attempting to stop the active Cluster services on all other server cluster nodes as a part of the restore ...
  59. Cluster service is shutting down as requested by node %1 (%2). Check the system event log on node %1 to determine the reason ...
  60. Cluster service is shutting down because the current node is not a member of any server cluster. Cluster service must be ...
  61. Cluster service is shutting down because the membership engine detected a membership event while trying to join the server ...
  62. Cluster service is shutting down because the membership engine detected that the arbitration process for the quorum device ...
  63. Cluster service is shutting down because the membership engine detected the loss of connectivity to all other nodes in the ...
  64. Cluster service is shutting down because the membership engine failed to arbitrate for the quorum device. This could be due ...
  65. Cluster service is shutting down because the membership engine suffered an internal error. Cluster service will restart per ...
  66. Cluster service received a membership event while shutting down. Cluster service is shutting down immediately to facilitate ...
  67. Cluster to which this Terminal server belongs. Typically, it is a DNS entry which represents the Virtual IP address of computers. ...
  68. Clustering Services have been detected on this node. Certain clustering functionality may be impaired by Internet Connection ...
  69. Clustering Services have been detected on this node. Certain clustering functionality may be impaired by the Network Bridge. ...
  70. CMD.EXE was started with the above path as the current directory. UNC paths are not supported. Defaulting to Windows directory. ...
  71. CollectionSetting represents the association between a CollectionOfMSEs class and the Setting class(es) defined for them. ...
  72. Collects and stores network configuration and location information, and notifies applications when this information changes. ...
  73. Collects performance data from local or remote computers based on preconfigured schedule parameters, then writes the data ...
  74. Collects, stores, and reports unexpected application crashes to Microsoft. If this service is stopped, then Error Reporting ...
  75. COM cannot locate a provider referenced in the schema. This error may be caused by any of the following: The provider is ...
日本語
Japanese English
English (United States)