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

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

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

L1 Bithead
29 REPLIES 29

Hi @Goutham C​ did yo by any chance fixed the issue?

Hi @Goutham C​ did yo by any chance fixed the issue?

L0 Member

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?

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?

L2 Linker

Was anyone able to find a solution to this issue? Reboot fixes the issue temporarily.

L1 Bithead

The issue still exists. Is there any workaround yet?

The same issue here

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.

L3 Networker

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?

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

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.

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?

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

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

  1. Local Groups are exactly the same
  2. Domain Groups are exactly the same
  3. File ACL are exactly the same
  4. All files are present.

 

The connectors worked fine before hardening, but both have ran hardening script. The server that's the issue works randomly at best..

L1 Bithead

Hallo dear, I have the same issue, please help us if anyone know how to resolve this issue.

  • 11967 Views
  • 29 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!