The WMI Repository is a database which stores meta information and definitions for WMI classes. I suspected this could be damaged and could be the route cause of the issue. In the past I’ve had to rebuild the WMI Repository when I’ve had issues with MMC. I ran a chkdsk on the server as I suspected disk corruption, however Windows 2008 R2 is pretty good when it comes to keeping the file system in order and it was fine. It wasn’t looking good at this point and there weren’t any further errors in the event log for me to go on. I decided to open the Remote Desktop Session Host Configuration MMC so I could check the RDS licensing was all present and correct, however the following message appeared: Restarting the XenApp server made no difference so it was clear there was something a little more serious going on. If the server load is 20000 it means there is a licensing issue which needs resolving. Opening an elevated command prompt window enabled me to run the following command to confirm there was a licensing issue:
#Command to export citrix xenapp 6.5 application qfarm license#
If necessary, set the license server location in the Citrix Group Policy. Check to see if the Citrix Independent Management Architecture service is running without errors.
I logged onto the system to interrogate the event log and it became apparent quite quickly why users couldn’t login. The error stood out like a sore thumb in a relatively clean event log:ĭescription: Citrix XenApp is unable to retrieve the license server location.
I got notified by our support team who required further assistance as its not something they’ve seen before. Anyway, after routine maintenance of a XenApp 6.5 session host we realised that no users were able to get logged in via Citrix Receiver. Now you might say, serves you right for using a product that’s end of life with limited support. Its been a challenging week at work so I thought I’d document something I’ve not come across before in my 6 years of dealing with Citrix XenApp 6.5.