Windows Server 2008

  1. The client presented an invalid inbound token as evidence. The token contained Active Directory Domain Services security ...
  2. The client presented an invalid inbound token as evidence. The token contained invalid Active Directory Domain Services security ...
  3. The client presented an invalid inbound token as evidence. The token contained invalid XML or did not conform to a supported ...
  4. The client presented an invalid inbound token as evidence. The token included a Kerberos AP-Request that was originated by ...
  5. The client presented an invalid inbound token as evidence. The token included a Kerberos AP-Request that was rejected by ...
  6. The client presented an invalid inbound token as evidence. The token included a valid Kerberos AP-Request from a trusted ...
  7. The client presented an invalid inbound token as evidence. The token referenced a trusted X509 certificate with a valid certificate ...
  8. The client presented an invalid inbound token as evidence. The token referenced an unknown X509 Subject Key Identifier (SKI). ...
  9. The client presented an invalid inbound token as evidence. The token referenced an X509 certificate that is not trusted by ...
  10. The client presented an invalid inbound token as evidence. The token referenced an X509 certificate that is not trusted by ...
  11. The client presented an invalid inbound token as evidence. The token referenced an X509 certificate whose certificate chain ...
  12. The client presented an invalid logon accelerator token as evidence. The token contained invalid XML or did not conform to ...
  13. The client presented an invalid logon accelerator token as evidence. The token included a Kerberos AP-Request that was originated ...
  14. The client presented an invalid logon accelerator token as evidence. The token included a Kerberos AP-Request that was rejected ...
  15. The client presented an invalid logon accelerator token as evidence. The token included a valid Kerberos AP-Request from ...
  16. The client presented an invalid logon accelerator token as evidence. The token referenced a trusted X509 certificate with ...
  17. The client presented an invalid logon accelerator token as evidence. The token referenced an unknown X509 Subject Key Identifier ...
  18. The client presented an invalid logon accelerator token as evidence. The token referenced an X509 certificate that is not ...
  19. The client presented an invalid logon accelerator token as evidence. The token referenced an X509 certificate whose certificate ...
  20. The client presented credentials, but they could not be verified because no account store returned an authoritative result. ...
  21. The client presented credentials, but they could not be verified because no account store returned an authoritative result. ...
  22. The client presented valid credentials. Depending on the audit policy, the list of generated claims may be written to a 10550 ...
  23. The client presented valid credentials. Depending on the audit policy, the list of generated claims may be written to a 550 ...
  24. The client specified username and password in the request to the destination computer. But the destination computer requested ...
  25. The client width you have entered is invalid. The client width must be a multiple of 4 pixels. Please enter another client ...
  26. The client-side extension could not %1 %2 preference items for the '%3' Group Policy object because Windows is shutting down ...
  27. The ClientAccessible property is indicates whether the shadow copy was created by the Windows Previous Versions component. ...
  28. The ClientCredentialInfo static method CreateCertificateCredential was called in a context where no client certificate was ...
  29. The ClientSiteName property indicates the name of the site where the domain controller is configured to be in. This value ...
  30. The clock difference between the home server %1 and target server %2 is greater than one minute. This may cause Kerberos ...
  31. The clock on your computer has been changed. Viewing of this content is not allowed if the clock has been changed since it ...
  32. The CLSID %1, item %2 and title %3 has the named value AppID, but is not recorded under \HKEY_CLASSES_ROOT\AppId. Do you ...
  33. The Clsid property, if applicable, defines the COM CLSID associated with server implementation. Note: decoupled providers ...
  34. The Clsid property, if applicable, defines the COM CLSID associated with server implementation. Note: decoupled providers ...
  35. The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class. ...
  36. The cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource. ...
  37. The cluster database could not be loaded due to error '%1' on node '%2'. The file may be missing or corrupt. Automatic repair ...
  38. The cluster does not use shared storage. A cluster must use a hardware solution based either on shared storage or on replication ...
  39. The cluster has an even number of nodes. Consider changing to the Node and Disk Majority quorum configuration to improve ...
  40. The cluster has an odd number of nodes and a quorum disk. A quorum disk in this scenario reduces cluster high availability. ...
  41. The cluster IP address and dedicated IP address cannot be identical. Type a different cluster IP and dedicated IP addresses. ...
  42. The cluster IP addresses are shared by every member of the cluster for load balancing. The first IP address listed is considered ...
  43. The cluster management item is no longer available. A possible cause is that the connection to the cluster is no longer available. ...
  44. The cluster network address is not valid. The address must be of the form xx-xx-xx-xx-xx-xx or xx:xx:xx:xx:xx:xx. Type valid ...
  45. The cluster network is not valid for an IPv6 Tunnel resource. Check the configuration of the IP Address resource on which ...
  46. The cluster network is the only one configured for internal cluster communication between two or more active cluster nodes. ...
  47. The cluster node '{0}' was evicted from the cluster, but was not fully cleaned up. Please see the Failover Clustering application ...
  48. The cluster node was evicted from the cluster successfully, but the node was not cleaned up. To determine what cleanup steps ...
  49. The cluster or computer you specified could not be found. Please make sure the cluster or computer is accessible and that ...
  50. The cluster resource host subsystem (RHS) stopped unexpectedly. An attempt will be made to restart it. This is usually due ...
  51. The Cluster service cannot identify node '%1' as a member of failover cluster '%2'. If the computer name for this node was ...
  52. The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node ...
  53. The cluster service detected that the witness disk designation has changed - usually indicating that the current node has ...
  54. The Cluster service failed to bring clustered service or application '%1' completely online or offline. One or more resources ...
  55. The cluster service failed to properly cleanup a clustered disk with ID '%2' while destroying the cluster. The error code ...
  56. The Cluster service failed to start because it was unable to register interface(s) with the RPC service. The error code was ...
  57. The cluster service failed to start. This was because the failover cluster virtual adapter failed to initialize the miniport ...
  58. The Cluster service failed to update the cluster database (error code '%1'). Possible causes are insufficient disk space ...
  59. The cluster service has determined that this node does not have the latest copy of cluster configuration data. Therefore, ...
  60. The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between ...
  61. The Cluster Service was unable to access network adapter '%1'. Verify that other network adapters are functioning properly ...
  62. The cluster subnet mask is required. Network Load Balancing has automatically generated a subnet mask. If you do not want ...
  63. The cluster that this computer is joining uses a different cryptographic provider (CSP) than the one specified. Install Active ...
  64. The cluster to which you are trying to join this server is not currently provisioned as either a root or licensing-only cluster. ...
  65. The cluster URL is either empty or mal-formatted. It must in the form of http(s)://domain/_wmcs/licensing or http(s)://domain/_wmcs/certification. ...
  66. The cluster URL specified in the Active Directory Rights Management Services (AD RMS) installation did not respond to an ...
  67. The cluster you are trying to join is not currently provisioned as either a Certification server or Licensing server. The ...
  68. The CNG key isolation service is hosted in the LSA process. The service provides key process isolation to private keys and ...
  69. The code describing why the Gatherer service went into back off state. 0 - up and running 1 - high system IO traffic 2 - ...
  70. The code set {0} matches but is not your current configuration ({1}). Select Update to replace your current settings with ...
  71. The CodeSet property indicates the code page value used by the operating system. A code page contains a character table used ...
  72. The Collect Procedure for the "%1!s!" service in DLL "%2!s!" generated an exception or returned an invalid status. The performance ...
  73. The collect procedure in Extensible Counter DLL "%1!s!" for the "%2!s!" service returned a buffer that was larger than the ...
  74. The CollectionOfMSEs object allows the grouping of ManagedSystemElements for the purposes of associating Settings and Configurations. ...
  75. The ColorPlanes property indicates the current number of color planes used in the video display. A color plane is another ...