Automatic/Manual Site Upgrade from Citrix Studio during an upgrade from XenApp 7.15 LTSR CU5 to CVAD 1912 CU1 fails with following exceptions:

1. Error Id: XDDS:C46CE32B
 
Exception:
    Citrix.Console.Models.Exceptions.ScriptException Cannot validate argument on parameter 'DatabaseName'. The character length (0) of the argument is too short. Specify an argument with a length that is greater than or equal to "1", and then try the command again.
 

DesktopStudio_ErrorId : UnknownError

    Sdk Error Message : Cannot validate argument on parameter 'DatabaseName'. The character length (0) of the argument is too short. Specify an argument with a length that is greater than or equal to "1", and then try the command again.

2.  All services have not been configured.
Click on view details and scroll to the end and check the message relevant to FMA service under inner exception 


 

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.

Test the connection by executing the below powershell command let.
     a. asnp Citrix*.
     b. Get-logDataStore
     c. Get-MonitorDataStore
     d. Get-command Get*servicestatus
     e. Execute all the commands retrieved by Get*servicestatus to expect "OK" for all FMA services

If any of FMA services or Datastore values return DBunconfigured nullify and set connection strings relevant to FMA service in error.

Detailed description to perform the above steps:

1. Nullify the connection strings on the controller

Set-AnalyticsDBConnection -DBConnection $null -force             
Set-AppLibDBConnection -DBConnection $null -force                
Set-OrchDBConnection -DBConnection $null -force                  
Set-TrustDBConnection -DBConnection $null -force               
Set-HypDBConnection -DBConnection $null -force
Set-ProvDBConnection -DBConnection $null -force                  
Set-BrokerDBConnection -DBConnection $null -force
Set-EnvTestDBConnection -DBConnection $null -force
Set-SfDBConnection -DBConnection $null -force
Set-MonitorDBConnection -DataStore Monitor -DBConnection $null -force
Set-MonitorDBConnection -DBConnection $null -force
Set-LogDBConnection -DataStore Logging -DBConnection $null -force
Set-LogDBConnection -DBConnection $null -force
Set-ConfigDBConnection -DBConnection $null  -force
Set-AcctDBConnection -DBConnection $null -force
Set-AdminDBConnection -DBConnection $null -force


2. Reconfigure connection strings

## Replace <dbserver> with the New SQL server, and instance if present
## Replace <dbname> with the name of your restored Database
## Note: AdminDBConnection should be first

$ServerName="<SQL server Name>"
$SiteDBName = "<DbName(case sensitive)>"
$LogDBName = "<LoggingDbName>"
$MonitorDBName = "<MonitorDbName>"
$cs="Server=$ServerName;Initial Catalog=$SiteDBName;Integrated Security=True"
$csLogging= "Server=$ServerName;Initial Catalog=$LogDBName;Integrated Security=True"
$csMonitoring = "Server=$ServerName;Initial Catalog=$MonitorDBName;Integrated Security=True"

Set-AdminDBConnection -DBConnection $cs
Set-ConfigDBConnection -DBConnection $cs
Set-AcctDBConnection -DBConnection $cs
Set-AnalyticsDBConnection -DBConnection $cs
Set-HypDBConnection -DBConnection $cs              
Set-ProvDBConnection -DBConnection $cs
Set-AppLibDBConnection -DBConnection $cs
Set-OrchDBConnection -DBConnection $cs
Set-TrustDBConnection -DBConnection $cs
Set-BrokerDBConnection -DBConnection $cs
Set-EnvTestDBConnection -DBConnection $cs
Set-SfDBConnection -DBConnection $cs
Set-LogDBConnection -DBConnection $cs
Set-LogDBConnection -DataStore Logging -DBConnection $csLogging
Set-MonitorDBConnection -DBConnection $cs
Set-MonitorDBConnection -DataStore Monitor -DBConnection $csMonitoring

3. Reboot the controller and run Automatic site upgrade again
4. If this doesn't resolve, run the manual site upgrade and run the Upgrade Scripts generated on the SQL database in SQLCMD mode.

---

Problem Cause

DB connection strings were missing on multiple DDC