Pages

Monday, March 10, 2014

Unable to connect to Citrix XenDesktop 7.x Delivery Controller after SQL server being unavailable

I received a call the other day from a client who had the Microsoft SQL Server hosting their Citrix XenDesktop 7.1 environment’s database go down over the weekend and when it came back up, their Delivery Controllers would present the following error:

Delivery Controller address has changed…

Re-enter the Controller address or try a new one.

The Controller cannot be connected to because it is reporting a failure. Ensure that the Controller can connect to its database.

Existing Controller address:

local host

Try again

Enter the address of the controller you want to configure:

image

The client tried restarting the SQL Server and Delivery Controller multiple times but was not able to connect to the Delivery Controllers via the locally installed Citrix Studio.

After logging in and verifying all the services on both the SQL Server and Delivery Controller were up, I proceeded to try using the Enter the address of the controller you want to configure: text field to enter one of the Delivery Controller’s NetBIOS name to see if it would connect:

image

image

… and to my surprise, this allowed me to connect to the Delivery Controller successfully:

image

What was strange was that after being to successfully connect to one Delivery Controller I was able to use localhost to connect via the other 2 Delivery Controllers (there are 3 in the environment).

Hope this helps anyone out there who may come across this issue as I can see how it would cause a bit of grief for the person troubleshooting.

2 comments:

Nitin Chitkara said...

http://citrixtroubleshootingsteps.blogspot.in/2015/03/citrix-xenapp-76-cannot-communicate.html

Anonymous said...

Thank you Terence for the post and solution. It worked for me too! I had a problem with Desktop Delivery Controllers not connecting to their Citrix site database after migrating to Win2019. I verified all required services are up and then entered the NetBIOS name of one DDC in the "Connect" field. In the beginning, it did not connect to the site database and failed but after waiting for some time I tried again and it was able to connect. Again. Other controllers connected right away with no intervention!