Citrix EdgeSight is an availability and performance management solution that monitors applications, devices, sessions, licensing, and network traffic in real time. It provides IT administrators with a way to analyze, resolve, and proactively prevent problems in Windows endpoint, XenDesktop, and XenApp environments.
The architecture for a Citrix EdgeSight server consists of a front-end Web Server and a back-end Database server. The EdgeSight database contains the configuration data for EdgeSight as well as the historical data that is being collected from the EdgeSight agents. As environments grow, so does the size of the EdgeSight database as EdgeSight collects more historical data. It is a common practice to migrate the database to a new server when the database grows too large.
Recently I had the opportunity to migrate the database of a 64-bit EdgeSight 5.4 Server on the Windows 2008 R2 platform. I followed the migration procedure for 64-bit servers outlined in Citrix document CTX118977 (http://support.citrix.com/article/CTX118977). After the upgrade everything appeared to work properly until I tried to create a new Alert rules or User Groups in the Console. I started seeing errors in the Console regarding login failures to the database.
With the assistance of a database administrator, a further analysis on the database server revealed that EdgeSight was still attempting to connect to the old database server. A quick search of the registry on the EdgeSight server showed a connection string was still pointing to the old database server. After the registry key was updated with the correct string and the EdgeSight services were restarted, everything started working again.
The lesson learned here is that you need to update both the 32-bit and the 64-bit database connection string paths on a 64-bit EdgeSight server. The connection string path is in the ZTECH_CONNECTION key and is located in the following two registry paths: