| Event Information | According to Microsoft :
Cause :
This event is logged when terminal service client has provided an invalid license.
Resolution :
Delete the appropriate registry subkey
To resolve this issue, delete the MSLicensing registry subkey on the client computer, restart the client computer, and then try again to connect remotely to the terminal server from the client computer. If the issue persists, delete the Certificate, X509 Certificate, X509 Certificate2, and X509 Certificate ID registry entries on the terminal server, restart the terminal server, and then try again to connect to the terminal server from the client computer.
Delete the MSLicensing registry subkey
To perform this procedure on the client computer, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To delete the MSLicensing registry subkey:
Caution : Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.- On the client computer, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.
- If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- Locate the HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing registry subkey.
- Click MSLicensing.
- Before deleting the MSLicensing subkey, back up the subkey. To back up the subkey, do the following:
a.On the Registry menu, click Export Registry File.
b.In the File name box, type mslicensingbackup, and then click Save. If you need to restore this registry subkey, double-click mslicensingbackup.reg. - To delete the MSLicensing subkey, on the Edit menu, click Delete, and then click Yes.
- Close Registry Editor, and then restart the client.
- After the client computer is restarted, try again to connect remotely to the terminal server from the client computer.
Delete the appropriate registry entries on the terminal server
If the issue persists, delete the Certificate, X509 Certificate, X509 Certificate2, and X509 Certificate ID registry entries on the terminal server.
To perform this procedure on the terminal server, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To delete the appropriate registry entries:
Caution : Incorrectly editing the registry can severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.- On the terminal server, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.
- If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Terminal Server\RCM registry subkey.
- Click RCM.
- Before deleting the subkeys, back up the RCM subkey. To back up the subkey, do the following:
a.On the Registry menu, click Export Registry File.
b.In the File name box, type tsrcm, and then click Save. If you need to restore this registry subkey, double-click tsrcm.reg. - To delete the Certificate, X509 Certificate, X509 Certificate2, and X509 Certificate ID registry entries, right-click each entry, click Delete, and then click Yes.
- Close Registry Editor, and then restart the terminal server.
- After the terminal server is restarted, try again to connect remotely to the terminal server from the client computer.
If the issue persists, do the following:- On the client computer, back up and then delete the MSLicensing registry key and its subkeys.
- On the terminal server, back up and then delete the Certificate, X509 Certificate, X509 Certificate2, and X509 Certificate ID registry entries.
- Deactivate and then reactivate the license server.
- Restart the terminal server and the client computer and then try again to connect remotely to the terminal server from the client computer.
Verify :
To verify that the terminal server can discover (contact) a Terminal Services license server with the appropriate type of Terminal Services client access licenses (TS CALs), use Licensing Diagnosis in Terminal Services Configuration.
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To use Licensing Diagnosis in Terminal Services Configuration:- On the terminal server, open Terminal Services Configuration. To open Terminal Services Configuration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration.
- If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- In the left pane, click Licensing Diagnosis.
- Under Terminal Server Configuration Details, the value for Number of TS CALs available for clients should be greater than 0.
|