Running Studio - Test Site reports errors similar to:
ConfigLoggingSchema objects, including HighLevelOperationStart, LowLevelOperationStart, OperationDetailStart, OperationDetailStop, and Users.
Table ConfigLoggingSchema.LowLevelOperationStart
object definition does not match the expected reference schema.
Table ConfigLoggingSchema.OperationDetailStart
object definition does not match the expected reference schema.
Table ConfigLoggingSchema.OperationDetailStop
object definition does not match the expected reference schema.
Table ConfigLoggingSchema.Users
object definition does not match the expected reference schema.
Restore the database Logging to the most recent backup
The error indicates that the Configuration Logging database schema differs from the schema expected by the currently installed CVAD version
Citrix detected discrepancies in multiple ConfigLoggingSchema objects
Common causes include:
The above mentioned sample code is provided to you as is with no representations, warranties or conditions of any kind. You may use, modify and distribute it at your own risk. CITRIX DISCLAIMS ALL WARRANTIES WHATSOEVER, EXPRESS, IMPLIED, WRITTEN, ORAL OR STATUTORY, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT. Without limiting the generality of the foregoing, you acknowledge and agree that (a) the sample code may exhibit errors, design flaws or other problems, possibly resulting in loss of data or damage to property; (b) it may not be possible to make the sample code fully functional; and (c) Citrix may, without notice or liability to you, cease to make available the current version and/or any future versions of the sample code. In no event should the code be used to support ultra-hazardous activities, including but not limited to life support or blasting activities. NEITHER CITRIX NOR ITS AFFILIATES OR AGENTS WILL BE LIABLE, UNDER BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY, FOR ANY DAMAGES WHATSOEVER ARISING FROM USE OF THE SAMPLE CODE, INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Although the copyright in the code belongs to Citrix, any distribution of the sample code should include only your own standard copyright attribution, and not that of Citrix. You agree to indemnify and defend Citrix against any and all claims arising from your use, modification or distribution of the sample code
Check permissions on SQL for Logging DB(service account and DDC's computer account)
If a healthy backup exists from the same Citrix deployment and CVAD version:
If historical logging data is not required, as Workaround, recreate the Logging database
recreating the Logging database after taking appropriate backups is a safe and commonly used remediation because the Logging database is not involved in brokering functionality(it stores administrative change history only)
Pre-Requisites:
Open WebStudio-Settings-Database-Edit

Studio-Configuration-Change Database

Studio-Configuration-Change Database(Logging)
Specify a new Logging DB name and click Ok
If you dont have permission on SQL:
Using WebsStudio or Studio generate the Logging database creation script for the current CVAD version
Have the SQL team execute the generated script against the new database
OR Using Citrix PowerShell: CTX232979
Disable Configuration Logging:
Set-LogSite -State Disabled
Remove Existing Connection:
Set-LogDBConnection -DBConnection $null
Create New Database and Grant the Citrix service account appropriate SQL permissions(securityadmin or db_owner):
Speicfy connection string for DB
Re-enable Logging:
Set-LogSite -State Enabled
Run Studio -Test Site and confirm all tests pass
Running Test Site in Citrix Studio - Citrix reports that ConfigLoggingSchema objects definition does not match the expected reference schema.