PSM Session fails with error - "The exception unknown software exception (0xe0434352) occurred in the application at location 0x0*******"

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 Session fails with error - "The exception unknown software exception (0xe0434352) occurred in the application at location 0x0*******"

L2 Linker

Field_Content_versions_oct20__068Vy00001BiVMDIA3.pngHi Experts,

 

We’re facing an issue on one of our CyberArk PSM servers where sessions fail to initiate. We have two PSM servers behind a load balancer, and the problem is isolated to only one node.

 

The PSM solution was implemented 8–9 months ago and had been functioning without issues until around 15 days ago.

 

For additional context, we are currently developing Web Application connection components for SaaS applications. As part of this activity, several new tools (browsers, drivers, etc.) were installed on the PSM servers, and AppLocker policies were updated and re-applied multiple times.

We have already attempted the following without success:

  • Restarting the affected PSM server
  • Clearing and re-running AppLocker rules
  • Rebuilding and re-hardening the PSM server

At this point, we’re trying to understand what could cause this issue to affect only one PSM server and what additional areas we should investigate.

 

Any insights or suggestions would be greatly appreciated.

 

1 accepted solution

Accepted Solutions

In addition to what @Robert Stothard​ suggested, you can try to use the 32-bit dispatcher version instead, you'll need to change the {PSMComponentsFolder} placeholder for that component to point to the 32-bit folder -> {PSMComponentsFolder32} in the Connection Component:

 

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

View solution in original post

5 REPLIES 5

L7 Applicator

That Windows dialog usually means an unhandled .NET exception occurred during the PSM logon flow (the code

0xE0434352

is the CLR “managed exception” marker).

 

 

.NET Framework 4.8 installed and healthy

PSM requires .NET 4.8; missing or corrupted .NET often yields 0xE0434352 .

Validate in Programs & Features or reg query and repair if needed.

 

RDS Session Host role present & licensing OK

Ensure the Remote Desktop Services (RDS) Session Host is installed and licensed (per‑device for local users on 2019/2022) per docs; broken RDS can crash RemoteApp launchers (like PSMInitSession.exe)

 

Hardening/AppLocker not blocking a needed binary

AppLocker rules must allow all PSM components and any client dispatchers (SSMS, toad, browsers, etc.). Review

PSMConfigureAppLocker.xml and the AppLocker logs when the crash occurs. Re‑run hardening if you’ve changed users or enabled Web Apps.

 

PSM service state

Confirm CyberArk Privileged Session Manager service is running; some errors are only in Event Log, and service stoppage/auto‑restarts can present as a user‑facing crash.

 

In addition to what @Robert Stothard​ suggested, you can try to use the 32-bit dispatcher version instead, you'll need to change the {PSMComponentsFolder} placeholder for that component to point to the 32-bit folder -> {PSMComponentsFolder32} in the Connection Component:

 

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

Thank you @Patrick Booth​.

 

Changing the PSMComponentFolder to 32-bit has resolved the issue - we are now able to access the Web App dispatcher as expected.

However, can you give further clarity on what caused it to throw the error? And what is a fix to make it work also with 64-bit. We have 3 PSM servers in our environment and we need to keep the configuration consistent across all components. The other 2 are working fine with 64-bit configuration.

L0 Member

I have the same issue after upgrade to 14.8 and Changing the PSMComponentFolder to 32-bit has resolved the issue, but I think is there is possibly bug with the x64 files.

Has anyone been able to identify the cause?

L1 Bithead

Have not determined cause but have been able to fix things via repair of the Visual C++ Redistribubles (Latest supported v14). Did not have to restart when prompted.

 

Most recently this issue recurred after the CyberArk Management Agent updated itself.

 

 

  • 1 accepted solution
  • 260 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!