Session Recording

Known issues

December 2, 2024

Contributed by:

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]
Session Recording might not function properly. The issue occurs with CU3 and CU4 and is resolved in CU5 and later versions. [SRT-11701]
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]
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]

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Known issues

December 2, 2024

Contributed by:

C B

December 2, 2024

Contributed by:

C B

Known issues

In this article