Hello Emil,
Thank you for your post. I'm also working with Citrix.
I have built a new 11.5 License server. At this point I have temp license for 90 days and have a Dev server pointing to this new server for the past 2 weeks with no issues. Today I will be moving a Production system to the new 11.5 License server. If everything goes well I will move my entire production farm to the new license server in 2 - 3 weeks.
I will keep you posted.
Thanks,
Chad
Any news here? Having exactly the same problem with a handful fresh installed servers, all joining the same farm, PS 4.5 with HRP 3 and the (required) license server 11.5. The machines are all running the same OS: Win 2k3 SP2 with all patches and all machines are in the same AD domain and subnet.
I tried to reinstall the license server several times, rebooted the whole farm... but after some minutes i have the same errors "left grace period, disabling connections" and "could not obtain a license from server".
In the license management console i can see the permanent licenses (5000) for server connections, and that the exactly number of farm servers have a license assigned (the server names are all correct). When I restart the IMA service i can see the message "successfully connected to license server" in the eventview. But anyway... the errors are still there.
Strange.
Hi, if you have, for example 10 servers in the environment, are all 10 servers registering with the LMC? Also you have the grace license error:
EventID: 9017
Source: MetaFrame
This computer running Citrix Presentation Server will now stop accepting connections. This server is no longer in or could not enter a licensing grace period.
But also are these servers in the LMC?
Are you getting the following message on 100% of your servers?
EventID: 9019
Citrix Presentation Server has successfully contacted the license server X.X.X.X or HostName
--Emil
Exactly. And as i can see in the LMC (therefor the license service is started) all 10 servers HAVE assigned a license (showing 5000 licenses - 10 licenses for the 10 servers and with correct machine names = 4990 left). But still the same error messages and popups.
OK so restart the "CitrixLicensing" Service, change the Farm licensing server for an ip address instead of a name (or vice versa). Then watch all of the servers get the:
Message for the IP and reregister with the license server. If they do not register within 60 minutes bounce IMA.
Hi,
I have sended Logs to citrix to check the root of this issue.
When I have an answer I will post it.
I still have the issue and I have instead name IP etc. but this helps only for this moment... then I get the same error a few days later...
I hope Citrix will find the bug...
Best regards
Thomas
Cool.
I only change the name to an IP so the Servers search for the license server and reconnect. You can also change from hostname to fqdn.
Will be interested to see what the issue is when Citrix respond.
Thanx for all the feedback,
that was one of my first tryouts: changing the global farm setting from netbios name to IP. What i did also was to disable "use farm settings" for the license server and entered an IP there... no effect. All servers are connecting successfully to the LS but always these mysterious errors.
*crying*
Hello All,
I'm still in the same situation I was in last month. I have built a new license server and have temp licenses on it, but I'm unable to point my production farm to it because we are using the temp licenses and it prompts the user every time they log in that they are using temporary licenses. I'm working on getting approval to reissue my license with the new server name, but production changes take a bit longer to get approval. I'm shooting for the week of Feb. 9th or 16th.
Has anyone else tried building a new license server? I see others have uninstalled and reinstalled on the original license server with no luck (I tried the same).
Note: I have not had the issue since I started restarting the License service everynight. I know it's not a fix, but it is better then having systems fail every few days
Hi Chad,
I have reinstalled my License Server a few Times (also with deleting all Directories of it), but I haven't tried to move it to a complete other Server.
It looks that its a License Server bug, when a daily restart helps in your case...
Iam waiting and waiting for Citrix response about analysing my Trace...
I hope they will fix it soon.
The benefit of restarting the License Server (just the Service) is that it clears all of the assigned licenses. When I have a problem with the issuing of licenses against the available pool I restart this service and let all of the Server re-register their users and licenses.
Chad do you have any more information on the current problem? I thought the Temporary license warning was only presented to Local or Domain Admins.
Also if the temporary licenses work does this mean that the issue is the Server Version?
Here is a great resource from citrix including Tools and Docs:
http://support.citrix.com/product/lic/v4.5/doc/
I had the same problem after applying the Hotfix Rollup Pack 3 for Citrix XenApp 5.0 and Citrix Presentation Server 4.5 for Microsoft Windows Server 2003 32-bit Edition
After installed it and rebooted the servers, the edition of my CPS changed from advanced to platinum. Just reconfigured toa advanced and everything was okay after.
I saw that as well, in the AMC the version is correct but in the Licensing Console it says MPS_PLAT/ENT etc.
I was finally able to fix this issue by building a new license server.
Just wanted to add to this - since it was HIGHLY useful...
Had an issue with a 4.5 Presentation Server - same problem: Event ID's 26 and 9017.
Only a single server out of 40+ was impacted on the farm. This has been a recurring issue with this particular server as well.
Changed the setting for that specific server to use the license server's IP address. It immediately was able to contact the license server. After waiting about 15 or 20 minutes, I changed it back to use license server settings from the Farm and it again contacted the license server by name.
It was quite helpful and saved a large facility from 15/20 minutes of down time.
Thanks! :)