The Citrix Config Sync Service is unable to import configuration data, resulting in errors during the process. Event logs capture the following:

CDF Traces collected from the Delivery Controller provide further insight, showing messages such as "Cannot insert duplicate key in object 'chb_Config.SecondaryBrokerZones'". This indicates that the database remains unchanged during the import process.
The CDF trace also reports: "HA::SetDBConnection: timeout while waiting for DAL to reset", highlighting a timeout issue.
One notable symptom is the failure to stop the Citrix High Availability Service.

When an attempt is made to stop this service, it becomes stuck in the "Stopping" state, which is a reliable indicator that the issue described may be present.
![]()
"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."
The root cause of the issue is that the High Availability (HA) service remains connected to the existing HA database, as the site service does not stop promptly. The registry key was manually set by an administrator in an older version of Citrix Virtual Apps and Desktops, likely to address reboot scheduling concerns. Some third-party blogs still reference this key, although it is not required in recent versions.
Examine the Windows registry and remove the problematic value.
Registry key: [HKEY_LOCAL_MACHINE\Software\Citrix\DesktopServer\SiteServices]
Value: MaxShutdownTimeSecs
Restart the Citrix High Availability Service or the Delivery Controller after removing the registry value.
It is important to note that this registry key is not set by default on controllers.
Caution! Refer to the Disclaimer at the end of this article before using the Registry Editor.
The purpose of this document is to provide guidance on identifying and resolving a Citrix Config Sync Service issue that might occur after an upgrade.
This specific failure is caused by a registry key value, which prevents the successful import of configuration data.
For further details about Local Host Cache, refer to https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/manage-deployment/local-host-cache.html.