PSM Web to access https://portal.azure.com does not work anymore

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

PSM Web to access https://portal.azure.com does not work anymore

L3 Networker

Hi,

 

we are getting the following error with one PSM Web App we published to access https://portal.azure.com using Microsoft Edge 64 bits.

 

[14/04/2026 | 11:10:48] | :: | PSMSR126E [06f281ff-45cc-416d-a473-55fc3133ca67] Failure occurred while handling session. PSMSR605E [06f281ff-45cc-416d-a473-55fc3133ca67] Error occurred while waiting for the dispatcher to communicate (Error details: [PSMSR282E One of the session components has failed and therefore the session will be closed. For further assistance, contact your system administrator. More info: Process [Client dispatcher] has failed. Session [06f281ff-45cc-416d-a473-55fc3133ca67].]) (Codes: -1, -1)

 

What we did on the PSM.

a) Run PSM checker all green

b) Edge version and Edge driver are the same

 

13/04/2026 | 09:05:14] | :: | PSMSR035I Privileged Session Manager version [14.9.0.10] is up

 

Any thoughts?

 

How can we better debug such PSM Web App that I found very sensitive?

 

 

3 REPLIES 3

L5 Sessionator

Hey @Diego Pessotto​ Make sure the 64bit edge driver is located in the PSM\Components\x64\ path. Also, try switching the ClientDispatcher path to use the 32-bit dispatcher by replacing {PSMComponentFolder} with {PSMComponentFolder32} on the connection component:

 

https://docs.cyberark.com/privilege-cloud-shared-services/latest/en/content/pasimp/psm_webapplication.htm

L1 Bithead

Hi @Diego Pessotto​ 

Give this a try!!

 

Download the WebAppdispatcher from Marketplace and copying the All the files from components folder of WebAppDispather to C:\Program Files (x86)\CyberArk\PSM\Components path and adding the EnableProtocolProviderLogging=Yes in basic_psm file and rerun the PSM check and fix web app issues 

 

Client Dispatcher is Set to "{PSMComponentsFolder}\CyberArk.PSM.WebAppDispatcher.exe" "{PSMComponentsFolder}" in default PSM-MS-AzurePortal in connection component

 

Field_Content_versions_oct20__068Vy00001LJtsGIAT.png 

Above steps worked for me

L4 Transporter

Hi @Diego Pessotto​ 

Two of our community members have shared answers to your question. Could you let us know if any of these resolved your issue?

If so, please mark the appropriate answer as “Select as Best” to help other members find the solution easily.

If the issue remains unresolved, I recommend submitting a ticket with our support team for further assistance.

Thank you,

Shaked

  • 84 Views
  • 3 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!