termsrv.dll
Associated Error Codes
Below lists error codes and symbolic names found for this module.
| Code | Found in | Description |
|---|---|---|
| 0x10000038 | 78.11011 | Classic |
| 0x30000001 | 78.11011 | Start |
| 0x30000002 | 78.11011 | Stop |
| 0x400003f4 | 78.11011 | Remote session from client name %1 exceeded the maximum allowed failed logon attempts. The session was forcibly terminated. |
| 0x50000002 | 78.11011 | Error |
| 0x50000003 | 78.11011 | Warning |
| 0x50000004 | 78.11011 | Information |
| 0x50000005 | 78.11011 | Verbose |
| 0x90000001 | 78.11011 | Microsoft-Windows-TerminalServices-RemoteConnectionManager |
| 0x90000002 | 78.11011 | System |
| 0xb0000002 | 78.11011 | %1 |
| 0xb0000003 | 78.11011 | %1 |
| 0xb0000004 | 78.11011 | %1 |
| 0xb0000005 | 78.11011 | %1 |
| 0xb0000006 | 78.11011 | %1 |
| 0xb0000007 | 78.11011 | %1 |
| 0xb0000008 | 78.11011 | %1 |
| 0xb0000009 | 78.11011 | %1 |
| 0xb0000100 | 8.11011 | Remote Desktop Services Remote Connection Manager is starting up |
| 0xb0000101 | 8.11011 | Remote Desktop Services Remote Connection Manager has finished start up. Return code %1 |
| 0xb0000102 | 78.11011 | Listener %1 has started listening |
| 0xb0000103 | 78.11011 | Listener %1 has stopped listening |
| 0xb0000104 | 78.11011 | Listener %1 failed while listening. Error code %2 |
| 0xb0000105 | 78.11011 | Listener %1 received a connection |
| 0xb0000106 | 78.11011 | Listener %1 has been asked to stop listening |
| 0xb0000107 | 1011 | WDDM graphics mode is enabled |
| 0xb0000110 | 1011 | Connection with ID %1 has started |
| 0xb0000111 | 1011 | Connection with ID %1 for session %2 has completed, total time %3 (ms), stack time %4 (ms) |
| 0xb0000112 | 1011 | Reconnect connection ID %1 to session %2 took %3 (ms) |
| 0xb00003eb | 1011 | The remote desktop client '%1' has provided an invalid license. |
| 0xb00003ec | 1011 | The Remote Desktop Session Host server cannot issue a client license. It was unable to issue the license due to a changed (mismatched) client license, insufficient memory, or an internal error. Further details for this problem may have been reported at the client's computer. |
| 0xb00003ee | 8.11011 | The RD Session Host server received large number of incomplete connections. The system may be under attack. |
| 0xb00003f3 | 1011 | The remote session could not be established from remote desktop client %1 because its temporary license has expired. |
| 0xb000042c | 1011 | The RD Licensing mode has not been configured. |
| 0xb000042d | 1011 | The RD Licensing grace period has expired and Licensing mode for the Remote Desktop Session Host server has not been configured. Licensing mode must be configured for continuous operation. |
| 0xb0000470 | 8.11011 | RD Session Host Server role is not installed. |
| 0xb0000471 | 8.11011 | The roaming user profile cache manager for Remote Desktop Services could not start. Error Code: %1 |
| 0xb0000472 | 8.11011 | The roaming user profile cache manager for Remote Desktop Services could not start because an incorrect value was specified for the monitoring interval. Error Code: %1 |
| 0xb0000473 | 8.11011 | The roaming user profile cache manager for Remote Desktop Services could not start because an incorrect value was specified for the maximum cache size. Error Code: %1 |
| 0xb0000474 | 8.11011 | The "Limit the size of the entire roaming user profile cache" Group Policy setting has been enabled, but the roaming user profile cache manager for Remote Desktop Services has encountered a problem. Error Code: %1 |
| 0xb0000475 | 8.11011 | The "Limit the size of the entire roaming user profile cache" Group Policy setting has been disabled, but the roaming user profile cache manager for Remote Desktop Services has encountered a problem. Error Code: %1 |
| 0xb0000476 | 78.11011 | The "Limit the size of the entire roaming user profile cache" Group Policy setting has been enabled. |
| 0xb0000477 | 78.11011 | The "Limit the size of the entire roaming user profile cache" Group Policy setting has been disabled. |
| 0xb0000478 | 8.11011 | The roaming user profile cache manager for Remote Desktop Services could not delete the roaming user profile for the user %1. The roaming user profile cache might still exceed the %2 gigabyte limit. Error Code: %3 |
| 0xb0000479 | 8.11011 | The roaming user profile cache manager for Remote Desktop Services deleted the roaming user profile for the user %1 because the roaming user profile cache exceeded the %2 gigabyte limit. |
| 0xb000047a | 78.11011 | Remote Desktop Services: Remote control session initiated: %1 initiated a remote control session: User: %2 Domain: %3 |
| 0xb000047b | 78.11011 | Remote Desktop Services: Remote control session connection succeeded: %1 initiated a remote control session: User: %2 Domain: %3 |
| 0xb000047c | 78.11011 | Remote Desktop Services: Remote control session connection failed: %1 initiated a remote control session: User: %2 Domain: %3 |
| 0xb000047d | 78.11011 | Remote Desktop Services: User authentication succeeded: User: %1 Domain: %2 Source Network Address: %3 |
| 0xb000047e | 78.11011 | Remote Desktop Services: User config data have been merged: User: %1 Domain: %2 Source Network Address: %3 |
| 0xb000047f | 78.11011 | The remote user's connection was declined by the logged on user. User Account: %2 Domain: %1 Source IP Address: %3 |
| 0xb0000480 | 78.11011 | Failed to create KVP sessions string. Error Code %1 |
| 0xb0000481 | 78.11011 | Failed to write KVP sessions string. Error Code %1 |
| 0xb0000483 | 78.11011 | The Remote Connection Manager selected Kernel mode RDP protocol stack. |
| 0xb0000484 | 78.11011 | The Remote Connection Manager selected User mode RDP protocol stack. |
| 0xb0000485 | 8.11011 | The listener named %1 has modified some configuration settings. |
| 0xb0000486 | 8.11011 | Remote Desktop Services accepted a connection from IP address %1. |
| 0xb0000500 | 1011 | Remote Desktop Configuration service could not remove user %1\%2 from administrators group, error Code: %3 |
| 0xb0000501 | 1011 | Remote Desktop Configuration service could not remove user %1\%2 from Remote Desktop Users group, error Code: %3 |
| 0xb0000502 | 1011 | Remote Desktop Configuration service could not remove user with SID %1 from administrators group, error Code: %2 |
| 0xb0000503 | 1011 | Remote Desktop Configuration service could not remove user with SID %1 from Remote Desktop Users group, error Code: %2 |
| 0xb0000504 | 1011 | Remote Desktop Configuration service has added user %1\%2 to administrators group |
| 0xb0000505 | 1011 | Remote Desktop Configuration service has added user %1\%2 to Remote Desktop Users group |
| 0xb0000506 | 1011 | Remote Desktop Configuration service has removed user with SID %1 from administrators group |
| 0xb0000507 | 1011 | Remote Desktop Configuration service has removed user with SID %1 from Remote Desktop Users group |
| 0xb0000508 | 1011 | Remote Desktop Configuration service has removed user %1\%2 from administrators group |
| 0xb0000509 | 1011 | Remote Desktop Configuration service has removed user %1\%2 from Remote Desktop Users group |
| 0xb0005000 | 8.11011 | Remote Desktop Services Network Fair Share started. |
| 0xb0005001 | 8.11011 | Remote Desktop Services Network Fair Share stopped. |
| 0xb0005002 | 8.11011 | Remote Desktop Services Network Fair Share was enabled for the user account %1 with a weight of %2. |
| 0xb0005003 | 8.11011 | Remote Desktop Service Network Fairshare has been enabled for connection on session %1 with weight of %2. |
| 0xb0005004 | 8.11011 | Remote Desktop Services could not enable Network Fair Share for the user account %1. The error code is %2. |
| 0xb0005005 | 8.11011 | Remote Desktop Services could not enable Network Fair Share for the connection on session %1. The error code is %2. |
| 0xb0005006 | 8.11011 | Remote Desktop Services could not enable Network Fair Share for session %1. The error code is %2. |
| 0xb0005007 | 8.11011 | Remote Desktop Services Network Fair Share was disabled for the user account %1. |
| 0xb0005008 | 8.11011 | Remote Desktop Services Network Fair Share was disabled for the connection on session %1. |
| 0xb0005009 | 8.11011 | Remote Desktop Services could not disable Network Fair Share for the user account %1. The error code is %2. |
| 0xb000500a | 8.11011 | Remote Desktop Services could not disable Network Fair Share for the connection on session %1. The error code is %2. |
| 0xb000500b | 8.11011 | Remote Desktop Services could not disconnect a user disk for the user account with a SID of %1. The error code is %2.%3 |
| 0xb000500c | 8.11011 | Remote Desktop Services could not detach a user disk for the user account with a SID of %1. The error code is %2.%3 |
| 0xb000500d | 8.11011 | Remote Desktop Services could not apply a user desktop for a user account with a SID of %1. A temporary profile was enforced for the user. Verify that the user profile disk settings are correct. The error code is %2.%3 |
| 0xb000500e | 8.11011 | Remote Desktop Services could not obtain a user profile disk for the user account with a SID of %1. Verify that the user profile disk location is accessible, the server's computer account has read and write permissions to it, and that the location has a user profile disk template file present. The error code is %2.%3 |
| 0xb000500f | 8.11011 | Remote Desktop Services could not attach a user profile disk for a user account with a SID of %1. The error code is %2.%3 |
| 0xb0005010 | 8.11011 | Remote Desktop Services could not apply a user desktop for a user account with a SID of %1. A temporary profile could not be enforced for the user. The user will get a normal profile, and the user's state will be discarded when the user logs off. Verify that the user profile disk settings are correct. The error code is %2.%3 |
| 0xb0005011 | 8.11011 | The RD Licensing has taken too long to process the client license |
| 0xb0005012 | 8.11011 | Remote Desktop Services has taken too long to complete the client connection |
| 0xb0005013 | 8.11011 | Remote Desktop Services has taken too long to load the user configuration from server %1 for user %2 |
| 0xb0005014 | 8.11011 | Remote Desktop Services took %3 milliseconds to load the user configuration from server %1 for user %2 |
| 0xb0005015 | 8.11011 | Remote Desktop Services failed to shutdown within the time allocated |
| 0xb0005016 | 8.11011 | Remote Desktop Services failed to retrieve information about a connection for session %1 within the time allocated |
| 0xb0005017 | 8.11011 | Shadow View Session Started User %1 on computer %2 viewing user %3 (Session ID: %4) |
| 0xb0005018 | 8.11011 | Shadow View Session Stopped User %1 on computer %2 viewing user %3 (Session ID: %4) |
| 0xb000501a | 8.11011 | Shadow Control Session Started User %1 on computer %2 controlling user %3 (Session ID: %4) |
| 0xb000501b | 8.11011 | Shadow Control Session Stopped User %1 on computer %2 controlling user %3 (Session ID: %4) |
| 0xb000501c | 8.11011 | Shadow View Permission Granted User %1 (Session ID: %3) granted permission to user %2 |
| 0xb000501d | 8.11011 | Shadow View Permission Denied User %1 (Session ID: %3) denied permission to user %2 |
| 0xb000501e | 8.11011 | Shadow Control Permission Granted User %1 (Session ID: %3) granted permission to user %2 |
| 0xb000501f | 8.11011 | Shadow Control Permission Denied User %1 (Session ID: %3) denied permission to user %2 |
| 0xb0005020 | 8.11011 | Shadow Session Failure User %2 encountered error %3 trying to shadow user %1 (Session ID: %4) |
| 0xb0005021 | 8.11011 | Shadow Session Failure User %2 was unable to shadow user %1 (Session ID: %3) because of group policy settings. |
| 0xb0005022 | 8.11011 | Shadow Session Failure User %2 was unable to shadow user %1 (Session ID: %3) because that session is already being shadowed. |
| 0xb0005023 | 8.11011 | Session %1 has been idle over its time limit, and was logged off |
| 0xb0005024 | 8.11011 | Session %1 has been idle over its time limit, and was disconnected |
| 0xb0005025 | 8.11011 | Session %1 has exceeded its time limit, and was logged off |
| 0xb0005026 | 8.11011 | Session %1 has exceeded its time limit, and was disconnected |
| 0xb0005027 | 8.11011 | Session %1 has exceeded its disconnect time limit, and was logged off |
| 0xb0005028 | 1011 | User config info will be loaded from domain controller for this %1 connection |
| 0xb0005029 | 1011 | User config info will be loaded from local machine for this %1 connection |
| 0xb000502a | 1011 | Shadow Session Clipboard Copy Request User %1 on computer %2 controlling user %3 (Session ID: %4) Clipboard format: %5 |
| 0xb000502b | 1011 | Connection from listener %1 will have terminal class of %2 |
| 0xb000c404 | 1011 | The remote session could not be established from remote desktop client %1 because its license could not be renewed. |
| 0xb000c413 | 1011 | The Remote Desktop Session Host server cannot communicate with the Remote Desktop license server %1. Ensure that the computer account for the Remote Desktop Session Host server is a member of the RDS Endpoint Servers group on the license server. |
| 0xb000c425 | 1011 | Remote Desktop Session Host server was unable to retrieve users licensing information from AD. Error %1 |
| 0xb000c426 | 1011 | Remote Desktop Session Host server was successfully validated %1 licensing information from AAD. |
| 0xb000c427 | 1011 | Remote Desktop Session Host server was unable to retrieve user licensing information from AAD. Error %1 |
| 0xb000c428 | 1011 | Remote Desktop Session Host server was unable to validate RDS license. Error %1 |
| 0xb000c468 | 1011 | The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up. |
| 0xb000c469 | 1011 | The RD Licensing grace period is about to expire on %1 and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up. |
| 0xb000c46a | 1011 | The Remote Desktop Session Host server does not have a Remote Desktop license server specified. To specify a license server for the Remote Desktop Session Host server, use the Remote Desktop Session Host Configuration tool. |
| 0xb000c46b | 1011 | The Remote Desktop Session Host server could not contact the Remote Desktop license server %1. Ensure that the Remote Desktop Licensing service is running on the license server, that the license server is accepting network requests, and that the license server is registered in WINS and DNS. |
| 0xb000c46c | 1011 | The Remote Desktop license server %1 does not support the version of the operating system running on the Remote Desktop Session Host server. |
| 0xb000c46d | 1011 | The certificate issued by the Remote Desktop license server to the Remote Desktop Session Host server is not valid. The license server will not issue Remote Desktop Services client access licenses to clients connecting to the Remote Desktop Session Host server. To resolve this issue, delete the certificate on the Remote Desktop Session Host server and then restart the Remote Desktop Services service. |
| 0xb000c480 | 1011 | The Remote Desktop Virtualization Host server cannot issue a client license. It was unable to issue the license due to a changed (mismatched) client license, insufficient memory, or an internal error. Further details for this problem may have been reported at the client's computer. |
| 0xb000c481 | 1011 | The RD Licensing grace period has expired and Licensing mode for the Remote Desktop Virtualization Host server has not been configured. Licensing mode must be configured for continuous operation. |
| 0xb000c482 | 1011 | The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Virtualization Host server can operate without a license server for 120 days after initial start up. |
| 0xb000c483 | 1011 | The RD Licensing grace period is about to expire on %1 and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Virtualization Host server can operate without a license server for 120 days after initial start up. |
| 0xb000c484 | 1011 | The Remote Desktop Virtualization Host server does not have a Remote Desktop license server specified. To specify a license server for the Remote Desktop Virtualization Host server, use the RDS module for Windows PowerShell. |
| 0xb000c485 | 1011 | The Remote Desktop Virtualization Host server could not contact the Remote Desktop license server %1. Ensure that the Remote Desktop Licensing service is running on the license server, that the license server is accepting network requests, and that the license server is registered in WINS and DNS. |
| 0xb000c486 | 1011 | The Remote Desktop license server %1 does not support the version of the operating system running on the Remote Desktop Virtualization Host server. |
| 0xb000c487 | 1011 | The certificate issued by the Remote Desktop license server to the Remote Desktop Virtualization Host server is not valid. The license server will not issue licenses to clients connecting to the Remote Desktop Virtualization Host server. To resolve this issue, delete the certificate on the Remote Desktop Virtualization Host server and then restart the Remote Desktop Services service. |
| 0xb000c488 | 1011 | The Remote Desktop Virtualization Host server cannot communicate with the Remote Desktop license server %1. Ensure that the computer account for the Remote Desktop Virtualization Host server is a member of the RDS Endpoint Servers group on the license server. |
| 0xc00003fe | 78.11011 | TermService clustering failed to redirect a client to an alternate clustered server, ntstatus=%1. |
| 0xc0000400 | 78.11011 | TermService clustering failed to initialize because the Session Directory Provider failed to initialize, hresult=%1. |
| 0xc000040b | 8.11011 | RD Session Host Server listener stack was down. The relevant status code %1. |
| 0xc000040c | 8.11011 | RD Session Host Server session creation failed. The relevant status code was %1. |
| 0xc0000411 | 78.11011 | Autoreconnect failed to reconnect user to session because authentication failed. (%1) |
| 0xc0000416 | 8.11011 | Failed to load RD Session Host Server Profile path. Note that the profile path must be less than 256 characters in length. User Name: %1 Domain: %2 |
| 0xc000041a | 8.11011 | The RD Session Host Server listener %1 is configured with inconsistent authentication and encryption settings. The Encryption Level is currently set to %2 and Security Layer is set to %3. These settings were automatically corrected to allow connections to proceed. Please change the Security Layer and Encryption Level settings in Group Policy or by using the Remote Desktop Session Host Configuration tool in the Administrative Tools folder. |
| 0xc000041b | 8.11011 | The RD Session Host Server is configured to use SSL with user selected certificate, however, no usable certificate was found on the server. The default certificate will be used for RD Session Host Server authentication from now on. Please check the security settings by using the Remote Desktop Session Host Configuration tool in the Administrative Tools folder. |
| 0xc000041c | 8.11011 | The RD Session Host Server is configured to use a certificate that will expire in %2 days. %1 The SHA1 hash of the certificate is in the event data. Please check the security settings by using the Remote Desktop Session Host Configuration tool in the Administrative Tools folder. |
| 0xc000041d | 8.11011 | The RD Session Host Server is configured to use a certificate that is expired. %1 The SHA1 hash of the certificate is in the event data. The default certificate will be used for RD Session Host Server authentication from now on. Please check the security settings by using the Remote Desktop Session Host Configuration tool in the Administrative Tools folder. |
| 0xc000041e | 8.11011 | The RD Session Host Server is configured to use a certificate that does not contain an Enhanced Key Usage attribute of Server Authentication. %1 The SHA1 hash of the certificate is in the event data. The default certificate will be used for RD Session Host Server authentication from now on. Please check the security settings by using the Remote Desktop Session Host Configuration tool in the Administrative Tools folder. |
| 0xc000041f | 8.11011 | The RD Session Host Server is configured to use a certificate but is unable to access the private key associated with this certificate. %1 The SHA1 hash of the certificate is in the event data. The default certificate will be used for RD Session Host Server authentication from now on. Please check the security settings by using the Remote Desktop Session Host Configuration tool in the Administrative Tools folder. |
| 0xc0000420 | 8.11011 | A new self signed certificate to be used for RD Session Host Server authentication on SSL connections was generated. The name on this certificate is %1. The SHA1 hash of the certificate is in the event data. |
| 0xc0000421 | 8.11011 | The RD Session Host Server has failed to create a new self signed certificate to be used for RD Session Host Server authentication on SSL connections. The relevant status code was %1. |
| 0xc0000422 | 8.11011 | The RD Session Host Server has failed to replace the expired self signed certificate used for RD Session Host Server authentication on SSL connections. The relevant status code was %1. |
| 0xc0000423 | 8.11011 | The RD Session Host Server authentication certificate configuration data was invalid and the service reset it. If the computer was configured to use a specific certificate, please verify it is available in the certificate store and use the administrative tools to select it again. |
| 0xc0000424 | 8.11011 | The Remote Desktop Services User Home Directory was not set because the path specified does not exist or not accessible. The default Home Directory Path was used instead. User Name: %1 Domain: %2 |
| 0xc0000426 | 1011 | The RD Session Host server is configured to use a template-based certificate for Transport Layer Security (TLS) 1.0\Secure Sockets Layer (SSL) authentication and encryption, but the subject name on the certificate is invalid. %1 The SHA1 hash of the certificate is in the event data. Therefore, the default certificate will be used by the RD Session Host server for authentication. To resolve this issue, make sure that template used to create this certificate is configured to use DNS name as subject name . |
| 0xc0000427 | 8.11011 | A new template-based certificate to be used by the RD Session Host server for Transport Layer Security (TLS) 1.0\Secure Sockets Layer (SSL) authentication and encryption has been installed. The name for this certificate is %1. The SHA1 hash of the certificate is provided in the event data. |
| 0xc0000428 | 8.11011 | The RD Session Host server cannot install a new template-based certificate to be used for Transport Layer Security (TLS) 1.0\Secure Sockets Layer (SSL) authentication and encryption. The following error occured: %1. |
| 0xc0000429 | 8.11011 | The template-based certificate that is being used by the RD Session Host server for Transport Layer Security (TLS) 1.0\Secure Sockets Layer (SSL) authentication and encryption has expired and cannot be replaced by the RD Session Host server. The following error occurred: %1. |
| 0xc000042a | 8.11011 | RD Session Host Server was unable to process session arbitration request. Error %1 |
| 0xc000042b | 8.11011 | The RD Session Host server cannot register 'TERMSRV' Service Principal Name to be used for server authentication. The following error occured: %1. |
| 0xc000042e | 8.11011 | A logon request was denied because the RD Session Host server is currently in drain mode and therefore not accepting new user logons. To configure the server to allow new user logons, use the Remote Desktop Services Configuration tool. |
| 0xc000042f | 8.11011 | A connection request was denied because the RD Session Host server is currently configured to not accept connections. To configure the server to allow connections, use the chglogon command-line tool. |
| 0xc0000430 | 1011 | The cn column for the template-based certificate %1 returned an unknown data type %2. |
| 0xc0000431 | 1011 | The msPKI-Cert-Template-OID column for the template-based certificate %1 returned an unknown data type %2. |
| 0xb000502c | 11 | Supplemental Kerberos credentials are not configured |
| 0xb000502d | 11 | Successfully updated supplemental Kerberos credential %1 in %2 logon session |
| 0xb000502e | 11 | Successfully removed supplemental Kerberos credential %1 from %2 logon session |
| 0xb000502f | 11 | Failed to update supplemental Kerberos credentials. %1 |
| 0xb0005030 | 11 | Failed to update supplemental Kerberos credential %1 in %2 logon session. %3 |
| 0xb0005031 | 11 | Failed to remove supplemental Kerberos credential %1 from %2 logon session. %3 |
| 0xb0005032 | 11 | Supplemental Kerberos credential %1 configuration is invalid. %2 |
| 0xb0005033 | 11 | Remote Desktop Service's Threadpool is in terminated state. Remote Desktop Connections may not work, this usually happens when TermService is being shutdown. If this was unintentional, restart Termservice manually. |
| 0x3eb | 78.1 | The remote desktop client '%1' has provided an invalid license. |
| 0x3ec | 78.1 | The Remote Desktop Session Host server cannot issue a client license. It was unable to issue the license due to a changed (mismatched) client license, insufficient memory, or an internal error. Further details for this problem may have been reported at the client's computer. |
| 0x3f3 | 78.1 | The remote session could not be established from remote desktop client %1 because its temporary license has expired. |
| 0x42c | 78.1 | The RD Licensing mode has not been configured. |
| 0x42d | 78.1 | The RD Licensing grace period has expired and Licensing mode for the Remote Desktop Session Host server has not been configured. Licensing mode must be configured for continuous operation. |
| 0xb0000100 | 7 | Terminal Services Remote Connection Manager is starting up |
| 0xb0000101 | 7 | Terminal Services Remote Connection Manager has finished start up. Return code %1 |
| 0xb00003ee | 7 | The terminal server received large number of incomplete connections. The system may be under attack. |
| 0xb0000470 | 7 | Terminal Server role is not installed. |
| 0xb0000471 | 7 | The roaming user profile cache manager for Terminal Services could not start. Error Code: %1 |
| 0xb0000472 | 7 | The roaming user profile cache manager for Terminal Services could not start because an incorrect value was specified for the monitoring interval. Error Code: %1 |
| 0xb0000473 | 7 | The roaming user profile cache manager for Terminal Services could not start because an incorrect value was specified for the maximum cache size. Error Code: %1 |
| 0xb0000474 | 7 | The "Limit the size of the entire roaming user profile cache" Group Policy setting has been enabled, but the roaming user profile cache manager for Terminal Services has encountered a problem. Error Code: %1 |
| 0xb0000475 | 7 | The "Limit the size of the entire roaming user profile cache" Group Policy setting has been disabled, but the roaming user profile cache manager for Terminal Services has encountered a problem. Error Code: %1 |
| 0xb0000478 | 7 | The roaming user profile cache manager for Terminal Services could not delete the roaming user profile for the user %1. The roaming user profile cache might still exceed the %2 gigabyte limit. Error Code: %3 |
| 0xb0000479 | 7 | The roaming user profile cache manager for Terminal Services deleted the roaming user profile for the user %1 because the roaming user profile cache exceeded the %2 gigabyte limit. |
| 0xb0000482 | 7 | Failed to open KVP registry key. Error Code %1 |
| 0xc0000404 | 78.1 | The remote session could not be established from remote desktop client %1 because its license could not be renewed. |
| 0xc000040b | 7 | Terminal Server listener stack was down. The relevant status code %1. |
| 0xc000040c | 7 | Terminal Server session creation failed. The relevant status code was %1. |
| 0xc0000413 | 7 | The Remote Desktop Session Host server cannot communicate with the Remote Desktop license server %1. Ensure that the computer account for the Remote Desktop Session Host server is a member of the Terminal Server Computers group on the license server. |
| 0xc0000416 | 7 | Failed to load Terminal Server Profile path. Note that the profile path must be less than 256 characters in length. User Name: %1 Domain: %2 |
| 0xc000041a | 7 | The Terminal Server listener %1 is configured with inconsistent authentication and encryption settings. The Encryption Level is currently set to %2 and Security Layer is set to %3. These settings were automatically corrected to allow connections to proceed. Please change the Security Layer and Encryption Level settings in Group Policy or by using the Terminal Services Configuration tool in the Administrative Tools folder. |
| 0xc000041b | 7 | The Terminal Server is configured to use SSL with user selected certificate, however, no usable certificate was found on the server. The default certificate will be used for Terminal Server authentication from now on. Please check the security settings by using the Terminal Services Configuration tool in the Administrative Tools folder. |
| 0xc000041c | 7 | The Terminal Server is configured to use a certificate that will expire in %2 days. %1 The SHA1 hash of the certificate is in the event data. Please check the security settings by using the Terminal Services Configuration tool in the Administrative Tools folder. |
| 0xc000041d | 7 | The Terminal Server is configured to use a certificate that is expired. %1 The SHA1 hash of the certificate is in the event data. The default certificate will be used for Terminal Server authentication from now on. Please check the security settings by using the Terminal Services Configuration tool in the Administrative Tools folder. |
| 0xc000041e | 7 | The Terminal Server is configured to use a certificate that does not contain an Enhanced Key Usage attribute of Server Authentication. %1 The SHA1 hash of the certificate is in the event data. The default certificate will be used for Terminal Server authentication from now on. Please check the security settings by using the Terminal Services Configuration tool in the Administrative Tools folder. |
| 0xc000041f | 7 | The Terminal Server is configured to use a certificate but is unable to access the private key associated with this certificate. %1 The SHA1 hash of the certificate is in the event data. The default certificate will be used for Terminal Server authentication from now on. Please check the security settings by using the Terminal Services Configuration tool in the Administrative Tools folder. |
| 0xc0000420 | 7 | A new self signed certificate to be used for Terminal Server authentication on SSL connections was generated. The name on this certificate is %1. The SHA1 hash of the certificate is in the event data. |
| 0xc0000421 | 7 | The Terminal Server has failed to create a new self signed certificate to be used for Terminal Server authentication on SSL connections. The relevant status code was %1. |
| 0xc0000422 | 7 | The Terminal Server has failed to replace the expired self signed certificate used for Terminal Server authentication on SSL connections. The relevant status code was %1. |
| 0xc0000423 | 7 | The Terminal Server authentication certificate configuration data was invalid and the service reset it. If the computer was configured to use a specific certificate, please verify it is available in the certificate store and use the administrative tools to select it again. |
| 0xc0000424 | 7 | The Terminal Services User Home Directory was not set because the path specified does not exist or not accessible. The default Home Directory Path was used instead. User Name: %1 Domain: %2 |
| 0xc0000425 | 78.1 | Remote Desktop Session Host server was unable to retrieve users Licensing information from AD. Error %1 |
| 0xc0000426 | 7 | The terminal server is configured to use a template-based certificate for Transport Layer Security (TLS) 1.0\Secure Sockets Layer (SSL) authentication and encryption, but the subject name on the certificate is invalid. %1 The SHA1 hash of the certificate is in the event data. Therefore, the default certificate will be used by the terminal server for authentication. To resolve this issue, make sure that template used to create this certificate is configured to use DNS name as subject name . |
| 0xc0000427 | 7 | A new template-based certificate to be used by the terminal server for Transport Layer Security (TLS) 1.0\Secure Sockets Layer (SSL) authentication and encryption has been installed. The name for this certificate is %1. The SHA1 hash of the certificate is provided in the event data. |
| 0xc0000428 | 7 | The terminal server cannot install a new template-based certificate to be used for Transport Layer Security (TLS) 1.0\Secure Sockets Layer (SSL) authentication and encryption. The following error occured: %1. |
| 0xc0000429 | 7 | The template-based certificate that is being used by the terminal server for Transport Layer Security (TLS) 1.0\Secure Sockets Layer (SSL) authentication and encryption has expired and cannot be replaced by the terminal server. The following error occurred: %1. |
| 0xc000042a | 7 | Terminal Server was unable to process session arbitration request. Error %1 |
| 0xc000042b | 7 | The terminal server cannot register 'TERMSRV' Service Principal Name to be used for server authentication. The following error occured: %1. |
| 0xc000042e | 7 | A logon request was denied because the terminal server is currently in drain mode and therefore not accepting new user logons. To configure the server to allow new user logons, use the Terminal Services Configuration tool. |
| 0xc000042f | 7 | A connection request was denied because the terminal server is currently configured to not accept connections. To configure the server to allow connections, use the chglogon command-line tool. |
| 0xc0000468 | 78.1 | The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up. |
| 0xc0000469 | 78.1 | The RD Licensing grace period is about to expire on %1 and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up. |
| 0xc000046a | 78.1 | The Remote Desktop Session Host server does not have a Remote Desktop license server specified. To specify a license server for the Remote Desktop Session Host server, use the Remote Desktop Session Host Configuration tool. |
| 0xc000046b | 78.1 | The Remote Desktop Session Host server could not contact the Remote Desktop license server %1. Ensure that the Remote Desktop Licensing service is running on the license server, that the license server is accepting network requests, and that the license server is registered in WINS and DNS. |
| 0xc000046c | 78.1 | The Remote Desktop license server %1 does not support the version of the operating system running on the Remote Desktop Session Host server. |
| 0xc000046d | 7 | The certificate issued by the Remote Desktop license server to the Remote Desktop Session Host server is not valid. The license server will not issue licenses to clients connecting to the Remote Desktop Session Host server. To resolve this issue, delete the certificate on the Remote Desktop Session Host server and then restart the Remote Desktop Services service. |
| 0xc0000480 | 78.1 | The Remote Desktop Virtualization Host server cannot issue a client license. It was unable to issue the license due to a changed (mismatched) client license, insufficient memory, or an internal error. Further details for this problem may have been reported at the client's computer. |
| 0xc0000481 | 78.1 | The RD Licensing grace period has expired and Licensing mode for the Remote Desktop Virtualization Host server has not been configured. Licensing mode must be configured for continuous operation. |
| 0xc0000482 | 78.1 | The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Virtualization Host server can operate without a license server for 120 days after initial start up. |
| 0xc0000483 | 78.1 | The RD Licensing grace period is about to expire on %1 and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Virtualization Host server can operate without a license server for 120 days after initial start up. |
| 0xc0000484 | 78.1 | The Remote Desktop Virtualization Host server does not have a Remote Desktop license server specified. To specify a license server for the Remote Desktop Virtualization Host server, use the RDS module for Windows PowerShell. |
| 0xc0000485 | 78.1 | The Remote Desktop Virtualization Host server could not contact the Remote Desktop license server %1. Ensure that the Remote Desktop Licensing service is running on the license server, that the license server is accepting network requests, and that the license server is registered in WINS and DNS. |
| 0xc0000486 | 78.1 | The Remote Desktop license server %1 does not support the version of the operating system running on the Remote Desktop Virtualization Host server. |
| 0xc0000487 | 78.1 | The certificate issued by the Remote Desktop license server to the Remote Desktop Virtualization Host server is not valid. The license server will not issue licenses to clients connecting to the Remote Desktop Virtualization Host server. To resolve this issue, delete the certificate on the Remote Desktop Virtualization Host server and then restart the Remote Desktop Services service. |
| 0xc0000488 | 7 | The Remote Desktop Virtualization Host server cannot communicate with the Remote Desktop license server %1. Ensure that the computer account for the Remote Desktop Virtualization Host server is a member of the Terminal Server Computers group on the license server. |
| 0xc0000413 | 8.1 | The Remote Desktop Session Host server cannot communicate with the Remote Desktop license server %1. Ensure that the computer account for the Remote Desktop Session Host server is a member of the RDS Endpoint Servers group on the license server. |
| 0xc0000426 | 8.1 | The RD Session Host server is configured to use a template-based certificate for Transport Layer Security (TLS) 1.0\Secure Sockets Layer (SSL) authentication and encryption, but the subject name on the certificate is invalid. %1 The SHA1 hash of the certificate is in the event data. Therefore, the default certificate will be used by the RD Session Host server for authentication. To resolve this issue, make sure that template used to create this certificate is configured to use DNS name as subject name . |
| 0xc000046d | 8.1 | The certificate issued by the Remote Desktop license server to the Remote Desktop Session Host server is not valid. The license server will not issue Remote Desktop Services client access licenses to clients connecting to the Remote Desktop Session Host server. To resolve this issue, delete the certificate on the Remote Desktop Session Host server and then restart the Remote Desktop Services service. |
| 0xc0000488 | 8.1 | The Remote Desktop Virtualization Host server cannot communicate with the Remote Desktop license server %1. Ensure that the computer account for the Remote Desktop Virtualization Host server is a member of the RDS Endpoint Servers group on the license server. |
| 227 entries | ||