PSM-SSH stopped working after applying CA19-07

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-SSH stopped working after applying CA19-07

L2 Linker

followed patch instruction for psm

replaced psmsshclient.exe and ran applocker rules on psm . . getting following error with psm-ssh connections

 

[10/07/2019 | 18:47:22] | :: | PSMSR543E [54a0cf3b-4cdc-4be2-ac8c-1353ebc6ecda] Failed during job pre-execution phase. Details: CmdRServerJob,PSMSR559E [54a0cf3b-4cdc-4be2-ac8c-1353ebc6ecda] Failed to receive handshake from audit client, probably client application did not start within time limit. Details: [PSMIC004E IPC Pipe Channel connect failed. (Extra details: 1, 536)],-1,536,-1,-1

[10/07/2019 | 18:47:25] | :: | PSMSC113E [54a0cf3b-4cdc-4be2-ac8c-1353ebc6ecda] Uploader job failed because recording file C:\Program Files (x86)\CyberArk\PSM\Recordings\54a0cf3b-4cdc-4be2-ac8c-1353ebc6ecda.SSH.txt doesn't exists.

[10/07/2019 | 18:47:25] | :: | PSMSC074E [54a0cf3b-4cdc-4be2-ac8c-1353ebc6ecda] Failed to upload recording file 54a0cf3b-4cdc-4be2-ac8c-1353ebc6ecda.SSH.txt. Error: PSMSC115E Recording file C:\Program Files (x86)\CyberArk\PSM\Recordings\54a0cf3b-4cdc-4be2-ac8c-1353ebc6ecda.SSH.txt was not found in the local recording folder

[10/07/2019 | 18:47:26] | :: | PSMSC105E The following expected recording file(s) is (are) missing in the actual recordings list of session '54a0cf3b-4cdc-4be2-ac8c-1353ebc6ecda': 54a0cf3b-4cdc-4be2-ac8c-1353ebc6ecda.SSH.txt

 

verified folder permissions on recordings and components

verified application paths on applocker.xml

 

did anyone had similar issue, can anyone please suggest what i am missing

 

Thanks

11 REPLIES 11

L6 Presenter

@Rajender Dudipala​ ,

 

The logs you have posted are a symptom and not the cause.

Need to go a bit further back.

 

Can you check for the following?

 

PSMSR280E [session_ID] Session component [Recorder] has stopped unexpectedly. Ending session

L6 Presenter

The problem faced is only on PSM-SSH or rest of the components and only on 1 PSM or all PSMs?

L4 Transporter

The problem faced is only on PSM-SSH or rest of the components and only on 1 PSM or all PSMs?

L2 Linker

No just tried the patch on one PSM, getting same error with PSM-WinSCP too and PSM-RDP is working fine .

i dont see that particular message in the log.

L0 Member

Hi @Rajender Dudipala​  , can you solve this issue with the patch of the client of PSMSSHClient.exe?

L2 Linker

No, it is still open . we opened a case with CyberArk.

L0 Member

@Rajender Dudipala​ i resolve this problem today with the same logs and i resolve this with the next steps:

 

1) Make a copy of your PSMSSHClient of the old version and paste & replace with the new

2) Next i open the secpol.msc search the rules of the app locker in Application Control Policies and i clean the rules

3) I make a test of the new PSMSSH on a plataform and specify the psm where I made the change and test the connection and for me was succesfull

4) Then a run the script of psmapplocker and make the test again and still succesfull the connection

 

I hope you can resolve with this 🙂

let me know if this solves the issue and I can write up an Article for public view.

 

-Matt

L2 Linker

Hi,

 

Tried solution suggested by @Jose Eduardo Muñoz Flores​ 

 

no luck for me , still failing with same error

 

 

 

L2 Linker

Did anyone ever find the resolution to this issue? We are experiencing the same issue after a recent upgrade from 9.10 to 10.4

  • 1257 Views
  • 11 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!