'The remote session was disconnected because there are no Terminal Server License Servers available to provide a license. Please contact the server administrator. The environment was fine but we encountered this before.
Applicable Products
Information![]() Summary
This article contains information on troubleshooting 1003 and 1004 Terminal Server licensing errors. Users attempting to connect to a XenApp server might experience the following Terminal Services related errors in the Event Log:
Event ID: 1003
Source: TermService Type: Information The terminal service client has provided an invalid license.
Event ID: 1004
Source: TermService Description: Unable to acquire a license for user name, domain name.
For more information, see Microsoft TechNet articles - TS Licensing Step-by-Step Guide and Troubleshooting Terminal Server Licensing.
Background
With Microsoft (both regular Client Access License (CAL) and Terminal Services CAL) licenses, before an ICA connection is established (the GINA logon pop-up), the client license must be confirmed to exist and be valid.
Note: Windows XP Professional workstations do not have built-in CALs with respect to Windows 2003 Terminal Server License Servers.
When there is insufficient permissions to the following registry key, connection failures occur. Investigate the Microsoft Terminal Services License manager to see if the workstation is enumerated. If the workstation is not enumerated, then this issue is on the Windows OS level. For more information, contact Microsoft Technical Support and verify that your Windows 2003 Terminal Licenses are activated.
Symptom-1
When connecting with a Citrix ICA Client after downloading a Remote Desktop Protocol (RDP) web client, the RDP client might not exhibit any issues and continue to connect.
Cause-1
The Event Log does not specify the client device that provided the invalid license. Insufficient permissions are being applied to the Microsoft license key in the registry for the Authenticated Users group. When testing, attempt to create an RDP connection after removing the MSLicense key in the registry as a user (no Domain Admin or Power User Group); the RDP connection also fails.
Solution-1
It might be useful to investigate the Cryptography registry keys in HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER on both the server and workstation. See Microsoft TechNet and the usage of RegMon and FileMon for additional information. In addition, see Windows Sysinternals. These changes will be reflected from the client device.
If you are making a desktop connection, then opening ICA connection inside the desktop session (Pass-through) and the subsequent ICA connection will fail. The affected workstation in this case is the server.
Complete the following procedure if you experience licensing errors previously mentioned:
Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.
Note: If using a non-native Windows client (Macintosh, Linux, or a Thin Terminal) without a local registry, the permission changes must be made to the following registry key:
HKEY_LOCAL_MACHINESOFTWARECitrixMSLicensing Symptom-2
After moving the Terminal Services Licensing Server, RDP clients do not exhibit any problems and continue to connect.
Cause-2
A potential race condition between the Icaapi.dll and the Rdpwsx.dll might cause the private certificate key on the Terminal Services server to become unsynchronized.
Solution-2
For Windows 2003 Terminal Server, follow Microsoft TechNet article How to override the license server discovery process in Windows Server 2003 Terminal Services to add the Terminal Server License Server. For Windows 2008 Server follow Microsoft TechNet article - TS Licensing Step-by-Step Guide.
Symptom-3
When connecting an ICA Client using a Wyse WT1200LE version 4.2.x terminal, there is a known issue that exists with the firmware shipped with the thin client device.
An individual workstation might connect to server A but not to server B.
Some client workstations might connect to all servers while others are denied to some servers.
In both cases, the RDP client connection from the same workstation might connect to both servers A and B.
Resolution-3
Upgrade to the latest firmware version 4.4.079 for the discontinued Winterm model 1200LE.
Troubleshooting for Non-Windows Clients
Note: If using a non-native Windows client (Macintosh, Linux, or a Thin Terminal) without a local registry, the preceding permissions (outlined in Issue 1) must be verified on the following registry key on the XenApp Server/Presentation Server:
HKEY_LOCAL_MACHINESOFTWARECitrixMSLicensing
Note: Purge option can be used to clean-up licenses from the stored client access licenses assigned to clients running non-Windows operating systems. For more information, see CTX137608 - DSCheck Maintenance Assistant.
Terminal Server License Key LinuxIsolation Steps
Retrieve Terminal Server License Keys
Notes: These steps are known to correct the preceding issue. The preceding action items, if completed successfully, conclude:
Additional Resources
Microsoft TechNet - TS Licensing Step-by-Step Guide
Disclaimer
Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.
Learning has never been so easy!
Tech Level: 1
When using Citrix or RDP, a user might experience the following message upon connection:
'The remote session was disconnected because there are no Terminal Service License Servers available to provide a license. Please contact your server administrator.'
This issue can be resolved typically by removing a registry key and reconnecting to the RDP or Citrix server.
3 Steps totalStep 1: Open the registry editor
While logged in as an administrator, click 'start'> 'run'
Windows 2003 Terminal Server License Key Generator
In the 'open' field, type 'regedit.exe' and click 'ok.'
Step 2: Locate and delete the MSLicensing registry key![]()
Navigate to HKLMSoftwareMicrosoft key. Export this key for backup purposes.
Find Terminal Server License Key
Find the 'MSLicensing' subkey and delete it.
Step 3: Retry your connection to Citrix/RDP
Vista training manual. Once the key has been deleted, you can try to open the Citrix/RDP session in question again. Note that you do not have to close Internet Explorer (if accessing via this method).
If the problem persists, check the remote end to ensure there is a valid terminal services licensing server online and available.
These steps can also be performed remotely, pending you have admin rights, using a remote registry connection via regedit.
References
1 CommentTerminal Server License Keygen
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |