UI Translation

Windows 7

  1. Failover Cluster Manager could not load clusapi.dll. This is required for any monitoring and management of local or remote ...
  2. Failover Cluster Manager could not load the DFS management assembly. This will prevent the Configure File Share Witness wizard ...
  3. Failover Cluster Manager could not make virtual machine '%1' highly available. Please refer to the cluster reports in the ...
  4. Failover Cluster Manager could not move the group '%1' to node '%2'. The error was '%3'. For more information see the Failover ...
  5. Failover Cluster Manager could not offline the group '%1'. The error was '%2'. For more information see the Failover Cluster ...
  6. Failover Cluster Manager could not open a handle to the cluster or a cluster item because the client does not support such ...
  7. Failover Cluster Manager could not retrieve properties for cluster resource type '%1'. Please make sure the resource type ...
  8. Failover Cluster Manager could not shut down cluster '%1'. For more information see the Failover Cluster Manager Diagnostic ...
  9. Failover Cluster Manager detected that the specified security descriptor for '%1' did not grant the required full access ...
  10. Failover Cluster Manager detected that virtual machine '%1' is configured to use disk '%2' which is not a valid shared disk ...
  11. Failover Cluster Manager detected that virtual machine '%1' is configured to use one or more disk that are not yet added ...
  12. Failover Cluster Manager encountered an error while changing the auto start settings for the selected groups. The error was ...
  13. Failover Cluster Manager encountered an error while deleting the selected groups. The error was '%1'. For more information ...
  14. Failover Cluster Manager encountered an error while moving the selected groups. The error was '%1'. For more information ...
  15. Failover Cluster Manager encountered an error while offlining the selected groups. The error was '%1'. For more information ...
  16. Failover Cluster Manager encountered an error while onlining the selected groups. The error was '%1'. For more information ...
  17. Failover Cluster Manager failed while managing one or more cluster. For more information see the Failover Cluster Manager ...
  18. Failover Cluster Manager failed while managing one or more cluster. The error was '%1'. For more information see the Failover ...
  19. Failover Cluster Manager remembers previous clusters to which it has been connected. To clear this setting click the 'Clear ...
  20. Failover Cluster Manager remembers your choices to not show specific dialogs and wizard pages. To reset this setting click ...
  21. Failover Cluster WMI Provider could not close one or more event handle. For more information see the Failover Clustering ...
  22. Failover Cluster WMI Provider could not close the cluster notification port. For more information see the Failover Clustering ...
  23. Failover Cluster WMI Provider could not close the handle to the cluster enumeration. For more information see the Failover ...
  24. Failover Cluster WMI Provider could not close the handle to the cluster group enumeration. For more information see the Failover ...
  25. Failover Cluster WMI Provider could not close the handle to the cluster group. For more information see the Failover Clustering ...
  26. Failover Cluster WMI Provider could not close the handle to the cluster network interface. For more information see the Failover ...
  27. Failover Cluster WMI Provider could not close the handle to the cluster network. For more information see the Failover Clustering ...
  28. Failover Cluster WMI Provider could not close the handle to the cluster node. For more information see the Failover Clustering ...
  29. Failover Cluster WMI Provider could not close the handle to the cluster resource enumeration. For more information see the ...
  30. Failover Cluster WMI Provider could not close the handle to the cluster resource. For more information see the Failover Clustering ...
  31. Failover Cluster WMI Provider could not close the handle to the cluster. For more information see the Failover Clustering ...
  32. Failover Cluster WMI Provider could not create one or more event handle. For more information see the Failover Clustering ...
  33. Failover Cluster WMI Provider could not create the thread context. For more information see the Failover Clustering WMI Diagnostic ...
  34. Failover Cluster WMI Provider could not determine if resource '%1' is a Cluster Shared Volume. The error code was '%2'. For ...
  35. Failover Cluster WMI Provider could not determine the state of cluster node '%1'. For more information see the Failover Clustering ...
  36. Failover Cluster WMI Provider could not execute the control code '%1' through MSCluster_Node.ExecuteNodeControl. Please confirm ...
  37. Failover Cluster WMI Provider could not execute the control code '%1' through MSCluster_Resource.ExecuteResourceControl. ...
  38. Failover Cluster WMI Provider could not find cluster node '%1'. Some properties may be skipped. Please make sure that the ...
  39. Failover Cluster WMI Provider could not find the current COM calling context. For more information see the Failover Clustering ...
  40. Failover Cluster WMI Provider could not initialize COM. For more information see the Failover Clustering WMI Diagnostic channel. ...
  41. Failover Cluster WMI Provider could not process a cluster event. For more information see the Failover Clustering WMI Diagnostic ...
  42. Failover Cluster WMI Provider could not reset a cluster event. For more information see the Failover Clustering WMI Diagnostic ...
  43. Failover Cluster WMI Provider could not retrieve the partition information for Cluster Shared Volume '%1' because it was ...
  44. Failover Cluster WMI Provider could not signal a cluster event. For more information see the Failover Clustering WMI Diagnostic ...
  45. Failover Cluster WMI Provider could not signal an event for cluster object '%1'. Any process waiting for this event will ...
  46. Failover Cluster WMI Provider could not start one or more thread. For more information see the Failover Clustering WMI Diagnostic ...
  47. Failover Cluster WMI Provider could not switch the COM calling context for cluster object '%1'. For more information see ...
  48. Failover Cluster WMI Provider detected an invalid character. The private property name '%1' had an invalid character and ...
  49. Failover Cluster WMI Provider detected an invalid character. The private property name '%1' had an invalid character and ...
  50. Failover Cluster WMI Provider detected an invalid character. The private property name '%1' had an invalid character but ...
  51. Failover Cluster WMI Provider detected an invalid character. The private property name '%1' had an invalid character but ...
  52. Failover Cluster WMI Provider failed to process cluster object '%1'. For more information see the Failover Clustering WMI ...
  53. Failover Cluster WMI Provider failed while waiting for a request to be processed. For more information see the Failover Clustering ...
  54. Failover Cluster WMI Provider timed out while waiting for a request to be processed. For more information see the Failover ...
  55. Failover Clustering allows multiple servers to work together to provide high availability of services and applications. Failover ...
  56. Failover Clustering allows multiple servers to work together to provide high availability of services and applications. Failover ...
  57. Failure HCAP Response was returned with result code %1 HCAP client host name: %2 HCAP client IP address: %3 Request ID: %4 ...
  58. Failure in binding to default Active Directory Domain Services server on localhost. %rMake sure user has credentials to access ...
  59. Failure reading password sync configuration. %rApply configuration changes again and if the problem persists, contact your ...
  60. Failure to connect to the FTP service on the internet server. Make sure that FTP service is running properly on the server ...
  61. Failure to execute the HTTP request to start internet synchronizer on the internet server. Use Replication Manager to configure ...
  62. Failure to execute the HTTP request to start the internet synchronizer on the internet server. Use Replication Manager to ...
  63. Failures Adapter is the number of connections that were dropped due to an adapter failure. This number is an accumulator ...
  64. Failures have occurred during migration of MTS packages and program settings to COM+ applications and program settings. See ...
  65. Failures Link is the number of connections that were dropped due to a link failure. This number is an accumulator and shows ...
  66. Failures No Listen is the number of connections that were rejected because the remote computer was not listening for connection ...
  67. Failures Not Found is the number of connection attempts that failed because the remote computer could not be found. This ...
  68. Failures Resource Local is the number of connections that failed because of resource problems or shortages on the local computer. ...
  69. Failures Resource Remote is the number of connections that failed because of resource problems or shortages on the remote ...
  70. Fair Share CPU Scheduling dynamically distributes processor time across all Remote Desktop Services sessions on the same ...
  71. Fall back to local name resolution if the name does not exist in DNS or the DNS servers are unreachable when the client computer ...
  72. Fast Read Not Possibles/sec is the frequency of attempts by an Application Program Interface (API) function call to bypass ...
  73. Fast Read Resource Misses/sec is the frequency of cache misses necessitated by the lack of available resources to satisfy ...
  74. Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the ...
  75. FastPurple installs drivers that are incompatible with this 64bit version of Windows. Installing this application may cause ...
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)