Product documentation
Session Recording
Current Release 2407 2402 LTSR 2311 2308 2305 2303 2212 2210 2209 2207 2206 2204 2203 LTSR 2201 2112 2110 2109 2107 2106 2104 2103 1912 LTSR 7.15 Service
View PDF

Known issues

December 2, 2024
Contributed by: 
C C B

The following issues have been identified in this release:

  • A 400 Bad Request error might occur when a user attempts to replay recorded sessions using the Session Recording player or web player. The issue can occur when the user is a member of too many Active Directory user groups. To work around this issue, complete the following steps:

    1. Go to the IIS server machine where the Session Recording server is installed and add the MaxFieldLength and the MaxRequestBytes DWORD values under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters.
    2. Set the DWORD values to 65534 in decimal.
    3. Restart the IIS server machine.

    [SRT-13739]

  • Attempts to record Microphone audio fail when HDX audio is transmitted in Real-time Transport Protocol (RTP) mode on a Windows 10 or Windows 11 VDA. [CVADHELP-26534]

  • If you are using Citrix Web App Firewall (WAF) signatures to mitigate in part the CVE-2021-44228 vulnerability, Session Recording might not work as expected. To resolve the issue, exclude the IP addresses of your Session Recording servers from the mitigate_cve_2021_44228 policy on the NetScaler side. [CVADHELP-24365]

  • Attempts to close unresponsive or dormant live recordings automatically or manually by using the ICLDB DORMANT command might fail. The issue occurs when you update Session Recording to 2308 instead of doing a fresh installation. To resolve the issue, run the following script in PowerShell on the Session Recording server machine and ensure that you have administrative access to the Session Recording database:

     Add-Type -AssemblyName System.data
 $registryKey = [Microsoft.Win32.Registry]::LocalMachine.OpenSubKey("SOFTWARE\\Citrix\\SmartAuditor\\Server")
 $dbName = $registryKey.GetValue("DatabaseName")
 $dbInstance = $registryKey.GetValue("SmAudDatabaseInstance")
 write-host "Connecting to $dbInstance\$dbName"
 # Connect db
 $conn = New-Object System.Data.SqlClient.SqlConnection
 $conn.ConnectionString = "workstation id=.;packet size=4096;integrated security=SSPI;data source=$dbInstance;persist security info=True;initial catalog=$dbName"
 $conn.Open()
 $cmd = $conn.CreateCommand()
 $cmd.CommandText = "use [$dbName];if not exists(select * from [dbo].[EndReason] where ID=5) begin insert [dbo].[EndReason] values (5, 'Dormant') end"
 $cmd.ExecuteNonQuery()
 <!--NeedCopy-->

    [SRT-11119]

  • Session Recording doesn’t capture file transfers between a native disk on the session host (VDA) and a disk that’s mapped to the session from the client. [SRT-10514]

  • When you upgrade Session Recording to the latest version, your image resolution scaling settings for lossy screen recording are lost and the default value 1.0 is restored. [SRT-10130]

  • A domain user with local administrator privileges on the Session Recording policy console can add local and domain users to which the action of a policy rule applies. However, a local user with local administrator privileges can add only local users but not domain users. [SRT-5769]

  • The web player might not work properly if you upgrade it from Version 2009 or earlier. To work around the issue, clear your browser cache. [SRT-5624]

  • Rules of custom policies might be lost after you update Session Recording from the version included in XenApp and XenDesktop 7.6 LTSR to the latest version. As a workaround, update the software to the version included in the latest CU of XenApp and XenDesktop 7.15 LTSR and then update it to the latest release. [SRT-4546]

  • When Machine Creation Services (MCS) or Citrix Provisioning (PVS) creates multiple VDAs with Microsoft Message Queuing (MSMQ) installed, those VDAs can have the same QMId. This condition might cause various issues, for example:

    • Sessions might not be recorded even if the recording agreement is accepted.
    • The Session Recording server might not be able to receive session-logoff signals and therefore, sessions might always be in a live state.

    For information about a workaround, see Install, upgrade, and uninstall. [#528678]

Known issues
December 2, 2024
Contributed by: 
C C B
December 2, 2024
Contributed by: 
C C B

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.