I am currently standing up a new 7.13 environment to test some new features. We will be migrating to it within the next 3 - 6 months. I am having an issue where if a certain delivery controller is offline I cannot open up Studio on the other 3 controllers. We have a total of 4 (2 in each site). I have rebooted everything, including th DB, and still cannot get it to open. Any suggestions?
Unable to open Citrix Studio when one DDC is offlineStarted by Paul Tanner , 20 March 2017 - 07:23 PM
Posted 20 March 2017 - 07:23 PM
Posted 21 March 2017 - 05:10 AM
What do you mean with "Unable to open Studio"?
Any (error) messages?
Posted 21 March 2017 - 10:40 AM
this could be a number of things, it would be useful to know what error message / event log messages you are seeing. It could be one of the required site services is not running on the other controllers.
One thing to try would be to take down 2 of the remaining controllers, leaving a single one up, then reboot that. If that is OK and you can start studio, then bring up the others.
One controller is the primary, if it goes down, there should be an election and an event log message showing this.
Are sessions still brokered by the other controllers ?
Posted 21 March 2017 - 12:49 PM
I did notice that if all 4 DDCs are in the primary zone then I have no issues opening up Studio when any of them are offline. If I move 2 of them to a satellite zone and power off the 2 that remain in the primary zone I cannot open Studio on either of the DDCs in the satellite zone. Is this intended?
The Studio application sits at the "Expand" window and eventually opens up with an error about the configuration service. I have tested the DB connection from the satellite zone and have no issues connecting.
"The Delivery controller address has changed
Reenter the Controller address or enter a new address
Existing controller address
I am also not seeing any event about an election process.
Posted 21 March 2017 - 03:08 PM
Unfortunately at the present time, there must be at least controller up in the primary zone.
The config logging service is dependent on the primary zone being available. There was a change made somewhere around 7.8 due to performance issues (config logging is quite "chatty") with studio in a secondary zone that had more than a certain amount of latency back to the database.
I'll have a look to see if there are any plans to improve on this.
Also tagged with one or more of these keywords: delivery controller, XA713, XenApp, Studio, Offline
|xenapp desktop printing networkprinting windowsserver2012r2 xendesktop||22 views 1 replies||Carl Stalhood 23 March 2017 - 01:48 PM|
|VDA Delivery Controller||176 views 4 replies||christianmdu 22 March 2017 - 10:41 AM|
|xenapp director xendesktop||63 views 0 replies||DJ Eshelman 25 January 2017 - 12:59 AM|
|Studio Host Connection VMWare||131 views 2 replies||Yves-Bernard Paul 23 January 2017 - 03:33 PM|
|licensing xendesktop xenapp||68 views 1 replies||mloenho329 30 December 2016 - 09:29 AM|