Matt
asked on
Xenapp 6.5 - Lost connection to SQL datastore - Users no longer able to logon
Hi all,
We recently had an issue whereby our SQL server which holds the Xenapp 6.5 datastore crashed. My understanding was that the Citrix farm should still allow users to logon by using the LHC on the server. However, no one could log on. What is the default behavior when the elected host loses the connection to the SQL server? and is this something I can change?
We recently had an issue whereby our SQL server which holds the Xenapp 6.5 datastore crashed. My understanding was that the Citrix farm should still allow users to logon by using the LHC on the server. However, no one could log on. What is the default behavior when the elected host loses the connection to the SQL server? and is this something I can change?
LHC had a grace period of only 96 hours it means licensing information stored on the data store. Once the 96 hour grace period ended then the licensing will fail and the server will stop accepting incoming connections.
ASKER
this was within 6 hours
Have you rebooted the server or restarted Citrix IMA service?. If Yes, then citrix farm don't allow users to logon.
Man the 96 hour thing hasn't applied since like 2005 or maybe earlier. If the SQL Server goes down, a XenApp server (if it has made at least one connection to the license server) will serve users for a very long time. There is no 96 hour or 30 day time limit - there is NO time limit.
If you have lost connection to the license server then the 30 day (768 hour) license grace period comes in.
I have seen instances when then SQL server goes down or the connection to the database goes down then the XenApp server(s) refuse to allow connections. It is NOT supposed to happen but it does. In these instances, we implemented SQL mirroring where each SQL server was on a different virtual host and the databases were on different storage systems.
If you have lost connection to the license server then the 30 day (768 hour) license grace period comes in.
I have seen instances when then SQL server goes down or the connection to the database goes down then the XenApp server(s) refuse to allow connections. It is NOT supposed to happen but it does. In these instances, we implemented SQL mirroring where each SQL server was on a different virtual host and the databases were on different storage systems.
ASKER
Thanks Carl but that's pretty poor. Its not meant to happen but does. I thought the whole point of the architecture was to allow things to keep working if the database connections goes down. Perhaps I should just revert back to my presentation 4.5 farm as it seems far more resilient. SQL mirroring. cluster, or whatever layer of resilience you want to add. You will still at some point run into a database connection problems. The problem is with XENAPP
I agree but I have seen this happen with PS4.5, XA5, XA6 and XA6.5.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Where can i check if configuration logging is enabled? basically my farm lost the SQL server and 1 of the data collectors. Web interface server was still available. Yet no connections aloud.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.