When performing an automatic upgrade to the version CVAD 1912, Citrix Studio returns the following error: "the database has already been configured".

The error details are :

Error Id: XDDS:346DA064

 

Exception:

    DesktopStudio_ErrorId : DatabaseConnectionDetailsAlreadyConfigured

    Error Source : CitrixDelegatedAdmin

    Sdk Error Message : Cannot transition directly from using one data store to another; clear the existing data-store connection first.

    Sdk Error ID : Citrix.XDPowerShell.Status.DatabaseConnectionDetailsAlreadyConfigured,Citrix.DelegatedAdmin.Sdk.DataStore.Commands.SetAdminDBConnectionCommand

    ErrorCategory : NotSpecified

    DesktopStudio_PowerShellHistory : SimplePowerShellScript

There are three modes available for the Configuration Logging as reported by the cmdlet Get-LogSite: Disable, Enable, Mandatory.

This translates in Studio > Logging > Preferences as follows:
Disable: when the radio button ‘Disable’ is selected
Enable: when the radio button ‘Enable’ is selected AND under Logging Security “Allow Changes to the site configuration when the database is not available”
Mandatory: when the radio button ‘Enable’ is selected AND under Logging Security “Prevent changes to the site configuration when the database is not available”

To resolve this issue, rollback the upgrade, then set the Configuration Logging to 'Disable' or Enable' but not ' Mandatory' for the time of the upgrade.
 

---

Problem Cause

The error "the database has already been configured" indicates that the connection strings for some of the CVAD services have not been unconfigured (set to null) during the upgrade process.
We attempted to reset the connection strings manually and verified that the following services returned some errors:

Set-BrokerDBConnection: error "Configuration logging required but unavailable; operation not allowed at this time"
Set-LogDbConnection and Set-MonitorDBConnection: "The operation could not be performed because of a configuration logging error"

Both errors are referring to the Configuration Logging feature.
Running the Cmdlet: Get-LogSite,  confirmed that the the Logging feature was set to 'Mandatory'.