Session Recording

Fixed issues in 2203 LTSR CU5

Compared to: Session Recording 2203 LTSR CU4

Session Recording 2203 LTSR CU5 contains all fixes included in the 2203 LTSR initial release, CU1, CU2, CU3, CU4 plus the following, new fixes:

  • Player users might not find any recordings from a search when only published apps or desktops are specified for their recordings to be visible to the specified viewer. [SRT-11332]

  • You might see the following error message in the Windows Event Viewer of the VDA: “Error: Failed to send disable recording request for session”. The error message indicates that the “disable recording” request (request not to record a session) wasn’t sent to the VDA successfully. This is an issue with the communication between the Session Recording agent and the Windows VDA. [SRT-12270]

  • When you press the Enter key when the cursor is on the database field, a misleading error is displayed. [CVADHELP-24494]

  • Citrix Session Recording Storage Manager displays the following error message:

    event 2067 - Exception caught while receiving message.

    [CVADHELP-24167]

  • When a database schema is not upgraded but server components are upgraded, the stored procedure, such as start recording, fails. [CVADHELP-24200]

  • When you use a VDA with Windows server 2016 EN and the Session recording agent 2203cu3 (22.3.3.3300), the Session recording Agent service fails on start and is terminated unexpectedly. [CVADHELP-24057]

  • A black window might appear with published apps on client device after you enable session recording. [CVADHELP-24025]

Fixed issues in 2203 LTSR CU5

In this article