- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
03-11-2024 02:26 PM
Hello , We are on version 14.0 PSM and everything was working fine till yesterday. Today we observed that CAPSM.exe is crashing every time we initiate any connection. Whether it's RDP,WinScp, Web connection etc. I observed that Windows Team installed few KB's and found one KB5033910 and it's related to .Net4.8 & We searched on google & found that few people also suggested that other apps were crashed after applying this KB.
Just wanted to cross check - is KB5033910 really a culprit in our case?
We reset credential file and did all type of basic troubleshooting but no luck, someone suggested in previous KB of CyberArk <PSM Service crashed> to comment API address, we also did that but no luck. Before going for repair, we would like to check whether KB is causing an issue, we can try to uninstall the KB and check again or only repair is the option??
"Event Viewer Logs" -
PSMPP098E Call to PreDisconnect in Protocol Connection failed. Reason: PSMPP136E Failed to send request. Reason: PSMCU014E Failed to connect to the messaging channel. Reason: PSMCU003E Failed to connect to the named pipe server. Reason: PSMCU004E Failed to open the pipe. Error Code: [2].
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: CAPSM.exe
P2: 14.0.0.30
P3: 6578b431
P4: VCRUNTIME140.dll
P5: 14.32.31332.0
P6: 4fbfc837
P7: c0000005
P8: 0000341e
P9:
P10:
Faulting application name: CAPSM.exe, version: 14.0.0.30, time stamp: 0x6578b431
Faulting module name: VCRUNTIME140.dll, version: 14.32.31332.0, time stamp: 0x4fbfc837
Exception code: 0xc0000005
Fault offset: 0x0000341e
Faulting process id: 0x2584
Faulting application start time: 0x01da73f99d558d91
Faulting application path: C:\Program Files (x86)\CyberArk\PSM\CAPSM.exe
Faulting module path: C:\windows\SYSTEM32\VCRUNTIME140.dll
Report Id: efbf6c6e-0b41-4469-9557-a5a008ce4531
Faulting package full name:
Faulting package-relative application ID:
03-26-2024 09:08 AM
Of course no guarantees, its my opinon, not official solution.
03-26-2024 09:36 AM
And im also posting XML file to import scheduled task, it has xpath filter for the specific event.
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
<RegistrationInfo>
<Date>2024-03-26T17:20:20.2373551</Date>
<Author>DOMAIN\user</Author>
<Description>workaround for issue 000035089 until its fixed by cyberark</Description>
<URI>Cyberark Fix 000035089</URI>
</RegistrationInfo>
<Triggers>
<EventTrigger>
<Enabled>true</Enabled>
<Subscription><QueryList><Query Id="0" Path="Application"><Select Path="Application">
*[System[Provider[@Name='Application Error'] and (EventID=1000)]]
and
*[EventData[Data and (Data='CAPSM.exe')]]
and
*[EventData[Data and (Data='C:\Program Files (x86)\CyberArk\PSM\CAPSM.exe')]]
and
*[EventData[Data and (Data='C:\Windows\SYSTEM32\VCRUNTIME140.dll')]]
</Select></Query></QueryList></Subscription>
</EventTrigger>
</Triggers>
<Principals>
<Principal id="Author">
<UserId>S-1-5-18</UserId>
<RunLevel>HighestAvailable</RunLevel>
</Principal>
</Principals>
<Settings>
<MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
<AllowHardTerminate>true</AllowHardTerminate>
<StartWhenAvailable>false</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<IdleSettings>
<StopOnIdleEnd>true</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>PT1H</ExecutionTimeLimit>
<Priority>7</Priority>
</Settings>
<Actions Context="Author">
<Exec>
<Command>powershell.exe</Command>
<Arguments>-File C:\scripts\cya-fix-000035089.ps1</Arguments>
</Exec>
</Actions>
</Task>
03-26-2024 09:36 AM
And im also posting XML file to import scheduled task, it has xpath filter for the specific event.
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
<RegistrationInfo>
<Date>2024-03-26T17:20:20.2373551</Date>
<Author>DOMAIN\user</Author>
<Description>workaround for issue 000035089 until its fixed by cyberark</Description>
<URI>Cyberark Fix 000035089</URI>
</RegistrationInfo>
<Triggers>
<EventTrigger>
<Enabled>true</Enabled>
<Subscription><QueryList><Query Id="0" Path="Application"><Select Path="Application">
*[System[Provider[@Name='Application Error'] and (EventID=1000)]]
and
*[EventData[Data and (Data='CAPSM.exe')]]
and
*[EventData[Data and (Data='C:\Program Files (x86)\CyberArk\PSM\CAPSM.exe')]]
and
*[EventData[Data and (Data='C:\Windows\SYSTEM32\VCRUNTIME140.dll')]]
</Select></Query></QueryList></Subscription>
</EventTrigger>
</Triggers>
<Principals>
<Principal id="Author">
<UserId>S-1-5-18</UserId>
<RunLevel>HighestAvailable</RunLevel>
</Principal>
</Principals>
<Settings>
<MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
<AllowHardTerminate>true</AllowHardTerminate>
<StartWhenAvailable>false</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<IdleSettings>
<StopOnIdleEnd>true</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>PT1H</ExecutionTimeLimit>
<Priority>7</Priority>
</Settings>
<Actions Context="Author">
<Exec>
<Command>powershell.exe</Command>
<Arguments>-File C:\scripts\cya-fix-000035089.ps1</Arguments>
</Exec>
</Actions>
</Task>
03-26-2024 09:36 AM
And im also posting XML file to import scheduled task, it has xpath filter for the specific event.
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
<RegistrationInfo>
<Date>2024-03-26T17:20:20.2373551</Date>
<Author>DOMAIN\user</Author>
<Description>workaround for issue 000035089 until its fixed by cyberark</Description>
<URI>Cyberark Fix 000035089</URI>
</RegistrationInfo>
<Triggers>
<EventTrigger>
<Enabled>true</Enabled>
<Subscription><QueryList><Query Id="0" Path="Application"><Select Path="Application">
*[System[Provider[@Name='Application Error'] and (EventID=1000)]]
and
*[EventData[Data and (Data='CAPSM.exe')]]
and
*[EventData[Data and (Data='C:\Program Files (x86)\CyberArk\PSM\CAPSM.exe')]]
and
*[EventData[Data and (Data='C:\Windows\SYSTEM32\VCRUNTIME140.dll')]]
</Select></Query></QueryList></Subscription>
</EventTrigger>
</Triggers>
<Principals>
<Principal id="Author">
<UserId>S-1-5-18</UserId>
<RunLevel>HighestAvailable</RunLevel>
</Principal>
</Principals>
<Settings>
<MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
<AllowHardTerminate>true</AllowHardTerminate>
<StartWhenAvailable>false</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<IdleSettings>
<StopOnIdleEnd>true</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>PT1H</ExecutionTimeLimit>
<Priority>7</Priority>
</Settings>
<Actions Context="Author">
<Exec>
<Command>powershell.exe</Command>
<Arguments>-File C:\scripts\cya-fix-000035089.ps1</Arguments>
</Exec>
</Actions>
</Task>
04-02-2024 11:02 PM
Thanks for script @Michal Masek?. Now I can see issue is fixed in new release 14.0.1 - Article Detail (site.com)
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!

