Windows Server 2008

  1. The terminal server discovered the following license servers. To view details about a specific license server, click the ...
  2. The Terminal Server has failed to create a new self signed certificate to be used for Terminal Server authentication on SSL ...
  3. The Terminal Server has failed to replace the expired self signed certificate used for Terminal Server authentication on ...
  4. The Terminal Server is configured to use a certificate but is unable to access the private key associated with this certificate. ...
  5. The Terminal Server is configured to use a certificate that does not contain an Enhanced Key Usage attribute of Server Authentication. ...
  6. The Terminal Server is configured to use a certificate that is expired. %1 The SHA1 hash of the certificate is in the event ...
  7. The Terminal Server is configured to use a certificate that will expire in %2 days. %1 The SHA1 hash of the certificate is ...
  8. The terminal server is configured to use a template-based certificate for Transport Layer Security (TLS) 1.0\Secure Sockets ...
  9. The Terminal Server is configured to use SSL with user selected certificate, however, no usable certificate was found on ...
  10. The Terminal Server listener %1 is configured with inconsistent authentication and encryption settings. The Encryption Level ...
  11. The terminal server load-balancing Jet remote procedure call (RPC) interface (Tssdjet) call to the TSSDRpcServerOffline function ...
  12. The Terminal Services ActiveX Client control is not available. Before you can access remote programs and connect to remote ...
  13. The Terminal Services ActiveX Client control is not available. You must install this ActiveX control before you can access ...
  14. The Terminal Services ActiveX Client control is not enabled. You must enable this ActiveX control before you can access RemoteApp ...
  15. The Terminal Services client access license (TS CAL) issued to "%1" could not be revoked because the revocation limit for ...
  16. The Terminal Services Configuration tool is running with local account credentials. Licensing Diagnosis will not be able ...
  17. The Terminal Services connection authorization policies (TS CAPs) cannot be read. This problem might be due to a corrupted ...
  18. The Terminal Services connection authorization policy (TS CAP) could not be created. To resolve this issue, use TS Gateway ...
  19. The Terminal Services Gateway server administrator has ended the connection. Try reconnecting later or contact your network ...
  20. The Terminal Services Gateway server has ended the connection. Try reconnecting later or contact your network administrator ...
  21. The Terminal Services Gateway service cannot determine the version of Windows that this computer is running. Therefore, users ...
  22. The Terminal Services Gateway service does not have sufficient permissions to access the Secure Sockets Layer (SSL) certificate ...
  23. The Terminal Services Gateway service requires a valid Secure Sockets Layer (SSL) certificate to accept connections. Ensure ...
  24. The Terminal Services license server "%1" does not have a sufficient number of permanent Terminal Services client access ...
  25. The Terminal Services license server "%1" does not have any remaining permanent Terminal Services client access licenses ...
  26. The Terminal Services license server "%1" does not have any Terminal Services client access licenses (TS CALs) installed ...
  27. The Terminal Services license server "%1" has not been activated and therefore will only issue temporary licenses. To issue ...
  28. The Terminal Services license server cannot be published in Active Directory Domain Services (AD DS) because AD DS cannot ...
  29. The Terminal Services license server cannot be published in Active Directory Domain Services because access is denied. Enterprise ...
  30. The Terminal Services license server cannot communicate with another Terminal Services license server because of the following ...
  31. The Terminal Services license server cannot detect locally installed Terminal Services client access licenses (TS CALs) or ...
  32. The Terminal Services license server cannot issue a Terminal Services client access license (TS CAL) to the client because ...
  33. The Terminal Services license server cannot update the license attributes for user "%1!s!" in the Active Directory Domain ...
  34. The Terminal Services license server could not be published in Active Directory Domain Services during the installation of ...
  35. The Terminal Services license server could not be unpublished from Active Directory Domain Services. Additionally, the TS ...
  36. The Terminal Services license server could not return an expired Terminal Services client access license (TS CAL) to the ...
  37. The Terminal Services license server failed to query Active Directory Domain Services for user information. Win32 error code: ...
  38. The Terminal Services license server was successfully published in Active Directory Domain Services during the installation ...
  39. The Terminal Services licensing mode determines the type of Terminal Services client access licenses (TS CALs) that a license ...
  40. The Terminal Services Licensing service cannot start. The following error occurred: %1!s! To resolve this issue, ensure that ...
  41. The Terminal Services resource authorization policies (TS RAPs) cannot be read. This problem might be due to a corrupted ...
  42. The Terminal Services resource authorization policy (TS RAP) could not be created. To resolve this issue, use TS Gateway ...
  43. The Terminal Services Session Broker service could not start because it was unable to create a directory that it needs to ...
  44. The Terminal Services Session Broker service could not start because of a problem creating a security descriptor. The system ...
  45. The Terminal Services Session Broker service failed to start because of a problem obtaining the default principal name from ...
  46. The Terminal Services Session Broker service failed to start because of a problem with remote procedure call (RPC) listen. ...
  47. The Terminal Services Session Broker service failed to start due to a problem registering an RPC endpoint. The error code ...
  48. The Terminal Services Session Broker service failed to start due to a problem registering RPC authentication information. ...
  49. The Terminal Services Session Broker service failed to start due to a problem with retrieving RPC binding handles. The error ...
  50. The Terminal Services Session Broker service failed to start due to a problem with RPC interface handle registration. The ...
  51. The Terminal Services Session Broker service failed to start due to a problem with specifying the RPC protocol sequence. ...
  52. The Terminal Services User Home Directory was not set because the path specified does not exist or not accessible. The default ...
  53. The Terminal Services Web Access (TS Web Access) Web site enables you to access remote programs or remote desktops that are ...
  54. The Terminate method terminates a process and all of its threads. The method returns an integer value that can be interpretted ...
  55. The Terms of Service or Privacy Statement for the Guide have changed. Review the new terms before proceeding. See the Web ...
  56. The test email has been sent to the Notification subsystem. Please verify that the email arrives at the intended mailbox. ...
  57. The text for the Voice property of a command is either missing a right parenthesis or includes a misplaced left parenthesis. ...
  58. The text for the Voice property of a command is missing a left parenthesis, includes a misplaced right parenthesis, or has ...
  59. The text for the Voice property of a command is missing a left square bracket, includes a misplaced right square bracket, ...
  60. The text for the Voice property of a command is missing a right square bracket or includes a misplaced left square bracket. ...
  61. The text for the Voice property of a command is missing surrounding parentheses or square brackets for specifying alternative ...
  62. The text is available to paste into a destination program, including Journal. Your original handwriting remains in Journal. ...
  63. The theme could not load because one of the needed theme files could not be found. This can happen with themes that are not ...
  64. The thesaurus file %2 for lcid %3 has invalid format. Please edit the file and correct it. Use retail tracing for detailed ...
  65. The Thread Details performance object consists of counters that measure aspects of thread behavior that are difficult or ...
  66. The Thread performance object consists of counters that measure aspects of thread behavior. A thread is the basic object ...
  67. The ThreadCount property specifies the number of active threads in this process. An instruction is the basic unit of execution ...
  68. The threading model of the component specified in the registry is inconsistent with the registration database. The faulty ...
  69. The ThreadingModel property specifies the threading model used by in-process COM classes, including: Apartment - components ...
  70. The ThreadingModel property, if applicable, defines the server threading model, can take one of the following values: 0 - ...
  71. The ThreadingModel value found in the registry has been modified outside of the COM+ environment. You will need to reinstall ...
  72. The ThreadState property indicates the current execution state for the thread. A thread can have one of eight values: Initialized ...
  73. The ThreadWaitReason property indicates why the thread is waiting. The value is only valid if the ThreadState member is set ...
  74. The time at the Primary Domain Controller is different than the time at the Backup Domain Controller or member server by ...
  75. The time between the earliest moment when a record timestamp can be refreshed and the earliest moment when the record can ...