We are getting below error while establishing a connection from PSM. PSMIN136W, PSMSR891E , PSMSR983E

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

We are getting below error while establishing a connection from PSM. PSMIN136W, PSMSR891E , PSMSR983E

L4 Transporter

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 [93f7331d-7b22-4c1f-abb4-861bc898e0c3] is being stopped because the Protocol Provider didn't run.

 

We checked few KB articles as well but it didn't work. Pls suggest.

10 REPLIES 10

L4 Transporter

Hi,

 

From "Cyberark Messages and responses" official doc:

 

"PSMSR983E The session <SessionUniqueIdentifier> is being stopped because the Protocol Provider didn'trun. Recommended Action: Look for errors in the Event Viewer and contact CyberArk support. "

 

So, have you checked Event viewer? Any errors on it?

 

Regards

L3 Networker

@Sushant Chaturvedi​ May we know how to resolve the issue?

L3 Networker

Please let us know how to resolve this as we are also getting this error.

Hi Inaya,

 

Any errors on event viewer matching the error timeframe?

 

Regards

L1 Bithead

Anyone found the solution for this please?

 

L1 Bithead

Has anyone found a solution to this? We're running 11.2 and seeing the same error

"Protocol provider" refers to the Remote Desktop Services Session host on the PSM, in my experience. So re-check that you have the correct hardening settings applied (PSMConnect user, logon rights), re-check Remote App settings, and look for errors in the Windows event logs.

L1 Bithead

Old thread, but I'm still running 11.4 for reasons and when these errors occurred I just ran the PSM installer and did a repair. Just clicked through all the prompts with whatever was already in there. Worked fine after that.

L3 Networker

For us it was missing some rights/assignment 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

For us it was missing some rights/assignment 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

  • 3616 Views
  • 10 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!