Session Recording stopped due to insufficient Disk space. Events logged : Event ID 1004 (Citrix Session Recording Logging) and Event ID 2005 (Citrix Session Recording Storage Manager)
Article ID: CTX269105
Updated On:
Description
Description: The storage to save recordings ran out of available disk space.
Event ID : Event ID 1004 (Citrix Session Recording Logging)
The description for the event ID "1004" from the source "Citrix Session Recording Logging" was not found. Either the component that triggers this event is not installed on the local computer, or the installation is damaged. You can install or repair the component on the local computer.
If the event occurred on another computer, the display information had to be saved with the event.
The following information was saved with the event:
Exception caught while in unknown context. Exception caught by unhandled exception handler.
--- Exception Details ---
Type: System.Runtime.InteropServices.COMException
Message: The object invoked has disconnected from its clients. (Exception from HRESULT: 0x80010108 (RPC_E_DISCONNECTED))
Stack trace:
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal (Int32 errorCode, IntPtr errorInfo)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR (Int32 errorCode, IntPtr errorInfo)
at System.Management.SinkForEventQuery.Cancel ()
at System.Management.ManagementEventWatcher.Stop ()
at System.Management.ManagementEventWatcher.Finalize ()
And
Event ID 2005 (Citrix Session Recording Storage Manager)
Data lost while recording file: E:\SessionRecordings\2019\11\13\i_e571b4cf-###-###-##########.icl
3779688 bytes missing.
Session Recording does not save even after the disk space is increased.
Resolution
The reason is that When Session Recording Server detected the hard disk is full, then marked the path as unavailable in order not to write new session's data to the path. This mark will not clear until restart the session recording server.
Also, here is a complete list of event errors and warnings that Session Recording produces in the Windows Event Log to help administrators optimize SCOM monitoring.
Session Recording has three main components : Session Recording Agent, Session Recording Server, Session Recording Player.
The Event Source in Windows Event Log shows below:
- Session Recording Agent
- Session Recording Server
o Citrix Session Recording Broker
o Citrix Session Recording Logging
o Citrix Session Recording Storage Manager Console
- Session Recording Player
Additionally, You could monitor below strings in Windows Event Viewer to check whether Session Recording works well.
1. Data lost while recording file
2. bytes missing
3. Service terminated due to fatal error
4. Session Recording Administrator Logging failed
In Windows Event viewer, the Data source is “Citrix Session Recording Storage”
