- 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.
08-08-2022 03:20 AM
10-10-2024 02:47 AM
Hi @Goutham C did yo by any chance fixed the issue?
10-10-2024 02:47 AM
Hi @Goutham C did yo by any chance fixed the issue?
02-18-2025 07:24 AM
I have the same issue on one of our servers. Was hoping that there was a fix rather than a restart to "address" the current problem. New sessions are not allowed so there is an impact but it appears that existing sessions are still connected. I had to change the PSM connection settings on the platforms assigned to get users working again. A load balancer wouldn't help keep things moving along for my users.
Is there a case logged on this that CyberArk has in view?
02-25-2025 04:22 AM
I am trying to integrate PSM-ADUC connector, and when I try to initiate session, I get message that says 'Initializing', a little pop up 'You are being recorded'....and then suddenly the session logs off and window disappears.
Interestingly, there is nothing worthwhile in Component logs, Console logs or Trace logs...but in event however, I see this event - 'PSMPP097E Call to CreateVirtualChannel of the wrapped Protocol Connection failed with code: 2147944165'
Anyone got stuck in same situation here?
03-04-2025 05:46 AM
Was anyone able to find a solution to this issue? Reboot fixes the issue temporarily.
03-10-2025 08:32 AM
The issue still exists. Is there any workaround yet?
07-07-2025 02:35 PM
I am having a similar issue. It only affects one of PSM connectors, however. The others work without issue. Everything about the PSM servers seem to be the same.
12-31-2025 01:47 AM
Hello @Roy Zhang @Matt Jennison - Do we have any update on this article - KI#00013494: Unnecessary error messages from protocol provider thrown in the event viewer - KI#00013494: Unnecessary error messages from protocol provider thrown in the event viewer
It seems there is no workaround & I checked many people faced this problem reported this issue and today it's also started in our environment too. Can you pls provide an update on this?
01-05-2026 07:31 AM
hey @NET LUX
What version are you using? also, what specific issue do you see? Is it just an error message showing but no problems occurring?
Also, have you opened a Support Case for this yet? this is important for any known issues so that R&D can better prioritize them.
-Matt
01-07-2026 07:31 PM
Hi @Matt Jennison - We are on Version 14.0 , and yes it interrupted PSM service during business peak time and disconnected all PSM sessions. ( it happened only on one PSM server out of 6)
We didn't opened a case yet & restart a PSM service did work but we were surprised to see that no workaround is available for this situation.
02-25-2026 04:52 AM
Hello @Matt Jennison - Any news on this? Today we also got the same message and it interrupted our SQL Developer dispatcher. It's very weird that SQL is working fine on other PSM Server. We have same applocker settings, same config file and we didn't change anything and only 1 PSM server is throwing this error and it broke SQL developer connection. We are on 14.0 - Do you have any work around?
02-25-2026 06:00 AM
Hey @NET LUX
Were you able to open a case for this? This is not something I have direct visibility into, but I would recommend working with R&D on this as it may be a known issue. Also, as this is an intermittent issue, I have bene unable to reproduce it myself.
If a restart of the PSM is what fixed it previously I would consider that a workaround, but definitely not an ideal one as it is very disruptive to service. R&D may have better options here.
-Matt
03-19-2026 09:22 AM
Hi, we are getting this issue on PSM version 15, one PSM works one PSM doesn't. Were you ever able to resolve this?
Things I checked
The connectors worked fine before hardening, but both have ran hardening script. The server that's the issue works randomly at best..
06-25-2026 11:33 PM
Hallo dear, I have the same issue, please help us if anyone know how to resolve this issue.
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!

