UI Translation

Windows 8.1

  1. Failover Cluster Manager detected that the specified security descriptor for '%1' did not grant the required full access ...
  2. Failover Cluster Manager detected that virtual machine '%1' is configured to use disk '%2' which is not a valid shared disk ...
  3. Failover Cluster Manager detected that virtual machine '%1' is configured to use one or more disk that are not yet added ...
  4. Failover Cluster Manager encountered an error while changing the auto start settings for the selected groups. The error was ...
  5. Failover Cluster Manager encountered an error while deleting the selected groups. The error was '%1'. For more information ...
  6. Failover Cluster Manager encountered an error while moving the selected groups. The error was '%1'. For more information ...
  7. Failover Cluster Manager encountered an error while offlining the selected groups. The error was '%1'. For more information ...
  8. Failover Cluster Manager encountered an error while onlining the selected groups. The error was '%1'. For more information ...
  9. Failover Cluster Manager failed while managing one or more cluster. The error was '%1'. For more information see the Failover ...
  10. Failover Cluster Manager remembers previous clusters to which it has been connected. To clear this setting click the 'Clear ...
  11. Failover Cluster Manager remembers your choices to not show specific dialogs and wizard pages. To reset this setting click ...
  12. Failover Cluster WMI Provider could not determine the state of cluster node '%1'. For more information see the Failover Clustering ...
  13. Failover Cluster WMI Provider could not find cluster node '%1'. Some properties may be skipped. Please make sure that the ...
  14. Failover Cluster WMI Provider could not retrieve the partition information for Cluster Shared Volume '%1' because it was ...
  15. Failover Cluster WMI Provider detected an invalid character. The private property name '%1' had an invalid character and ...
  16. Failover Cluster WMI Provider detected an invalid character. The private property name '%1' had an invalid character but ...
  17. Failover Cluster WMI Provider detected an invalid character. The private property name '%1' had an invalid character but ...
  18. Failover Cluster WMI Provider encountered property '%1' which does not exist in the schema of class '%2'. A common cause ...
  19. Failover Cluster WMI Provider found multiple virtual machines with the same name '%1'. This ambiguous operation is not supported. ...
  20. Failover Clustering allows multiple servers to work together to provide high availability of server roles. Failover Clustering ...
  21. Failover Clustering allows multiple servers to work together to provide high availability of services and applications. Failover ...
  22. Failover Clustering Tools include the Failover Cluster Manager snap-in, the Cluster-Aware Updating interface, and the Failover ...
  23. Failover completed with multiple warnings for the virtual machine '%1' during failover. Check Administrator events in the ...
  24. Failover completed with warnings: Failed to apply the network setting data for the virtual machine '%1' during failover. ...
  25. Failover completed with warnings: Failed to revert the VSS snapshot for the virtual machine '%1' during failover. Check Administrator ...
  26. Failover protocol message BINDING-ACK from server %1 for failover relationship %2 is rejected because message digest was ...
  27. Failover protocol message BINDING-ACK from server %1 for failover relationship %2 was rejected because message digest failed ...
  28. Failover protocol message BINDING-ACK from server %1 for failover relationship %2 was rejected because message digest was ...
  29. Failover protocol message BINDING-ACK from server {0} for failover relationship {1} is rejected because message digest was ...
  30. Failover protocol message BINDING-ACK from server {0} for failover relationship {1} was rejected because message digest failed ...
  31. Failover protocol message BINDING-ACK from server {0} for failover relationship {1} was rejected because message digest was ...
  32. Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 is rejected because message digest was ...
  33. Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 was rejected because message digest ...
  34. Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 was rejected because message digest ...
  35. Failover protocol message BINDING-UPDATE from server {0} for failover relationship {1} is rejected because message digest ...
  36. Failover protocol message BINDING-UPDATE from server {0} for failover relationship {1} was rejected because message digest ...
  37. Failover protocol message BINDING-UPDATE from server {0} for failover relationship {1} was rejected because message digest ...
  38. Failover protocol message CONNECT from server %1 for failover relationship %2 is rejected because message digest was not ...
  39. Failover protocol message CONNECT from server %1 for failover relationship %2 was rejected because message digest failed ...
  40. Failover protocol message CONNECT from server %1 for failover relationship %2 was rejected because message digest was not ...
  41. Failover protocol message CONNECT from server {0} for failover relationship {1} is rejected because message digest was not ...
  42. Failover protocol message CONNECT from server {0} for failover relationship {1} was rejected because message digest failed ...
  43. Failover protocol message CONNECT from server {0} for failover relationship {1} was rejected because message digest was not ...
  44. Failover protocol message CONNECTACK from server %1 for failover relationship %2 is rejected because message digest was not ...
  45. Failover protocol message CONNECTACK from server %1 for failover relationship %2 was rejected because message digest failed ...
  46. Failover protocol message CONNECTACK from server %1 for failover relationship %2 was rejected because message digest was ...
  47. Failover protocol message CONNECTACK from server {0} for failover relationship {1} is rejected because message digest was ...
  48. Failover protocol message CONNECTACK from server {0} for failover relationship {1} was rejected because message digest failed ...
  49. Failover protocol message CONNECTACK from server {0} for failover relationship {1} was rejected because message digest was ...
  50. Failover protocol message CONTACT from server %1 for failover relationship %2 is rejected because message digest was not ...
  51. Failover protocol message CONTACT from server %1 for failover relationship %2 was rejected because message digest failed ...
  52. Failover protocol message CONTACT from server %1 for failover relationship %2 was rejected because message digest was not ...
  53. Failover protocol message CONTACT from server {0} for failover relationship {1} is rejected because message digest was not ...
  54. Failover protocol message CONTACT from server {0} for failover relationship {1} was rejected because message digest failed ...
  55. Failover protocol message CONTACT from server {0} for failover relationship {1} was rejected because message digest was not ...
  56. Failover protocol message STATE from server %1 for failover relationship %2 is rejected because message digest was not present. ...
  57. Failover protocol message STATE from server %1 for failover relationship %2 was rejected because message digest failed to ...
  58. Failover protocol message STATE from server %1 for failover relationship %2 was rejected because message digest was not configured. ...
  59. Failover protocol message STATE from server {0} for failover relationship {1} is rejected because message digest was not ...
  60. Failover protocol message STATE from server {0} for failover relationship {1} was rejected because message digest failed ...
  61. Failover protocol message STATE from server {0} for failover relationship {1} was rejected because message digest was not ...
  62. Failover protocol message UPDDONE from server %1 for failover relationship %2 is rejected because message digest was not ...
  63. Failover protocol message UPDDONE from server %1 for failover relationship %2 was rejected because message digest failed ...
  64. Failover protocol message UPDDONE from server %1 for failover relationship %2 was rejected because message digest was not ...
  65. Failover protocol message UPDDONE from server {0} for failover relationship {1} is rejected because message digest was not ...
  66. Failover protocol message UPDDONE from server {0} for failover relationship {1} was rejected because message digest failed ...
  67. Failover protocol message UPDDONE from server {0} for failover relationship {1} was rejected because message digest was not ...
  68. Failover protocol message UPDREQ from server %1 for failover relationship %2 is rejected because message digest was not present. ...
  69. Failover protocol message UPDREQ from server %1 for failover relationship %2 was rejected because message digest failed to ...
  70. Failover protocol message UPDREQ from server %1 for failover relationship %2 was rejected because message digest was not ...
  71. Failover protocol message UPDREQ from server {0} for failover relationship {1} is rejected because message digest was not ...
  72. Failover protocol message UPDREQ from server {0} for failover relationship {1} was rejected because message digest failed ...
  73. Failover protocol message UPDREQ from server {0} for failover relationship {1} was rejected because message digest was not ...
  74. Failover protocol message UPDREQALL from server %1 for failover relationship %2 is rejected because message digest was not ...
  75. Failover protocol message UPDREQALL from server %1 for failover relationship %2 was rejected because message digest failed ...
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)