- 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-16-2019 12:25 PM
problems using psm pool in load balancer:
Could not proceed with the connection because authentication is not enabled and the remote computer requires that authentication to be enabled before making the connection.
Could you tell me if pvwa was missing a parameter to configure?
I can post what I set up here if needed.
12-18-2019 04:12 AM
@Matt Jennison
Did you see something similar?
can you help?
12-18-2019 05:10 AM
Hey @Rafael Chagas
unfortunately I have never attempted to setup PSMs in a load balancer, but I have seen this error before doing other activities with PSM.
Based on the error being thrown it would seem one of these machines is not setup to allow RDP access or perhaps requires RDP over SSL. Does RDP work to each machine outside of Cyberark?
Do these connections require RDP over SSL?
there are a few articles related to this error that I would recommend you review and test:
https://community.cyberark.com/s/article/00003442
good luck!
-Matt
12-18-2019 06:43 AM
@Matt Jennison
It works normally.
Following are the error logs:
PSMCP038E Failed to set serialization. Reason: PSMCP119E Failed to receive a response from the PSM server. Reason: PSMCU015E Failed to receive the message over the channel. Reason: PSMCU012E Failed to read the message from the pipe server. Reason: PSMCU010E Failed to read from the pipe. Error Code: [109].
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 [0b8d5ed1-b5e0-4cb3-9fc4-9dfebdb91560] is being stopped because the Protocol Provider didn't run.
PSMIN136W An error occurred while handling the messaging server client. Error: PSMSR891E Failed to handle the session logon request. Diagnostic information: 1, Reason: PSMSR141E [5dbc52f5-d6ec-4254-a8f9-0fee6e33ae0d] Problem processing SessionTokenMessage xml message, Reason: PSMSR207E Secured parameters section is not present in the session token message (Extra information: 11100)
12-18-2019 06:52 AM
sounds like there is a block somewhere:
"PSMCP119E Failed to receive a response from the PSM server."
Maybe antivirus or a firewall is causing issues.
-Matt
12-18-2019 06:57 AM
@Matt Jennison
Strange that if I point to the individual psm it usually opens
12-18-2019 07:02 AM
ok, that's good! that means the problem can be narrowed down to the LB setup/LB itself.
-Matt
02-18-2020 02:32 PM
@Rafael Chagas Was there any resolution for this? I've rebuilt a PSM (same name, same IP) and I'm getting "PSMCP038E Failed to set serialization. Reason: PSMCP119E Failed to receive a response from the PSM server. Reason: PSMCU015E Failed to receive the message over the channel. Reason: PSMCU012E Failed to read the message from the pipe server. Reason: PSMCU010E Failed to read from the pipe. Error Code: [109]."
Haven't found any help so far in the forums.
02-18-2020 06:43 PM
@Eric Shafto ,
My problem I solved by opening a case in the support, we verified that there was a line in the pvconfiguration file that we changed. I believe that in your case it could be this file, if you wanted to expose it for us to take a look, I don't know if you could.
02-23-2020 11:33 PM
@Rafael Chagas May we know which line is related to give some hints on this 109 error?
Thanks.
12-27-2020 12:36 PM
@Rafael Chagas please specify which line. Having same error.
08-05-2022 04:18 AM
It should include PSMProtocolVersion 3 in your PVConfiguration.xml file found under PVWAconfig safe.
<PSMServer ID="PSMServer" Name="xxxxxxx" PSMProtocolVersion="3">
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!

