CVAD | How to Change Database Locations of Monitoring and Configuration Logging Databases

Split the monitor and logging databases from site database as part of best practices which will eventually help to resolve excessive growth of site database and improve the performance.

Starting from XenApp/Xendesktop 7.6 we introduced 3 types of databases:

Site: (also known as Site Configuration) stores the running Site configuration, plus the current session state and connection information.

Configuration Logging: (also known as Logging) stores information about Site configuration changes and administrative activities. This database is used when the Configuring Logging feature is enabled (default = enabled).

Monitoring: stores data used by Director, such as session and connection information.

In previous versions of Citrix Virtual Apps and Desktops, such as XenApp and XenDesktop 7.6, the database required for Citrix Virtual Apps and Desktops has been created as one database during the initial Site configuration (via Studio or by running scripts on the SQL Server). After the installation, the admin could split it into different databases to enhance performance or comply with backup/security guidelines.

With newer releases of Citrix Virtual Apps and Desktops, you can create the databases during the initial Site configuration, as well as via Studio, or by running scripts on the SQL Server. Your database is automatically split into three separate databases.

For environments with large Monitoring databases, an ideal configuration would be to host the Monitoring database on a different server from the Site Configuration and Configuration Logging databases. It records more data, changes occur more frequently, and the data is not considered to be as critical as the other databases.

Each cumulative update (CU) for the long-term service release (LTSR) contains fixes to the SQL database schema. For example, see CTX230536. To best protect your environment against unexpected issues, make sure that you have a process to regularly upgrade your environment to the latest CU. Also, make sure that appropriate SQL server and database monitoring are in place to catch failure events and issues with high resource utilization and free space.


  • No Related Posts

How to Troubleshoot Maintenance Upgrade Failures on Citrix Cloud Connector for Windows

Check Windows Services

The first step in diagnosing any issues with Cloud Connector installation is to evaluate the health of the connector machine.

·Login to the Connector machine as administrator.

·Run Services.msc from either the Start Menu or from a Command Prompt.

·The following Citrix services are required to be in Started state for the Cloud Connector’s communications with the Citrix Cloud.


·Try to manually start any stopped services and see if that solves the issue.

·If services are unable to start, review the logs (discussed later) and event view for clues.

·If the services are not listed, the install likely did not complete properly.

·This may require an uninstall, reboot and reinstall of the controller software.

Connectivity Test

·It is important that the Connector meet the proper connectivity requirements prior to installation.


·To troubleshoot connectivity issues quickly, run theCloud Connector Connectivity Check Utility to verify the Machine has the required connectivity.

·Investigate and resolve any proxy or firewall errors.

Advanced Logging

·Enable Additional Debug Logging for Proxy Events on Citrix Cloud Connector


Event messages

  • Event messages are available in the Windows Application Event viewer on the Cloud Connector machine.
  • All Citrix Services report messages to the event viewer.

·Locate any relevant errors that coincide with the time of the install failure.

Event messages

Event messages are available in the Windows Event viewer on the Cloud Connector machine.

·The Windows event logs that the Cloud Connector generates are in the following documents:

·Connector Agent Provider [XML format]

·Connector AgentWatchDog Provider [XML format]

Connector Installation Logs

·Recent installation logsare located here:


·Additionally, historical install logs are added to:


·Search the text files for errors or exceptions.

·Look for key points of interest, like where packages are installed successfully, or communications are being tested.

·Look for any errors that might be related to the exact time of the install failure.

·Common Exit codes

·1603 – An unexpected error occurred.

·2 – A prerequisite check failed.

·0 – Installation completed successfully.


·Make sure the installation pre-requisites are met.

·Make sure the Windows systems are in good health and fully updated.

·Reboot the machine prior to running the install.

Connector logs

·By default, event logs are located in this directory of the machine hosting the Cloud Connector:


·The plugins folder contains many logs that coincide with the Citrix Windows Services.


·Browse these logs if a specific service is failing to start.


·Make sure the installation pre-requisites are met.

·Make sure the Windows systems are in good health and fully updated.

·Reboot the machine prior to running the install.


  • No Related Posts

ShareFile Sync for Windows isn't authenticating the user and Instead opens the Dashboard

To resolve this issue:

  1. Open regedit and navigate to: ComputerHKEY_CURRENT_USERSoftwareCitrixShareFileSync
  2. Check the registry keys for:
  • AccountID
  • CompanyName
  • Email
  • Subdomain
  • UserID
  • UserName

If the information, particularly the subdomain and Email, don’t match the user’s update them to match.(preserve the original values in case they need to be changed back).

Relaunch Sync and have the User log in again and make sure their Sync authenticate and starts syncing data.


  • No Related Posts