PSM sessions are closed randomly.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

PSM sessions are closed randomly.

L0 Member

"Hey everyone, I'm running into an issue with some PSM sessions—they're closing randomly and unexpectedly. The log files show the following errors."

 

SessionXXXXXXXXXX.Recorder.log

 

[28/05/2025 | 13:54:34] | :: | PSMRC059I Desktop capturer initialized, impl: DXGI, status: feature level 45056; 1 screens; desktop size 1920x1200, using builtin software adapter: yes

[28/05/2025 | 13:54:34] | :: | PSMRE008I PSM Recorder started to record

[28/05/2025 | 13:54:34] | :: | PSMRC017I Avi file initialized successfully

[28/05/2025 | 13:54:34] | :: | PSMRC012I PSM Recorder start record (screen resolution: 1920X1200)

[28/05/2025 | 13:54:34] | :: | PSMRE005I Opening [channel-rec-ba4400b1-bff3-49c4-b4a5-d7993d55cffa] channel to parent process

[28/05/2025 | 13:54:49] | :: | PSMRC061I Detected screen setup change, resetting desktop capturer.

[28/05/2025 | 13:54:49] | :: | PSMRC001I PSM Recorder exception occurred. PSMRC062E DXGI capturer error, operation: DXGIDesktopCapture::ReleaseFrame, reason: Screen access lost - session disconnected or resolution changed (Codes: -1, -2005270490)

 

SessionXXXXXXXX.SessionKeeper.log

 

[28/05/2025 | 13:54:31] | :: | SessionKeeper finished initialization. The following parameters were received:

[28/05/2025 | 13:54:31] | :: | Session UUID: [ba4400b1-bff3-49c4-b4a5-d7993d55cffa]

[28/05/2025 | 13:54:31] | :: | Log Folder: [C:\Program Files (x86)\CyberArk\PSM\Logs\Components]

[28/05/2025 | 13:54:31] | :: | Log Level: [1,2]

[28/05/2025 | 13:54:31] | :: | Enable Session Reconnection: [no]

[28/05/2025 | 13:55:00] | :: | PSMSK007I Stop command received from PSM

 

PSMConsole.log

 

[28/05/2025 | 10:50:08] | :: | PSMSR126E [1607939c-544a-4e58-a640-2b6c721e10d9] Failure occurred while handling session. PSMSR280E [1607939c-544a-4e58-a640-2b6c721e10d9] Session component [Recorder] has stopped unexpectedly. Ending session. (Codes: -1, -1)

 

 

PSMTrace.log

 

[28/05/2025 | 10:49:47.392819] | {pid= 2404} | {tid=   5996} | class CPSMBaseException *      | PSM\PSMServer\PSMBaseException.cpp(38)            | :: | PSMSR009I Privileged Session Manager exception occurred. PSMSR280E [1607939c-544a-4e58-a640-2b6c721e10d9] Session component [Recorder] has stopped unexpectedly. Ending session. (Codes: -1, -1)

[28/05/2025 | 10:49:47.403190] | {pid= 2404} | {tid=   4456} | class PipeIPCChannel *       | PSM\PSMServerProtocol\PipeIPCChannel.cpp(261)        | :: | PSMIC008I IPC Pipe Channel was instructed to stop while waiting for data

[28/05/2025 | 10:49:47.403334] | {pid= 2404} | {tid=   4456} | class CIPCChannelExceptionBase *  | PSM\PSMServerProtocol\IPCChannelExceptionBase.cpp(29)    | :: | PSMIC001I IPC Channel exception was thrown. PSMIC013I IPC Pipe Channel received stop event. (Codes: -1, 0)

[28/05/2025 | 10:49:47.403526] | {pid= 2404} | {tid=   4456} | class CPSMProtocolExceptionBase *  | PSM\PSMServerProtocol\PSMProtocolExceptionBase.cpp(29)    | :: | PSMPR001I Protocol exception occurred. PSMPR062I Stop event received, terminating gracefully. (Codes: -1, -1)

[28/05/2025 | 10:50:07.410454] | {pid= 2404} | {tid=   5996} | class CPSMBaseException *      | PSM\PSMServer\PSMBaseException.cpp(38)            | :: | PSMSR009I Privileged Session Manager exception occurred. PSMSR606E [1607939c-544a-4e58-a640-2b6c721e10d9] Timeout occurred while waiting for a specific component to end (Codes: -1, -1)

[28/05/2025 | 10:50:07.411145] | {pid= 2404} | {tid=   5996} | class CPSMBaseException *      | PSM\PSMServer\PSMBaseException.cpp(38)            | :: | PSMSR009I Privileged Session Manager exception occurred. PSMSR269E The recorder already shutdown but with failed exit code -1073740791. (Codes: -1, -1)

[28/05/2025 | 10:50:07.910225] | {pid= 2404} | {tid=   1200} | class PSMFutureWaiterJob *     | PSM\PSMServer\PSMFutureWaiterJob.cpp(21)           | :: | PSMSRThere are jobs to wait for.

[28/05/2025 | 10:50:08.184004] | {pid= 2404} | {tid=  11196} | class CPSMConfigurationManager const * | PSM\PSMServer\PSMConfigurationManager.cpp(799)        | :: | PSMSR174I Starting configuration management operation (operation: lock configuration manager for read)

[28/05/2025 | 10:50:08.184118] | {pid= 2404} | {tid=  11196} | class CPSMConfigurationManager const * | PSM\PSMServer\PSMConfigurationManager.cpp(801)        | :: | PSMSR175I Configuration management operation ended successfully (operation: lock configuration manager for read)

[28/05/2025 | 10:50:08.184171] | {pid= 2404} | {tid=  11196} | class CPSMConfigurationManager const * | PSM\PSMServer\PSMConfigurationManager.cpp(814)        | :: | PSMSR174I Starting configuration management operation (operation: release configuration manager lock (read))

[28/05/2025 | 10:50:08.184224] | {pid= 2404} | {tid=  11196} | class CPSMConfigurationManager const * | PSM\PSMServer\PSMConfigurationManager.cpp(816)        | :: | PSMSR175I Configuration management operation ended successfully (operation: release configuration manager lock (read))

[28/05/2025 | 10:50:08.184279] | {pid= 2404} | {tid=  11196} | class CPSMConfigurationManager const * | PSM\PSMServer\PSMConfigurationManager.cpp(799)        | :: | PSMSR174I Starting configuration management operation (operation: lock configuration manager for read)

[28/05/2025 | 10:50:08.184324] | {pid= 2404} | {tid=  11196} | class CPSMConfigurationManager const * | PSM\PSMServer\PSMConfigurationManager.cpp(801)        | :: | PSMSR175I Configuration management operation ended successfully (operation: lock configuration manager for read)

[28/05/2025 | 10:50:08.184373] | {pid= 2404} | {tid=  11196} | class CPSMConfigurationManager const * | PSM\PSMServer\PSMConfigurationManager.cpp(814)        | :: | PSMSR174I Starting configuration management operation (operation: release configuration manager lock (read))

[28/05/2025 | 10:50:08.184417] | {pid= 2404} | {tid=  11196} | class CPSMConfigurationManager const * | PSM\PSMServer\PSMConfigurationManager.cpp(816)        | :: | PSMSR175I Configuration management operation ended successfully (operation: release configuration manager lock (read))

 

 

"If anyone has an idea of what might be causing the issue, I'd really appreciate it."

 

Thanks!

 

 

 

6 REPLIES 6

L7 Applicator
  • User changed screen resolution during the session.
  • Remote desktop session was interrupted (e.g., network blip, user logoff).
  • Graphics driver or DXGI issue on the PSM server.
  • Multiple monitors or display reconfiguration triggered a capturer reset.

 

 

L0 Member

Hi @Robert Stothard​ 

 

Thanks for responding.

Indeed, the user has two monitors. The problem usually occurs when moving the RDP session from one monitor to the other, but not always; it's random. Our configuration is set to Full Screen and the smart sizing:i parameter is set to 1.

The problem still persists.

 

Thanks for your help. I'm hoping to hear if you have any ideas for a solution.

 

L0 Member

Setting this value to NO may help as i see  "Session component [Recorder] has stopped unexpectedly. Ending session." in the logs

 

https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/psmconnectioncomponents.htm#WindowsSessionsPSMRDP

 

TerminateOnWinAuditTimeout -> No

 

you will need to create the parameter TerminateOnWinAuditTimeout and set the value to no under your RDP connector

L7 Applicator

Hi @Hector Rojas​ 

 

Per error message this issue likely to be caused by a disruption in the screen recording process.

 

PSMRC062E DXGI capturer error, operation: DXGIDesktopCapture::ReleaseFrame, reason: Screen access lost - session disconnected or resolution changed (Codes: -1, -2005270490)

 

 

If the PSM server is under heavy performance load the PSMRecorder process might not be getting enough resources, hence impacting recordings.

 

Please check the PSM CPU performance and try to connect to via another PSM server to see whether you see a different behaviour.

 

L4 Transporter

Hello @Hector Rojas​ 

 

The issue seems to be non-standard resolution or low/poor resolution for recorder to be recorded. Please compare the resolution on your Desktop/Laptop (main Screen) and the Monitor Resolution, if there is discrepancy then that is the issue.

L4 Transporter

Hello @Hector Rojas​ 

 

The issue seems to be non-standard resolution or low/poor resolution for recorder to be recorded. Please compare the resolution on your Desktop/Laptop (main Screen) and the Monitor Resolution, if there is discrepancy then that is the issue.

  • 904 Views
  • 6 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!