Basic XenApp Licensing troubleshooting

Troubleshooting licensing issues in XenApp 6 and 6.5

1. Make sure the license server name on the license file has the same name as the hostname of the license server (note: the name is case sensitive, so if the hostname has upper and lower case, the license file must match the upper and lower case of the hostname)

The license file is located in c:\program files (x86)\citrix\Licensing\My Files folder. The license file has a .LIC extension.

It can be opened by MS WordPad, but it cannot be modified (it has a signed key, which is a encrypted signature for the number of licenses described in the top of the file, so if you change the number of licenses manually, the signed key won’t match the signed key and this will make your license file useless)

NOTE: The license file is tied to dates, not the version of XenApp. As long as the date interval for the license is  valid, the subscription advantage  license is valid and the license file doesn’t care what version of XenApp you have.


2. Open a command prompt and type : “netstat -a” on the licensing server and see if port 27000 is listening.

3. If you change the license file name or did any modifications  in the policies container of XenApp (DSC or Apps Center) make sure to run from the command prompt “gpupdate /force” on the server you made the change(s)

4. Open a command prompt and type “net stop imaservice” and “net start imaservice”  to restart the IMA service after the gpupdate,  so IMA can re-read the policies

5. To check if the Licensing registry key is correct: (on the XenApp server or servers), open regedit and look into the [HKEY_LOCAL_MACHINE\Software] hive for this key:



Make sure you see something like this:


“LicenseServerHostName”=”server name”

To recreate the ICA listener in XA6.0 or XenApp 6.5:

Navigate to the [HKEY_LOCAL_MACHINE\System] hive and look for this key:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\ICA-Tcp]

Delete the ICA-Tcp key and reboot.

After rebooting import the ICA listener key from another server that is working properly

(see this Citrix article here for more details)

Miscellaneous information on the Licensing Server
The Citrix License Server maintans a list of users based on the concurrent license model.
The license server can be installed on the following type of servers:

File server
DB server
Web server
XenApp server

If license server fails there is a 720 hrs or 30day grace period
License server groups can be found here: ctx106282
License files are timed to dates – no specific versions of Xen App
License files are located in the c:\Program Files\Citrix\licensing\My files folder
The license file has a signed key which is the encrypted signature of the file. Modifying this file will make it unusable

Event ID 7034 logged in the EventViewer System log of the Licensing server is related
to an issue when the Citrix Licensing service unexpectedly stops on License Server 11.6.1 Build 10007 running on Windows Server 2003, when logging off the server console. This issue occurs when logging off the physical console or logging off RDP session 0 that was established using the /console or /admin switch.

The cause: The underlying code of the License Server does not properly handle the Windows logoff function

The workaround
: the recovery option of the Citrix Licensing service can be modified to restart the service when it fails.

To modify the recovery option of the Citrix Licensing service, complete the following procedure:

In the Recovery tab of the Citrix Licensing service, set the response for first, second, and subsequent failures to Restart the Service.
Set the Restart service after option to 0 minutes (see the CTX article with screen shot)


Citrix Licensing Service Crashes on Startup with event id 1000:

Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Description: Faulting application lmadmin.exe, version, faulting module lmadmin.exe, version, fault address 0x0005d8c2.

The Cause:
The C:\Program Files\Citrix\Licensing\LS\conf\concurrent_state.xml and or the C:\Program Files\Citrix\Licensing\LS\conf\activation_state.xml files becomes unusable and the Citrix Licensing Service, lmadmin.exe, file does not properly handle the unusable file and crashes.

The Workaround: Delete the concurrent_state.xml and the activation_state.xml files.
Restart the license server.

These files are recreated after restarting the license server allowing the Citrix Licensing Service to successfully start and the Citrix License Server to function normally.

This is a bug on the Citrix code for both Licensing Server 11.6 and 11.9, as confirmed here. Wait for the next version of Licensing Server

Windows Updates and Anti-Malware software can cause the License server to stop working
The License Server uses the following ports:
Port 8082 – The License Management Console uses this port and needs to be open in order for you to view the console
Port 27000 – Used by XenApp servers to communicate with the License Server
Port 7279 – Static port for the Citrix vendor daemon

If The licensing service stops working after a Windows update or because the Anti-virus, Anti malware software is blocking any of those ports, you might need to disable the Anti-virus, Anti-malware, re-open those ports or even uninstall the Windows update that blocked the port
In addition you can remove the License server installation and reinstall it by using the msi install file found in the Mycitrix website

For the License Server, version 11.9, the Add/Remove Programs may list the license software as product version 7.6, but the registry key should list both the version and the product version of the software, so it should list the version as 11.9 and product version of 7.6. Not sure why this is done but it can be confusing for sure.
The registry key should be HKLM\Software\Citrix\Licensing Server\Install, Check to make sure that is the case and don’t worry: “It is working as designed”!


Xen Desktop User Device licensing issue; Using the new Citrix Licensing VPX appliance (Linux based)


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: