Citrix Director error System is currently unavailable when logging in
Article ID: CTX221602
Updated On:
Description
System is currently unavailable when logging into Citrix director and on the event viewer we see "No sites could be accessed"
Environment
Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.
Resolution
Solution 1:
Run "Update-BrokerNameCache –Machines" to refresh Controller DNS name in database. Restart Controller which shows DNSName missing in Get-BrokerController.
Solution 2:
Verify if all the Delivery Controllers' Fully Qualified Domain Names are added at the below location.
On Director Server, Open IIS > Director website > Application Settings > Name Service: Service.AutoDiscoveryAddresses, Value: Delivery controller 1, Delivery controller 2.
If none of the above mentioned article helps then proceed with the following:-
Try with IP/FQDN/NetBios of the controllers in the AutoDiscoveryAddress in IIS director site and reset the IIS.
Solution 3:
Get-brokercontroller should give both the controllers as healthy with correct DNS name.
In the Director logs we noticed that director is trying to fetch/connect with another controller which was a part of the same site one year ago and no longer exist.
Ran > Get-configregisteredserviceinstance | measure --> Output- 125 instance.
The count of the instances is incorrect, it should be 98 for 2 XA/XD 7.6 controllers.
Which proves that the third controller does have entries in the database.
We need to remove all the entries of the 3rd controller from the XA/XD database.
Customers are encouraged to engage their DBA to remove the partial entries of the unwanted controllers.
1. Ran Get-configregisteredserviceinstance | measure
2. Output- 125 instance.
3. The count of the instances is incorrect, it should be 98 for 2 XA/XD 7.6 controllers.
Run "Update-BrokerNameCache –Machines" to refresh Controller DNS name in database. Restart Controller which shows DNSName missing in Get-BrokerController.
Solution 2:
Verify if all the Delivery Controllers' Fully Qualified Domain Names are added at the below location.
On Director Server, Open IIS > Director website > Application Settings > Name Service: Service.AutoDiscoveryAddresses, Value: Delivery controller 1, Delivery controller 2.
If none of the above mentioned article helps then proceed with the following:-
Try with IP/FQDN/NetBios of the controllers in the AutoDiscoveryAddress in IIS director site and reset the IIS.
Solution 3:
Get-brokercontroller should give both the controllers as healthy with correct DNS name.
In the Director logs we noticed that director is trying to fetch/connect with another controller which was a part of the same site one year ago and no longer exist.
Ran > Get-configregisteredserviceinstance | measure --> Output- 125 instance.
The count of the instances is incorrect, it should be 98 for 2 XA/XD 7.6 controllers.
Which proves that the third controller does have entries in the database.
We need to remove all the entries of the 3rd controller from the XA/XD database.
Customers are encouraged to engage their DBA to remove the partial entries of the unwanted controllers.
Problem Cause
Cause :1. Ran Get-configregisteredserviceinstance | measure
2. Output- 125 instance.
3. The count of the instances is incorrect, it should be 98 for 2 XA/XD 7.6 controllers.
Additional Information
https://support.citrix.com/article/CTX206380
Was this article helpful?
Yes
No
Powered by
