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

L2 Linker

Do you have any impacted by this error? There was an open bug logged for this error: https://community.cyberark.com/s/article/KI00013494

L1 Bithead

These errors started appearing and impacting end users about 2 weeks ago. PSM reboot seemed to resolve things - but only temporarily because the issue has returned today.

L4 Transporter

@Roy Zhang​ I have this issue in one of my PSM , that not functioning (windows 2019 ) not sure whether this impact on the psm issue . Its a newly installed one and . any update about whether this impacts for the function of PSM ?

L4 Transporter

@Roy Zhang​ I have this issue in one of my PSM , that not functioning (windows 2019 ) not sure whether this impact on the psm issue . Its a newly installed one and . any update about whether this impacts for the function of PSM ?

L1 Bithead

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

L3 Networker

Having same issue in Privilege Cloud connector server.

Hi @Asanka Weerasinghe​ May I know, if you were able to resolve the issue. In our environment, out of 2 PSMs, only 1 psm is generating the error, while connecting to target server. Connections from other PSM servers are working fine.

Hi @Goutham C​  I could not get rid of this error message , But still I haven't had any related impact to PSM with this error . accourding to below artile there is no workaround for this error message yet .

 

https://community.cyberark.com/s/article/KI00013494

 

 

 

Issue Description

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

(Messages will be similar, but with different code number at the end)

There are many codes relating to this event that are defined as errors.

These errors do not impose any negative impact

 

 

 

 

Workaround---- >No Workaround was found

 

Hi @Goutham C​  I could not get rid of this error message , But still I haven't had any related impact to PSM with this error . accourding to below artile there is no workaround for this error message yet .

 

https://community.cyberark.com/s/article/KI00013494

 

 

 

Issue Description

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

(Messages will be similar, but with different code number at the end)

There are many codes relating to this event that are defined as errors.

These errors do not impose any negative impact

 

 

 

 

Workaround---- >No Workaround was found

 

@Goutham C​  are you experiencing any functional errors with this error log in your PSM ?

@Goutham C​  are you experiencing any functional errors with this error log in your PSM ?

Hi @Asanka Weerasinghe​ 

Connections from our PSM01 server are few servers are failing with RDP error code 4. But to the same servers, connections from PSM02 are working fine. In the event viewer, I found this error -( PSMPP098E Call to CreateVirtualChannel in Protocol Connection failed. Reason: PSMPP097E Call to CreateVirtualChannel of the wrapped Protocol Connection failed with code: 2416737906.) generated at the same time when connection failed.

L0 Member

having same issue on 2 out of 3 psms. these are cloud connectors. this happens with psm for aduc connector and displays when exiting the app

 

L1 Bithead

Hi, I'm getting same error and when this happens no new psm sessions could be established.

The other PSM server is working fine.

 

This error is followed bythose errors:

 

PSMSR126E [189e3742-6b76-4fae-82cf-b588f8d9941e] Failure occurred while handling session. PSMSR605E [189e3742-6b76-4fae-82cf-b588f8d9941e] Error occurred while waiting for the dispatcher to communicate (Error details: [PSMSR606E [189e3742-6b76-4fae-82cf-b588f8d9941e] Timeout occurred while waiting for a specific component to end]) (Codes: -1, -1)

 

and those:

 

Application: CyberArk.PSM.WebAppDispatcher.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.DllNotFoundException

  at PSMDispatcherUtilsManaged.PSMDispatcherUtilsWrapper._LogWrite(System.String, UInt32, Int32)

  at PSMDispatcherUtilsManaged.PSMDispatcherUtilsWrapper.LogWrite(System.String, Int32)

 

Exception Info: System.Exception

  at PSMDispatcherUtilsManaged.PSMDispatcherUtilsWrapper.LogWrite(System.String, Int32)

  at CyberArk.PSM.WebAppDispatcher.PsmWrapper.LogWrite(System.String, Int32)

  at CyberArk.PSM.WebAppDispatcher.PsmLogWriter.WriteLine(System.String, Int32)

  at CyberArk.PSM.WebAppDispatcher.ConnectionComponentController.Main(System.String[])

 

It seems there is a limit elsewhere for active sessions, because if I disconnect some active sessions it start working fine.

 

Anyone has any idea? There are any limitation?

 

Tks

  • 11893 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!