- 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.
12-12-2019 04:08 AM
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.
12-12-2019 05:41 AM
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
12-22-2019 12:23 AM
@Sushant Chaturvedi May we know how to resolve the issue?
01-28-2020 05:05 AM
Please let us know how to resolve this as we are also getting this error.
01-28-2020 05:13 AM
Hi Inaya,
Any errors on event viewer matching the error timeframe?
Regards
03-10-2020 10:43 PM
Anyone found the solution for this please?
11-22-2021 11:30 AM
Has anyone found a solution to this? We're running 11.2 and seeing the same error
11-22-2021 02:24 PM
"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.
02-09-2025 07:06 PM
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.
07-22-2025 01:49 AM
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
07-22-2025 01:49 AM
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
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!

