PSMPrivateArkClientDispatcher failed with error

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

PSMPrivateArkClientDispatcher failed with error

L3 Networker

I'm trying to use "PSM-PrivateArk", but it fails with error as scrreen shot.

I edit the applocker file but it still continues.

Dis anyone solve this issue?

 

The PAS is v10.6

 

Field_Content_versions_oct20__0682J00000670irQAA.png

5 REPLIES 5

L0 Member

Hi kawamura-t,

 

Can you confirm that you re-ran the PSMConfigureApplocker.ps1 script after modifying the .xml file?

 

Additionally we sometimes see this issue when the PSMShadowUser group does not have permissions to execute the application you are trying to run (PrivateArk Client).

 

Can perform the following test and see if this resolves you issue:

 

- RDP to the PSM server 

- Confirm that you can open up PrivateArk Client and connect to the Vault.

- Run PrivateArk Client as a shadow user 

  • Reset the password of a shadow user (use computer management (the user's Full Name will indicate the correct Shadow user). 
  • Run PrivateArk 'as a different user' (right click 'PrivateArkClient.exe' > "Run as different user" > insert the PSM Shadow user + password). 

-- Try to connect to the Vault again

 

Thanks,

George

L5 Sessionator

@Tomoki Kawamura​ 

Please look at your PSM Server's Applocker event viewer logs : (Event Viewer > Application and Services Logs > Microsoft > Windows > AppLocker) and see if something was blocked. If there anything, add them into PSMApplocker and re-run it.

L3 Networker

@Nirmalkumar Dhanaraj​ 

I added the lines below, and re-run PSMConfigureApplocker.:

  <Application Name="PSMPrivateArkClientDispatcher" Type="Exe" SessionType="*" Path="C:\Program Files (x86)\CyberArk\PSM\Components\PSMPrivateArkClientDispatcher.exe" Method="Hash" />

 

  <Application Name="ArkUI" Type="Exe" Path="c:\Program Files (x86)\PrivateArk\Client\ARKUI.EXE" Method="Hash" />

 

@George Pickers​ 

I added PSMShadowUser group to ARKUI.exe.

But still continue.

 

If I execute "PSMPrivateArkClientDispatcher" directly, the similar error shows up.

Is it a normal behavior?

 

L0 Member

Hi kawamura-t,

 

Like @Nirmalkumar Dhanaraj​ suggested you should check your Windows Event Viewer > Application and Services Logs > Microsoft > Windows > AppLocker to verify Applocker is not blocking a related process for executing.

 

Additionally I would recommend checking the 'Event Viewer > Windows Logs > Application' or 'Event Viewer > Windows Logs >System' to see if there are any related events to the process failing.

 

Finally I would recommend you enable debugging on the PSM server as per the recommendations here: https://cyberarkdocu.azurewebsites.net/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASIMP/Configuring-Debug-Levels.htm?Highlight=PSM%20debug#h2-item-3

 

Then re-run the tests and verify if anything meaningful is added to the PSMTrace.log or the ThirdParty logs that may suggest the root cause.

 

Thanks,

George

 

 

L7 Applicator

Enable debug logging for PSM, restart your PSM service, run the connection component again, check logs in Logs/ThirdParty and PSMTrace.log.

 

https://cyberarkdocu.azurewebsites.net/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASIMP/Configuring-Debug-Levels.htm

  • 920 Views
  • 5 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!