I need a solution for an intermittant reoccuring problem. The system cannot find the file specified. THe initial program cannot be started: PSM@xxxxxxx-xxxx-xxx

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

I need a solution for an intermittant reoccuring problem. The system cannot find the file specified. THe initial program cannot be started: PSM@xxxxxxx-xxxx-xxx

L0 Member

I have read all the article and I believe that all is as it should be...

 

These are the Windows Event logs (Application) on the PSM

 

Event ID 257 - Error

PSMPP098E Call to GetClientData in Protocol Connection failed. Reason: PSMPP071E Failed to receive RDS settings from PSM service. Reason: PSMCU015E Failed to receive the message over the channel. Reason: PSMCU012E Failed to read the message from the pipe server. Reason: PSMCU010E Failed to read from the pipe. Error Code: [109].

 

Event ID 257 - Error

PSMPP098E Call to NotifySessionId in Protocol Connection failed. Reason: PSMPP072E Failed to send the register session Id request. Reason: PSMCU013E Failed to send the message over the channel. Reason: PSMCU006E Failed to write the message to the pipe server. Reason: PSMCU008E Failed to write to the pipe. Error Code: [232].

 

Event ID 257 - Error

PSMPP098E Call to CreateVirtualChannel in Protocol Connection failed. Reason: PSMPP097E Call to CreateVirtualChannel of the wrapped Protocol Connection failed with code: 2147944165

 

Event ID 257 - Error

PSMCP038E Failed to set serialization. Reason: PSMCP119E Failed to receive a response from the PSM server. Reason: PSMCU015E Failed to receive the message over the channel. Reason: PSMCU012E Failed to read the message from the pipe server. Reason: PSMCU010E Failed to read from the pipe. Error Code: [109].

 

 

Event ID 257 - Warning

PSMIN136W An error occurred while handling the messaging server client. Error: PSMSR891E Failed to handle the session logon request. Diagnostic information: 2, Reason: PSMSR983E The session [101c15de-4e36-44ab-97e2-ce1bef833972] is being stopped because the Protocol Provider didn't run.

 

12 REPLIES 12

L2 Linker

Similar issue here, just started yesterday. Rebooted one of the PSMs, another is now displaying the same issue. Users are presented an "Audit server failure" and session is closed. Perseverance gets them in sometimes. Not all users are affected, some have connections active on the PSM

 

Field_Content_versions_oct20__068Ht00000QVO26IAH.png

L0 Member

All my users see is this...

​

Field_Content_versions_oct20__068Ht00000QVkjFIAT.png​

If I reboot the PSM the problem clears!!

I believe this might be something to to with envoking the process responsible for ingesting recordings?

​

Then after a random number of days it happens again.

The only observation to this pattern is that the error can occur more frequently over a 2 week period and then not happen at all for 3 weeks.😕

L0 Member

I am having the same issue specifically when use PSM Toad for Oracle

L4 Transporter

Bump!

 

L1 Bithead

Guys, the issue was resolved by applying the KB below;

https://community.cyberark.com/s/article/PSM-connection-fails-intermittently-after-migrating-PSMconnect-user-to-domain

 

We also double checked the whitelisting from Third Party Scanners, follow the KB below;

https://community.cyberark.com/s/article/What-files-and-folders-to-whitelist-from-Third-Party-Scanners-Agents-for-PSM

 

 

L2 Linker

Hi,

 

Maybe it is about hardening, you can run the PSM hardening script again.

 

best regards.

L2 Linker

Hi,

 

Maybe it is about hardening, you can run the PSM hardening script again.

 

best regards.

L7 Applicator

Some of this behaviour looks similar to

https://community.cyberark.com/s/article/PSM-needs-to-be-regularly-rebooted

 

Try implementing the ms patch and registry key, but on my site the problem isn't fully resolved by the patch.

Please dont forget to pay attention at PSMHardening.ps1 script line#98 and 99.

 

PSMConfigureAppLocker --->line#494 line#495

L2 Linker

In my experience this is usually caused by a combination of the following:

  • Some Domain Controllers have the "Network Access: Restrict clients allowed to make remote calls to SAM" set to only allow Administrators (the default on Domain Controllers is to allow Everyone (https://learn.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/network-access-restrict-clients-allowed-to-make-remote-sam-calls)
  • The PSM servers have the following Registry setting set:
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\IgnoreRegUserConfigErrors = 1

When PSM attempts to retrieve the user information (including Initial Program) from the domain controller, it fails due to not being allowed to access SAM, and because IgnoreRegUserConfigErrors is set, it fails silently, and insteads loads default settings, which does not include the Initial Program.

 

This may present as an intermittent issue if only a subset of domain controllers have the restriction, as it depends on where the PSM servers happens to try to retrieve the user configuration from.

L3 Networker

Similar to @Henning Botha​ 

For us it was missing some rights/assigment for the PSMConnect/PSMAdminConnect in the Local Computer Policy, no errors in the prereq/psm installation, nor hardening logs.

Local Computer Policy - Computer Configuration - Windows Settings - Security Settings - Local Policies - Security Options -

Network Access: Restrict clients allowed to make remote calls to SAM

right click -> properties -> edit security -> add PSMConnect and PSMAdminConnect

 

L3 Networker

Similar to @Henning Botha​ 

For us it was missing some rights/assigment for the PSMConnect/PSMAdminConnect in the Local Computer Policy, no errors in the prereq/psm installation, nor hardening logs.

Local Computer Policy - Computer Configuration - Windows Settings - Security Settings - Local Policies - Security Options -

Network Access: Restrict clients allowed to make remote calls to SAM

right click -> properties -> edit security -> add PSMConnect and PSMAdminConnect

 

  • 2842 Views
  • 12 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!