UI Translation

Windows 7

  1. The CIM_ToDirectorySpecification association identifies the target directory for the file action. When this association is ...
  2. The CIM_USBController antecedent reference represents the Universal Serial Bus (USB) controller associated with this device. ...
  3. The CIM_VersionCompatibilityCheck class specifies whether it is permissible to create the next state of a software element. ...
  4. The CIM_VideoSetting class associates the CIM_VideoControllerResolution setting object with the controller to which it applies. ...
  5. The class ID of the proxy stub DLL for the interface is not available, or failed to load the proxy stub DLL, or failed to ...
  6. The ClassGuid property contains the Globally Unique Identifier (GUID) that uniquely identifies this Plug and Play device. ...
  7. The clean up operation was successfully initiated, but did not complete within the specified time. It is still running and ...
  8. The CliConnection class defines parameters to be used with the owning alias when establishing the connection to the namespace ...
  9. The Client Access License (CAL) limit was reached. This server is unable to serve more clients. This may lead to messaging ...
  10. The Client Access Point is not yet available. This may be due to network propagation delays, please try Refresh after a few ...
  11. The client at %1 has sent an invalid response. The client cannot be removed from quarantine. You might want to enable logging ...
  12. The client can't connect because it doesn't support FIPS encryption level. Please lower the server side required security ...
  13. The client cannot connect to the destination specified in the request. Verify that the service on the destination is running ...
  14. The client certificate does not contain a valid UPN, or does not match the client name in the logon request. Please contact ...
  15. The client certificate exceeded the maximum size allowed by the WinRM service. User Action Please use a different client ...
  16. The client certificate for the user %1\%2 is not valid, and resulted in a failed smartcard logon. Please contact the user ...
  17. The client certificate that is associated with your scan servers has been uninstalled or has expired. If you want to select ...
  18. The client completed the protocol stream without negotiating all registered framing upgrades. Expected server framing upgrade ...
  19. The client configuration file enables users to automatically configure RemoteApp and Desktop Connection (RAD Connection) ...
  20. The client could not be authenticated because the Extensible Authentication Protocol (EAP) Type cannot be processed by the ...
  21. The client could not establish a connection to the remote computer. The most likely causes for this error are: 1) Remote ...
  22. The client credentials are valid, but claims could not be produced because a Lightweight Directory Access Protocol (LDAP) ...
  23. The client credentials are valid, but claims could not be produced because a Lightweight Directory Access Protocol (LDAP) ...
  24. The client credentials are valid, but claims could not be produced because the user is from a Windows NT 4.0 domain. %18 ...
  25. The client credentials are valid, but one or more claims could not be produced. The syntax of a Lightweight Directory Access ...
  26. The client credentials are valid, but one or more claims could not be produced. The syntax of a Lightweight Directory Access ...
  27. The client credentials could not be verified because multiple Lightweight Directory Access Protocol (LDAP) objects were found ...
  28. The client credentials could not be verified because multiple Lightweight Directory Access Protocol (LDAP) objects were found ...
  29. The client credentials could not be verified because of a Lightweight Directory Access Protocol (LDAP) connection error. ...
  30. The client credentials could not be verified because of a Lightweight Directory Access Protocol (LDAP) connection error. ...
  31. The client credentials could not be verified because of a Lightweight Directory Access Protocol (LDAP) error. Account store ...
  32. The client credentials could not be verified because of a Lightweight Directory Access Protocol (LDAP) error. The error string ...
  33. The client credentials could not be verified because searching is not supported for this Lightweight Directory Access Protocol ...
  34. The client credentials could not be verified because searching is not supported for this Lightweight Directory Access Protocol ...
  35. The client credentials could not be verified because the Lightweight Directory Access Protocol (LDAP) distinguished name ...
  36. The client credentials could not be verified because the Lightweight Directory Access Protocol (LDAP) distinguished name ...
  37. The client credentials could not be verified because the user's Lightweight Directory Access Protocol (LDAP) object could ...
  38. The client credentials could not be verified because the user's Lightweight Directory Access Protocol (LDAP) object could ...
  39. The client credentials were verified by Active Directory Domain Services, but claims could not be produced because the user's ...
  40. The client credentials were verified by Active Directory Domain Services, but claims could not be produced because the user's ...
  41. The client credentials were verified with Active Directory Domain Services, but an error was encountered when extracting ...
  42. The client credentials were verified with Active Directory Domain Services, but an error was encountered when extracting ...
  43. The client did not receive a response for close operation in the specified time interval. This might happen when a command ...
  44. The client did not receive a response for signal operation in the specified time interval. This might happen when a command ...
  45. The client does not belong to the same Message Queuing enterprise. This error can occur only in a mixed-mode environment. ...
  46. The client has failed to validate the Domain Controller certificate for %2. The following error was returned from the certificate ...
  47. The Client IP Address condition specifies the IP address of the RADIUS client that forwarded the connection request to NPS. ...
  48. The Client IPv6 Address condition specifies the IPv6 address of the RADIUS client that forwarded the connection request to ...
  49. The client made an unexpected and illegal sequence of calls, such as calling EndEnumeration before calling BeginEnumeration. ...
  50. The Client page cannot be displayed. Message Queuing may not be properly installed. Please reinstall Message Queuing using ...
  51. The client presented a certificate that could not be mapped to an Active Directory Domain Services user account. Error code: ...
  52. The client presented a valid inbound token as evidence. Depending on the audit policy, further details of this token may ...
  53. The client presented a valid inbound token as evidence. Depending on the audit policy, further details of this token may ...
  54. The client presented a valid inbound token as evidence. Token ID: %4 Issuer: %5 Audience: %6 Effective time: %7 %8 Expiration ...
  55. The client presented a valid logon accelerator token as evidence, but the logon accelerator token applied to a different ...
  56. The client presented a valid logon accelerator token as evidence, but the logon accelerator token applied to a different ...
  57. The client presented a valid logon accelerator token as evidence, but the logon accelerator token applied to a different ...
  58. The client presented a valid logon accelerator token as evidence, but the logon accelerator token applied to a different ...
  59. The client presented a valid logon accelerator token as evidence. Depending on the audit policy, further details of this ...
  60. The client presented a valid logon accelerator token as evidence. Depending on the audit policy, further details of this ...
  61. The client presented a valid XML token, and a Windows NT token was created successfully. Token ID: %4 Issuer: %5 Identity: ...
  62. The client presented a valid XML token, but a Windows NT token could not be produced because the token contains neither a ...
  63. The client presented a valid XML token, but a Windows NT token could not be produced because the token contains neither user ...
  64. The client presented a valid XML token, but an error occurred during the attempt to generate a Windows NT token from the ...
  65. The client presented a valid XML token, but an error occurred during the attempt to generate a Windows NT token from the ...
  66. The client presented a valid XML token, but an error occurred during the attempt to generate a Windows NT token from the ...
  67. The client presented a valid XML token, but an error occurred when generating a Windows NT token from the Active Direcotry ...
  68. The client presented an invalid inbound token as evidence. Ensure that a verification certificate corresponding to the token-signing ...
  69. The client presented an invalid inbound token as evidence. The token contained Active Directory Domain Services security ...
  70. The client presented an invalid inbound token as evidence. The token contained invalid Active Directory Domain Services security ...
  71. The client presented an invalid inbound token as evidence. The token contained invalid XML or did not conform to a supported ...
  72. The client presented an invalid inbound token as evidence. The token included a Kerberos AP-Request that was originated by ...
  73. The client presented an invalid inbound token as evidence. The token included a Kerberos AP-Request that was rejected by ...
  74. The client presented an invalid inbound token as evidence. The token included a valid Kerberos AP-Request from a trusted ...
  75. The client presented an invalid inbound token as evidence. The token referenced a trusted X509 certificate with a valid certificate ...
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)