ConfigSync Failure May Be Seen When Delivering App-V, MSIX, or MSIX App Attach Packages
book
Article ID: CTX581114
calendar_today
Updated On:
Description
For customers using Delivery Controller Version 2308 and delivering App-V, MSIX or MSIX app attach packages through Citrix, errors with the source “Citrix ConfigSync Service” and the Event ID “505” may be logged to the Windows Event Viewer on Delivery Controllers with the following message:
“The Citrix Config Sync Service failed an import. Exception calling "GenerateCmdletParameterSplatHash" with "4" argument(s): "Bad reference ConfigurationSlot..."."

This issue can cause ConfigSync imports of the Site configuration to the Local Host Cache database to fail. If a prior ConfigSync import was successful, Local Host Cache will work, but will use the old Site configuration data. If no prior ConfigSync import was successful, Local Host Cache will not work.
Resolution
Note: This process must be repeated on all Delivery Controllers in your site. It is advised to take a snapshot of the Delivery Controller before making any changes.
- Download the import script file named "Default.zip", attached to this article.
- Replace the existing “Default.zip” file present in "C:\Program Files\Citrix\Broker\Service\ImportScripts" with the newly downloaded file in the following location on your Deliver Controller
- Trigger a ConfigSync import by running the following PowerShell command:
if ((Get-BrokerSite -Property LocalHostCacheEnabled).LocalHostCacheEnabled) {Set-BrokerSite -LocalHostCacheEnabled $false;Set-BrokerSite -LocalHostCacheEnabled $true}
- Verify that the fix worked by looking in the event viewer on your Delivery Controller for a "Citrix ConfigSync Service" "504" event, which indicates that the import was successful.
Problem Cause
Changes introduced in Delivery Controller version 2308 relating to the initialization of certain App-V, MSIX, and MSIX app attach objects can cause ConfigSync imports to fail
Issue/Introduction
This is a workaround fix to prevent the Config Sync failures due to changes introduced in Delivery Controller version 2308 relating to the initialization of certain App-V, MSIX, and MSIX app attach objects can cause ConfigSync imports to fail
Was this article helpful?
thumb_up
Yes
thumb_down
No