[NOTE: I had to recently follow similar steps to reduce the size of my EdgeSight database to save disk space]
Document ID: CTX137750 / Created On: Jul 8, 2013 / Updated On: Jul 8, 2013
This document describes how to truncate EdgeSight’s alert and alert_param table. This operation deletes all the “stability” (such as agent’s windows logs like application, system, and security) data.
There are many other conditions that will also justify the need to clean out the “stability” data. Following are some guidelines.
If you have an appropriate reason or requirement, skip the “Pre-requisite” section.
Required conditions (so you do not arbitrarily empty out the alert and alert_param table)-
- Core_zbatch_run.log shows [alert] table grooming resulted in timeout (in excess of 240 minutes) error. The ES web console timeout, “Background Services Query” has default setting of 14400 (seconds, 60s/m * 60m/hr * 4hr).
The setting can be found in “Configure (top tab) > Server Configuration (left tab) > Settings; Timeouts (main window tab).”
- Many days of failure in core_zbatch_run.log.
- The filegroup5 is very large, with alert and alert_param tables being excessively large.
- The customer consent to having the data deleted.
- And one of the conditions:
- The database server had run out of disk space or is about to.
- The “Background Services Query” timeout was extended to a larger value- and timeout failure continues.
Preceding screenshot displays EdgeSight 5.4 Web Server database diagram for “alert” table and its related tables. The highlighted key is “alert_param” table references “alertid,” therefore this relationship must be broken when truncating the “alert” table.
As a pre-requisite for the procedure, do this as late in the working day as possible, it will avoid the grooming job and most of the current day’s performance payloads will have been processed.
You must have access to the EdgeSight database. The step described utilizes the SQL Server Management Studio.
Complete the following steps to truncate the EdgeSight’s alert and alert_param table:
- Stop the EdgeSight Server’s “Citrix RSSH Admin Service” (it stops the dependent “Citrix RSSH Application Manager” service).
- Save a script to recreate the “FK_alert_param_alert” index in “alert_param” table. This script is used to restore the FK.
Right click on FK_alert_param_alert and select Script Key as > CREATE To > New Query Editor Window.
- Drop the FK_alert_param_alert key.
Right click on FK_alert_param_alert and select Delete.
- Click OK on the Delete Object form. (OK button is not displayed in the following screenshot).
- Obtain a New Query window. Run both SQL commands here truncate table alert_param and truncate alert.
In this example, all four commands have been issued at the same time and verified that the tables are empty (0 rows).
- Switch back to the Query Window (for example “SQLQuery6.sql…”) to recreate foreign key. Click Execute button to execute the ALTER TABLE commands.
- Right click on FK_alert_param_alert and select Refresh.
- Expand Keys and verify the FK_alert_param_alert key is present.
- Start the EdgeSight Server’s Citrix RSSH Application Manager service (it starts the dependent Citrix RSSH Admin Service service).
CTX138381 – FAQ – Truncate EdgeSight’s Alert and Alert_Param Table
This document applies to:
[NOTE: I recently ran into this issue and the webinterface.conf changes mentioned in this Citrix forum post solved my issue. I’m also re-posting a Citrix article that covers the same problem.]
SSL 38 Error is Displayed when Launching Applications
Document ID: CTX128812 / Created On: Apr 26, 2011 / Updated On: Aug 24, 2011
Average Rating: not yet rated
When trying to launch an application using ICA Proxy to XenApp via Access Gateway Enterprise the following error message is displayed:
This is possibly because of licensing restrictions as indicated in the article CTX119980 – SSL Error 38 when Launching Applications using Access Gateway Enterprise Edition
This issue can also be because of problems with Domain Name System (DNS) name resolution. When launching an application, the Access Gateway Enterprise Edition appliance uses the method specified in the WebInterface.conf file for name resolution. The Web Interface generates the ICA file. If the WebInterface.conf file is set to dns-port and DNS resolution is not possible, either because no DNS server is specified in the Access Gateway Enterprise configuration or the appliance being in a DMZ where no DNS server is reachable, then the launch of the application fails with the preceding error message.
The first option to resolve this issue is to specify a DNS server in the Access Gateway Enterprise Edition appliance within the Name Servers pane as shown in the following screenshot:
The second option is to edit the WebInterface.conf file on the Web Interface server for that site, to resolve through ipv4-port rather than dns-port. The default location of the WebInterface.conf file is C:\inetpub\wwwroot\Citrix\sitename\conf\. Replace the sitename with the name of your site; the default sitename for a Web site on Web Interface is /Citrix/Xenapp. The following screenshots are sample screenshots of the WebInterface.conf file:
Restart the IIS Web Server after saving the WebInterface.conf file.
This document applies to:
CTX131172 – Hotfix ES540ServerWX64001 (Version 184.108.40.206) – For Citrix EdgeSight 5.4 Server x64
Link to x86 version: CTX131171 – Hotfix ES540ServerWX86001 (Version 220.127.116.11) – For Citrix EdgeSight 5.4 Server x86
Caution! This release may require you to edit the registry. Using Registry Editor incorrectly can cause serious problems that may 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.
Where to Find Documentation
This document describes the issue(s) resolved by this release and includes installation instructions. For additional product information, see Citrix eDocs, the Citrix Product Documentation Library.
New Fixes in This Release
Uploading the payload results in the following error message due to the violation of primary key constraint:
“Cannot insert duplicate key in object ‘dbo.ctrx_session_autoreconnect’.”
When Worker 101 (Performance Upload) and Worker 2 (Database Maintenance) run at the same time, an upload is attempted even though the database is not available. Although the status of Worker 101 is displayed as successful, this situation results in the following payload error:
“Invalid payload, no ENV data found”
When exporting the Session Counts report to Microsoft Excel, the exported data displays “#Value!” in the peak columns.
If multiple users connect to different XenApp servers and are assigned the same session id by the terminal server, the payload from one XenApp Server can overwrite the principal id of the other XenApp Server, resulting in incorrect EdgeSight report data.
Users can run the “Assets for a Device” report against devices for which they do not have user permissions.
If the initial attempt to upgrade a server from EdgeSight Version 5.2 to Version 5.3 or later fails, an error might occur when making subsequent upgrade attempts. The following error message appears in the MSI log:
“Error -2147217900: failed to execute SQL string, error detail: Ambiguous column name ‘appid’., SQL key: SchemaPost530”
Running any of the following reports on Version 5.4 of EdgeSight Web server (Version 18.104.22.16807 or earlier) in the EdgeSight database might generate errors messages:
- Process Errors
- Process Errors for a User Group
- Process Faults
- Process Faults for a User Group
The following error messages are observed:
- An error occurred during the client rendering
- An error has occurred during the report processing (rsProcessingAborted)
- Cannot read the next data row for the dataset edgesight (rserrorreadingnextdatarow)
- Arithmetic over flow error converting expression to data type int
This occurs when the ID generated by the alert table (alert ID) exceeds the maximum integer value (2147483648).
Fixes from Replaced Hotfixes
No hotfixes were replaced by this release.
Installing This Release
- This version is packaged as a .zip file containing the replacement EdgeSightServerx64.msi file and Setup.exe file. For more information about deploying msi files, see Microsoft article 884016 or visit the Microsoft Web site and search on keyword msiexec.
- To install this version successfully, servers must not have registry modification restrictions in place.
To install this version:
- Copy the file to a shared folder on the network.
- Extract the compressed file and save the EdgeSightServerx64.msi file and Setup.exe file on the computer you want to update.
- Run the Setup.exe file.
- Restart the computer if prompted to do so.
If it does not exist already, this will add a new entry, Citrix EdgeSight Server, to the Add/Remove Programs list.
This document applies to: