Error when connect via PSM

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

Error when connect via PSM

L3 Networker

Hi everyone,

 

I have just installed my CyberArk 14.2, I create some test account to test connect via PSM. At first, the connect button is greyed out but i manage to make it up after checking document around. However, after press connect and fill in the reason, i continue run into this error. The RDP file is not even download. I can't find any related doc for this error.

 

PSM service is ok, PrivateArk Server shows no error logs.

 

Field_Content_versions_oct20__068Vy00000pN7hpIAC.png 

Here is PSMConsole logs:

 

[19/09/2025 | 14:40:31] | :: | PSMSR583I Vault IP address: 10.19.168.101

[19/09/2025 | 14:40:31] | :: | PSMSR1476W SAML Sessions are disabled in the PSM Server. Reason: SAML Object is not configured for the PSM Server.

[19/09/2025 | 14:40:31] | :: | PSMSR035I Privileged Session Manager version [14.2.3.65] is up

[19/09/2025 | 14:45:08] | :: | PSMSR059E Failed to wait for Internal jobs to exit. Error CASGE001E Thread pool failed to wait for threads

[19/09/2025 | 14:45:08] | :: | PSMSR036I Privileged Session Manager has been normally terminated

 

 

Please kindly advise, thank you!

1 accepted solution

Accepted Solutions

L3 Networker

Hi guy,

 

I have opened a ticket with the TAC team and find the solution as below:

 

Analysis/Troubleshooting:

- We identified from the logs that the PSM session is being triggered and throwing error such as;

2025-09-24 16:36:58,770 || ERROR || 49 || admin-quang || UI || C61F4 || eb5c0042-2871-4560-af4a-e3c9adeab637 || EPVWA096E Failed to store the session data for the PSM connection in the Vault. Reason: "Failed to set value in the cache for key:3a943e77-6b72-4466-9967-8d1060f07e74" || ||

- The error usually occurs in a Distributed Vault Environment.

- Upon further check, we acknowledge that the Vault is a Standalone.

- Going through the configuration, we noticed that the 'EnableDistributedConnect' is set to yes, and when the PVWA cannot publish the cache, it fails.

- Upon disabling ('EnableDistributedConnect' set to no), we can now download the RDP file and establish the PSM session successfully.

 

View solution in original post

9 REPLIES 9

L4 Transporter

Hi @Quang Le​ ,

 

Check whether PSMConnect user is disabled or out of sync

L6 Presenter

Could you also check if the component user for PSM shows is 'connected' in your System Health?

L7 Applicator

Hi @Quang Le​ 

 

Please check the following,

 

  • Verify that the PSMConnect and PSMAdminConnect users on the PSM server are not disabled or locked out.
  • Add user PSMAppUser to the "PSMSession" safe.
  • Make sure that the Password Object Name/ID, in the PSM Server Settings (PVWAConfiguration.xml and basic_psm.ini) is the same as the Password Object Name/ID in the Vault, in the safe which the account is configured(the default is PSM safe).
  • Open the GPO settings via a domain controller (gpedit.msc) and check the following location GPO Policies -> Windows Settings -> Security Settings -> Local Policies/User Rights and confirm PSMConnect has rights.
  • Reboot the server, then re-run the PSMHardening.ps1 script. Ensure the PSMConnect user is defined appropriately in the script depending on whether you are using local PSMConnect or domain PSMConnect accounts.

 

Please also follow this KB https://community.cyberark.com/s/article/00002412

 

Hope it helps !

Hi @Tanishq Pandey​ ,

 

Yes, it looks good. Thank you.

Field_Content_versions_oct20__068Vy00000pcS1AIAU.png 

L4 Transporter

L4 Transporter

Hi @Malhar Vora​ ,

 

Thank you, I have check as below:

  • PSMConnect and PSMAdminConnect users on the PSM server > Yes, these users are actived.
  • Field_Content_versions_oct20__068Vy00000pccbmIAA.png
  • Add user PSMAppUser to the "PSMSession" safe > I don't see this Safe, should it created by default after installed? Or i need to create manually?
  • Field_Content_versions_oct20__068Vy00000pcdceIAA.png
  • Make sure that the Password Object Name/ID, in the PSM Server Settings (PVWAConfiguration.xml and basic_psm.ini) is the same as the Password Object Name/ID in the Vault, in the safe which the account is configured(the default is PSM safe). > I don't see this PSM Safe either
  • Open the GPO settings via a domain controller (gpedit.msc) and check the following location GPO Policies -> Windows Settings -> Security Settings -> Local Policies/User Rights and confirm PSMConnect has rights. > Yes, i see it does.
  • Field_Content_versions_oct20__068Vy00000pcIbbIAE.png

 

L3 Networker

Hello everyone,

 

I just have quick update. I search around and finally try to re-install the PSM component as i see from this post. https://community.cyberark.com/s/question/0D52J00006fbEOsSAM/psm-failed-to-handle-the-session-logon-....

 

And it is kind of work for me but it's not fully work.

 

Before re-install,

 

I create a local RDP file instead of download from PVWA, put the info and tried to connect but failed with this error:

 

PSMSR1055E Failed to handle the request for logon credentials by session details. Reason: Failed to establish connection. Reason: 1071E The requested account cannot be used with Privileged Session Manager or with the connection component you specified.

 

The psm command i used were:

  • alternate shell:s:PSM /u administrator /a x.x.x.x /c RDP
  • alternate shell:s:PSM /u administrator /a x.x.x.x /c PSM-RDP

 

But both of them were failed.

 

After re-installing the PSM, PSM-RDP works but RDP still failed with same error ".... The requested account cannot be used with Privileged Session Manager or with the connection component you specified."

 

And even though i can connect from the local RDP file, but when i go to the PVWA, i still not able to download the RDP file and show the error.

 

 

 

L3 Networker

Hi guy,

 

I have opened a ticket with the TAC team and find the solution as below:

 

Analysis/Troubleshooting:

- We identified from the logs that the PSM session is being triggered and throwing error such as;

2025-09-24 16:36:58,770 || ERROR || 49 || admin-quang || UI || C61F4 || eb5c0042-2871-4560-af4a-e3c9adeab637 || EPVWA096E Failed to store the session data for the PSM connection in the Vault. Reason: "Failed to set value in the cache for key:3a943e77-6b72-4466-9967-8d1060f07e74" || ||

- The error usually occurs in a Distributed Vault Environment.

- Upon further check, we acknowledge that the Vault is a Standalone.

- Going through the configuration, we noticed that the 'EnableDistributedConnect' is set to yes, and when the PVWA cannot publish the cache, it fails.

- Upon disabling ('EnableDistributedConnect' set to no), we can now download the RDP file and establish the PSM session successfully.

 

  • 1 accepted solution
  • 574 Views
  • 9 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!