Hotfix package name: ES540XA6AgentWX64007.zip
For: EdgeSight for XenApp Agents, Version 5.4, running on Windows Server 2008 R2
Replaces: All previous versions 
Date: December, 2015
Languages supported: English (US), German (DE), Spanish (ES), French (FR), Japanese (JA)
Readme version: 1.00

Readme Revision History

Important Note(s)

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 EdgeSight 5.4 on the Citrix Product Documentation site.

New Fixes in This Release

1. The EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring) might exit unexpectedly.

   [From ES540XA6AgentWX64007][#LC1306]

2. When the Print Spooler Service stops, EdgeSight alerts and email notifications fail to be triggered.

   [From ES540XA6AgentWX64007][#LC2102]

3. Attempts to uninstall Hotfix ES540XA6AgentWX64006 for EdgeSight for XenApp Agent Version 5.4 might fail with errors.

   [From ES540XA6AgentWX64007][#LC2968]

4. After upgrading to Version 5.4.20.35 of EdgeSight, the EdgeSight Agent Service (RsCorSvc.exe; Citrix System Monitoring Agent) can fail to start.

   [From ES540XA6AgentWX64007][#LC3238]

5. The EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring) might go into a restart loop after a database maintenance error.

   [From ES540XA6AgentWX64007][#LC3448]

Fixes from Replaced Hotfixes

1. When launching certain applications, a C++ Runtime Initialization Error may occur which prevents the application from launching.

   This is caused by processes that dynamically link to the same runtime components of Visual C++ libraries as the EdgeSight Agent. In order to avoid this problem, the conflicting processes need to be excluded from EdgeSight monitoring by using the registry keys listed below.

   By default all processes are monitored.

   To exclude specific processes:

   1. Add a list of processes to be excluded from being monitored by EdgeSight (separate the processes by a semi-colon) to the UviProcessList registry key.
   2. Set the UviProcessIsExcluded registry key to 1 to exclude the processes in the list:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rskcore 
   Name: UviProcessList
   Type: REG_SZ
   Data: <semi-colon separated list of processes to exclude>

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rskcore
   Name: UviProcessIsExcluded
   Type: REG_DWORD
   Data: 1 (to exclude the listed processes from being monitored, this is set to 1 by default)

   This enhancement extends the agent’s functionality by providing the option to monitor only specific processes and exclude all others.

   To monitor only specific processes:

   1. Add a list of processes to be monitored by EdgeSight (separate the processes by a semi-colon; do not include any leading spaces in process names) to the UviProcessList registry key.
   2. Set the UviProcessIsExcluded registry key to 0 to include the processes in the list:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rskcore 
   Name: UviProcessList
   Type: REG_SZ
   Data: <semi-colon separated list of processes to monitor>

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rskcore
   Name: UviProcessIsExcluded
   Type: REG_DWORD
   Data: 0 (to include the listed processes to be monitored)

   Note:

   Applying this fix deprecates the following registry key. During the upgrade its values are migrated to the new UviProcessIsExcluded key:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rskcore\UviProcessExcludes

   [From ES540XA6AgentWX64001][#248309]

2. EdgeSight can fail to store an "End User Experience Monitoring Service" value in the SYS_EVENT_TXT.txt log. The following entry is logged when this condition occurs: "SEMS Collector detected data overflow of type 19 for counter."

   [From ES540XA6AgentWX64001][#257873]

3. The EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring Agent) can exit unexpectedly, causing sessions running on XenApp servers to be disconnected at random several times a day. The following error message appears:

   "The Citrix System Monitoring Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service."

   [From ES540XA6AgentWX64001][#259762]

4. The Published Application Launch Count report for compiled scripts displays the number of launch counts incorrectly.

   Note: To address this issue in its entirety, you must install a hotfix that contains Fix #LA0066 before installing this fix. Fix #LA0066 is available as a EUEM hotfix (for Presentation Server and XenApp for Windows Server 2003) and as a XenApp hotfix (for Windows Server 2008).

   The combination of Fixes #LA0066 and #LA0136 resolves the issue in most scenarios. Additionally, consider installing a XenApp hotfix that contains Fix #LA0572. Fix #LA0572 addresses this issue specifically in scenarios with short-lived sessions (sessions shorter than 5 seconds).

   [From ES540XA6AgentWX64001][#LA0136]

5. The EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring Agent) can restart unexpectedly due to a defect in the ZCollect!ProcessTracker::PersistUsage module. The restart generates a rscorsvc.exe.dmp file.

   [From ES540XA6AgentWX64001][#LA0207]

6. The EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring Agent) can restart unexpectedly due to a defect in the QRThread (thread#4 ZCollect!QThread::FindPrincipal called by winsta!RpcWinStationGetAllProcesses_NT6). The restart generates a rscorsvc.exe.hang.dmp file.

   [From ES540XA6AgentWX64001][#LA0208]

7. This fix addresses several instances where the EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring Agent) can restart unexpectedly due to a defect in the ZCollect!ProcessTracker::Find module. The restart generates a rscorsvc.exe.dmp file.

   [From ES540XA6AgentWX64001][#LA0245]

8. The EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring Agent) can restart unexpectedly or can appear to be non-functional while writing to the rscorsvc.exe.hang.dmp file due to a defect in the ZCollect module. The restart generates a rscorsvc.exe.hang.dmp file.

   Another symptom might be that the EdgeSight Agent stops working (the time when the last entry was made in SYS_EVENT_TXT.txt exceeds one hour) and a rscorsvc.exe.hang.dmp file with zero bytes is created.

   [From ES540XA6AgentWX64001][#LA0355]

9. When running the Citrix System Monitoring Agent, some applications might exit unexpectedly.

   [From ES540XA6AgentWX64002][#260104]

10. Several processes, including explorer.exe, iexplore.exe, and cnthelp.exe, running on servers with the EdgeSight Agent installed can exit unexpectedly. The dump of a process shows that the EdgeSight RSIntCor module exited when trying to get version information (RSCorInt!ModInfo::getVersionInfo) for the program module.

    [From ES540XA6AgentWX64002][#LA0769]

11. A generic rscorsvc.exe.dmp file is created for the EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring Agent) for a variety of reasons.

    [From ES540XA6AgentWX64002][#LA0921]

12. EdgeSight causes the ctxprelaunch.exe process to terminate, preventing attempts to pre-launch applications.

    [From ES540XA6AgentWX64002][#LA1409]

13. The EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring Agent) can restart unexpectedly with the following message in the sys_event-txt.txt file: "queue thread has stopped responding."

    A few thread activities might exceed the allowed fixed time (300 seconds) for processing, and the restart generates a rscorsvc.exe.hang.dmp file.

    This fix lets you modify the allowed fixed time beyond 300 seconds. To enable it, you must create the following registry key:

    On 32-bit Windows:

    HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\System Monitoring\Agent\Core\4.00
    Name: MaxQueuedSecs
    Type: REG_DWORD
    Data: <A value of 0x12c (300 seconds) to 0x384 (900 seconds); lower or higher data values are replaced (in code) by 300 and 900>

    On 64-bit Windows:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\System Monitoring\Agent\Core\4.00
    Name: MaxQueuedSecs
    Type: REG_DWORD
    Data: <A value of 0x12c (300 seconds) to 0x384 (900 seconds); lower or higher data values are replaced (in code) by 300 and 900>

    [From ES540XA6AgentWX64002][#LA1478]

14. When launching certain applications, a C++ Runtime Initialization Error may occur which prevents the application from launching.

    This is caused by processes that dynamically link to the same runtime components of Visual C++ libraries as the EdgeSight Agent. In order to avoid this problem, the conflicting processes need to be excluded from EdgeSight monitoring by using the registry keys listed below.

    By default all processes are monitored.

    To exclude specific processes:

    1. Add a list of processes to be excluded from being monitored by EdgeSight (separate the processes by a semi-colon) to the UviProcessList registry key.
    2. Set the UviProcessIsExcluded registry key to 1 to exclude the processes in the list:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rskcore 
    Name: UviProcessList
    Type: REG_SZ
    Data: <semi-colon separated list of processes to exclude>

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rskcore
    Name: UviProcessIsExcluded
    Type: REG_DWORD
    Data: 1 (to exclude the listed processes from being monitored, this is set to 1 by default)

    This enhancement extends the agent’s functionality by providing the option to monitor only specific processes and exclude all others.

    To monitor only specific processes:

    1. Add a list of processes to be monitored by EdgeSight (separate the processes by a semi-colon; do not include any leading spaces in process names) to the UviProcessList registry key.
    2. Set the UviProcessIsExcluded registry key to 0 to include the processes in the list:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rskcore 
    Name: UviProcessList
    Type: REG_SZ
    Data: <semi-colon separated list of processes to monitor>

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rskcore
    Name: UviProcessIsExcluded
    Type: REG_DWORD
    Data: 0 (to include the listed processes to be monitored)

    Note:

    Applying this fix deprecates the following registry key. During the upgrade its values are migrated to the new UviProcessIsExcluded key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\rskcore\UviProcessExcludes

    [From ES540XA6AgentWX64002][#LA1577]

15. The EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring Agent) can exit and then restart intermittently.

    [From ES540XA6AgentWX64003][#LA1289]

16. Real-time alerts that are configured for CPU times might fail when the polling interval exceeds 10 minutes.

    [From ES540XA6AgentWX64003][#LA1706]

17. The ICA Session Round Trip time might be missing from the EdgeSight report. The issue occurs when the error in the sys-event_txt.txt of the agent occurs repeatedly due to a numeric overflow, arithmetic exception, or a string truncation while consolidating the ICA Session Round Trip data of the EdgeSight Agent.

    [From ES540XA6AgentWX64003][#LA1998]

18. Inclusion or exclusion of processes with names that contain more than 15 characters does not work correctly.

    This fix allows using process names up to 31 characters in length.

    [From ES540XA6AgentWX64003][#LA2960]

19. The EdgeSight Agent might fail to validate the license and to send payload data. The issue occurs during system startup if the IMA Service initialization is delayed due to heavy server load.

    This fix introduces support for the following registry key that, if set, allows you to delay the agent’s startup until after the IMA Service has completely initialized:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\System Monitoring\Agent\Ctrx\4.00
    Name: RetryLicensingCheck
    Type: REG_DWORD
    Data: 1

    [From ES540XA6AgentWX64004][#LA0854]

20. The EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring) can restart unexpectedly due to unnecessary counter lookups for disconnected sessions using Performance Data Helper. The restart generates a rscorsvc.exe.hang.dmp file.

    If analysis of the rscorsvc.exe.hang.dmp indicates that a thread is performing a PDHAddCounter lookup called "ctrx_ext!CFlexibleCounterSet::AddCounter," rebuild the Performance Monitoring (Perfmon) counters (for each agent device) by following the steps in Knowledge Center article http://support.microsoft.com/kb/300956.

    Note: Not all rscorsvc.exe.hang.dmp files result from unresponsive threads due to performance counter lookups. As a general rule of thumb, rebuilding the perfmon counters is a good way of addressing most issues logged in rscorsvc.exe.hang.dmp files.

    [From ES540XA6AgentWX64004][#LA1403]

21. If you change user names in Active Directory, the changes are not reflected in the EdgeSight database.

    To enable this fix, you must also install EdgeSight server-side Fix #LA1243 (ES540ServerWX86002; ES540ServerWX64002 or their replacements).

    [From ES540XA6AgentWX64004][#LA1506]

22. The EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring Agent) can exit and then restart intermittently. The following errors are recorded:

    Error in sys_event_txt.txt log:
    "unavailableDB"

    Error in Firebird.log:
    "XNET error: get_free_slot() failed” or “unknown ISC error 0"

    [From ES540XA6AgentWX64004][#LA1761]

23. Version 5.4 of the EdgeSight Agent running on XenApp 6.0 servers might log the following Get-XAFarm command exception:

    "Unable to get farm name: Exception type: System.Management.Automation.Runspaces.PipelineStateInfo - Message: Pipeline execution in runspace <> for command Get-XAFarm failed"

    This log entry is unnecessary and confusing. After installing this fix, the error message is preceded by the following text:

    "Error reading the current administrator data (<>)" is expected on XenApp 6.0.

    [From ES540XA6AgentWX64004][#LA1902]

24. The following error might be recorded in the sys_event_txt.txt log: "Unable to connect to database server RSDatr" and the administrator might be notified of a fatal database error. Also, an rscorsvc.exe.shutdown.dmp file might be created in the EdgeSight data folder. The issue usually occurs when there are connectivity issues with the Firebird Service. This fix lets you set the following registry key to configure a fault tolerance level for the number of database connectivity issues encountered before the error notifications are triggered:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\System Monitoring\Agent\Core\4.00
    Name: DatabaseMaxExceptionLevel
    Type: REG_DWORD
    Value: 2 (default) 3, 4, or 5 (Recommendation: Start with a value of 3)

    [From ES540XA6AgentWX64004][#LA2705]

25. The EdgeSight Active Application Monitoring (AAM) data might not be logged to the EdgeSight Agent database (rsdatr.fdb) due to connectivity issues, and the alerts might not be triggered.

    [From ES540XA6AgentWX64004][#LA2840]

26. The EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring) can restart unexpectedly due to processing of data while shutting down. The restart generates a rscorsvc.exe.shutdown.dmp file.

    [From ES540XA6AgentWX64004][#LA2958]

27. The EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring) can restart due to a defect with connections to an unresponsive database. The restart generates a rscorsvc.exe.hang.dmp.

    [From ES540XA6AgentWX64004][#LA3077]

28. The EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring) can restart unexpectedly while purging inactive sessions. The restart generates a rscorsvc.exe.dmp file.

    [From ES540XA6AgentWX64004][#LA4125]

29. The EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring Agent) can exit unexpectedly while the system shuts down or restarts.

    [From ES540XA6AgentWX64004][#LA4130]

30. When starting the EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring) after launching a session on a client device, the session display might become unresponsive.

    [From ES540XA6AgentWX64005][#LA4032]

31. For agents running on PVS provisioned XenApp servers, the Device Reboot alert can fail due to non-persistent storage locations of the Windows System Event log. To enable this fix, the Window System Event log must be written to persistent storage.

    Important: Along with installing this fix, you must set up the Windows System Event log of each provisioned XenApp server in a permanent storage location.

    [From ES540XA6AgentWX64005][#LA4124]

32. Time changes in the Virtual Desktop Agent causes errors in the EdgeSight Agent payload processing.

    [From ES540XA6AgentWX64005][#LA4593]

33. When configuring the “XenApp Performance” alert rules ("Application Response Failure" and "Application Response Time" alert rules) for Active Application Monitoring scripts, the Launcher can fail to be evaluated, which leads to alerts being triggered. With this fix, the launcher is evaluated properly.

    Note: If you specify the launcher name in a rule, you must use all UPPERCASE letters to do so.

    [From ES540XA6AgentWX64005][#LA4830]

34. This fix addresses a non-paged pool memory issue that occurs when EdgeSight falls behind in processing the collection of Windows event logs. This fix introduces support for the following registry key, which allows you to completely turn off the collection of Windows event logs. One consequence of turning off the collection of Windows event logs is that EdgeSight alert rules that are based on event IDs will not work. After installing this fix but before using this method, create an Agent property to suppress security event logging (and if necessary also to reduce or suppress system/application event logging).

    To enable the fix, set the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\System Monitoring\Agent\Core\4.00
    Name: DisableEventLogging
    Type: REG_DWORD
    Value: 1 (disable); 0 (reenable)

    [From ES540XA6AgentWX64005][#LA5284]

35. If EdgeSight is disabled by using the UI setting, starting the application can cause an infinite load or unload loop. This can slow the process start time because the CPU consumption is high.

    [From ES540XA6AgentWX64005][#LA5461]

36. The EdgeSight Agent Service (rscorsvc.exe; Citrix System Monitoring) might exit unexpectedly if the partition has a corrupt transaction.

    [From ES540XA6AgentWX64005][#LA5760]

37. This feature enhancement updates the SQL API in EdgeSight from Version 3.x to Version 4.1.3 and improves stability while accessing the database.

    [From ES540XA6AgentWX64005][#LC0154]

38. When configuring EdgeSight alerts with the poll interval set to 270 seconds, the first two alerts might occur every 270 seconds but subsequent alerts occur every 360 seconds.

    [From ES540XA6AgentWX64006][#LA4339]

39. The EdgeSight Agent Service (RsCorSvc.exe; Citrix System Monitoring Agent) might quit unexpectedly and the error is recorded in the log file sys_event_txt.txt.

    [From ES540XA6AgentWX64006][#LA4621]

40. After restarting, the EdgeSight Agent (for VDA) does not collect system and disk performance data.

    [From ES540XA6AgentWX64006][#LC0297]

41. After updating the XenServer tools, EdgeSight Agent can delay the appearance of the logon screen for up to 10 minutes in a XenApp 6.5 environment.

    [From ES540XA6AgentWX64006][#LC0839]

42. If EdgeSight versions 5.4.9.10 to 5.4.16.19 are running, the ICA Session Round Trip time information might be empty in the EdgeSight report. The issue occurs when the error in the sys-event_txt.txt of the agent occurs repeatedly due to a numeric overflow, arithmetic exception, or a string truncation while consolidating the ICA Session Round Trip data of the EdgeSight Agent.

    [From ES540XA6AgentWX64006][#LC1547]

43. A large number of event logs can cause the server to run out of memory and stop responding. To prevent this from occuring, change the following registry setting:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\System Monitoring\Agent\Core\4.00
    Name: EventLogThrottleSleep
    Type: REG_DWORD
    Data: 0 through 500

    The default value is 0.

    [From ES540XA6AgentWX64006][#LC1714]

44. With this release, the Firebird database is updated to Version 2.5.3 Update 1 and includes important security updates.

    [From ES540XA6AgentWX64006][#LC2086]

Installing This Release

Notes:

• This version is packaged as a .zip file containing the replacement EdgeSightXA6Agentx64.msi file. For more information about deploying msi files, see Microsoft article 884016 or visit the Microsoft Web site and search on keyword msiexec.
• Caution: Downgrades, also known as rollbacks, from this upgrade are not supported and might leave your systems in an unstable state. This upgrade does not patch the existing installation - it fully replaces it with a new installation. As a result, uninstalling this package removes the entire component from the computer. If the need arises to revert to an earlier version of the product, you must uninstall this package and then reinstall the earlier version of the product. Reverting to an earlier version of the product might result in the loss of settings you configure while this upgrade is installed.
• To install this version successfully, servers must not have registry modification restrictions in place.
• If you are installing this release on a German (DE), French (FR), Spanish (ES), or Japanese (JA) operating system, run the MSI file using the msiexec command and specify the language-specific MST file as the value for the TRANSFORMS argument. Each MST file name includes the two letter language code. For example: msiexec /I EdgeSightXA6Agentx64.msi TRANSFORMS=:de_transform.mst.

To install this version:

1. Copy the file to a shared folder on the network.
2. Extract the compressed file and save the EdgeSightXA6Agentx64.msi file on the computer you want to update.
3. Run the .msi file.
4. Restart the computer if prompted to do so.

If it does not exist already, this will add a new entry, Citrix EdgeSight for XenApp 6 Agent 5.4 x64, to the Add/Remove Programs list.