How to solve errors on PSM servers?

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

How to solve errors on PSM servers?

L0 Member

Hi,

we have encountered a problem connecting to some target servers via the PVWA interface.

The problem seems to reside on the two PSM machines; however, the machines are functioning normally, and we can reach the target server from the PSM, via RDP and using the account stored in the Vault by using the “Show Password” function.

We had to add a load balancer for the 2 PSM, after that it won't work anymore.

The main anomaly we encountered is when connecting via a CyberArk Account to a target server. The first session is created and immediately closed, thus invalidating the RDP session for further investigation

Already tried the following solutions:

·       Tried to reconfigure the PVWA to work only with the PSMs and not through the Load Balancer

·       Tried to connect through each of the two PSM we had

·       Tried to connect to a different target server

·       Tried to disable the ScreenSaver on the PSM

·       Tried to disable the ticketing System on the PVWA Interface

·       Tried to create a new entry in the PSM’s list on the PVWA Interface

·       Tried to manipulate the PSM Server object within the Safe, from the PrivateArk Interface

·       Tried to manually run the ApiKeyManager.exe from <PSMInstallationfolder>\Vault.

·       Explicitly granted permission to the users PSMConnect and PSMAdminConnect on :\Program Files (x86)\CyberArk\PSM\Components\PSMInitSession.exe

·       Verified the correct configuration of the Vault.ini file.

·       Verified that the Administator user is not an owner of the PSM Safe.

·       An uninstallation and reinstallation of the two PSM components was also carried out, to no avail.

 

We get this error on the PSMConsole.log while connecting to any target server (log and trace log attached):

[31/10/2023 | 15:31:28] | :: | PSMSR504W [e1c288c3-0b5e-4435-ae31-f9492c3eb909] An exception occurred during the session flow's exception handling procedure (Handling stage: [DisplayErrorNotification], Internal exception: [PSMSC050E Failed to get user token of TS session [4] (System error [2]: The system cannot find the file specified.)])

[31/10/2023 | 15:31:28] | :: | PSMSR948W [e1c288c3-0b5e-4435-ae31-f9492c3eb909] Session keeper did not logoff the session. The session will be forcefully logged off. (Session id: 4). Reason: PSMSR511E The SessionKeeper process already shutdown but with failed exit code 1028.

[31/10/2023 | 15:31:28] | :: | PSMSR966W [e1c288c3-0b5e-4435-ae31-f9492c3eb909] Failed to logoff the session (Diagnostic information: 2). (Session id: 4). Reason: PSMSC050E Failed to get user token of TS session [4] (System error [2]: The system cannot find the file specified.)

[31/10/2023 | 15:31:28] | :: | PSMSRCDA003E Failed to retrieve file categories. Reason: ITATS053E Object e1c288c3-0b5e-4435-ae31-f9492c3eb909.session doesn't exist.

[31/10/2023 | 15:31:28] | :: | PSMSR504W [e1c288c3-0b5e-4435-ae31-f9492c3eb909] An exception occurred during the session flow's exception handling procedure (Handling stage: [EndSession], Internal exception: [PSMSCCDA003E Failed to retrieve file categories. Reason: ITATS053E Object e1c288c3-0b5e-4435-ae31-f9492c3eb909.session doesn't exist. ])

[31/10/2023 | 15:31:28] | :: | PSMSR126E [e1c288c3-0b5e-4435-ae31-f9492c3eb909] Failure occurred while handling session. PSMSR516E [e1c288c3-0b5e-4435-ae31-f9492c3eb909] Failed to invoke SessionKeeper process (More information: [PSMIC004E IPC Pipe Channel connect failed. (Extra details: 1, 536)]) (Codes: -1, -1)

1 accepted solution

Accepted Solutions

L7 Applicator
4 REPLIES 4

L7 Applicator

Hi @Simone Maraldi? 

 

Please check the following KB and see if if helps !

 

https://community.cyberark.com/s/article/PSMSR516E-Failed-to-invoke-SessionKeeper-process

L6 Presenter

Hi @Simone Maraldi​,

 

I think you complicated things a bit with all the changes you applied.

 

A couple of questions to frame the situation:

- Infrastructure version?

- Have you installed any new PSMs?

- Have you applied Hardening and Applocker?

- Do you have the possibility to use individual PSMs to run tests (for example directly from a PSM server so as to bypass the Load Balancer)?

- Can you post the configurations of a Platform to verify the entry used to point the PSM and the PSM configuration part (Administration > Options > PSM...)?

 

A separate check must be done on the balancer side:

- What type of balancer are you using?

- Have you generated and installed the certificates (SAN) on the two servers?

 

Nino

L0 Member

Thank you for your reply,

@Malhar Vora​  the KB fixed the problem. We had the ServerSettings -> TraceLevels=4

changed to 1,2 and restarted the psm. This solved the problem.

@Antonino Bambino​ You are right, we complicated things a lot.

 

Thaks you for your support

Glad to hear that issue is fixed !

  • 1 accepted solution
  • 1335 Views
  • 4 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!