Log in stuck at "Authenticate" stage - CreateNamedPipe 231 error

[JonasBertels]

Hello,

At my current client, we are facing some annoying issues with some new VDIs we are setting up.

The VDI seems to be set up and ready to go and it in fact is able to do actions like 'Login', 'Logout' from the Login Agent. It can also run processes as expected.

However, the problems begin when we are logging out after being logged in. If we stay logged out for more than half an hour, when we try to login again, we cannot. When we try to log in at that point, we get stuck at the "Authenticate" code stage (in the object 'Authenticate to windows' in the login process).

It will not log in, we cannot do 'immediate stop' & only by logging in manually and then either signing out do we fix this issue. However, when we wait 30 again after this sign out, the same issue happens all over again.

I have added the logs of Blue Prism when it can't authenticate in attachment. As you can see it keeps on getting the error "BluePrismProvider.cpp(212): CreateNamedPipe failed: 231".

Does anyone have an idea how to solve this? Is this BluePrism related, VDI related, or something else?

As a last remark, note that when the VDI is restarted, exceeding this 30 min window doesn't seem to cause the same issues, so it seems there is a difference between a restarded, fresh vdi and one that is already logged in once.

Thanks for the help!

Kind regards,

Jonas
RPA Consultant


------------------------------
Jonas Bertels
RPA Consultant
BrightKnight
Europe/Brussels
------------------------------

[JerinJose]

​Please check if the ALT+CLRL+DEL Secure attention key for initiating login is disabled on the VMs for if you are using  BP version prior to 6.6

------------------------------
Jerin Jose
RPA Product SME
EY
Asia/Kolkata
------------------------------

[benny.poumoko-bafouatika]

HI Jonas

Are you using Remote desktop connection by any chance?

------------------------------
[Benny Poumoko-Bafouatika]
[Customer Support Analyst]
[Blueprism]
------------------------------

[DanielMurray]

Hi jonas,

We have been having the same issue for a while now, What version of Blue Prism Login Agent are you using. We are experiencing this on v6.4. However, when we run version 6.2.2 it works. Going through the release notes of the login agent, Blue Prism made some changes in the way they use Named Pipes in version 6.3 which may explain why it works with the 6.2.2 login agent for us. We are considering trying the 6.5 or 6.6 login agent see if this resolves the issue.

So far we haven't worked out what is causing the issue, still investigatin.

------------------------------
Daniel Murray
Solution Architect
DXC
Europe/London
------------------------------

[DanielMurray]

Hi Jonas,

Have you managed to fix this yet?

We still having this issue, one thing to note is we run hardened builds hardened to the CIS benchmarks, do you harden your builds? I am thinking it may be some GPOs are impacting the login agent?


------------------------------
Daniel Murray
Solution Architect
DXC
Europe/London
------------------------------

[JonasBertels]

Hi all,

A small summary of the status of this issue:
- We have all group policies and screen locks/CTRL+ALT+DEL formatted correctly. They do not form the issue
- We are using a Citrix SSon
When removing the Login agent 6.5 and downgrade this agent to version 6.2.2., it does seem to work as well. We are figuring out this issue together with an expert from BluePrism to see what the exact issue might be and how to proceed avoiding this issue. But for now, it seems a combination of V6.5 BP with V6.2.2. Login agent seems to do the trick.

------------------------------
Jonas Bertels
RPA Consultant
BrightKnight
Europe/Brussels
------------------------------

[DanielMurray]

Thanks for the update, we are also working with BP and will keep you informed if we find anything

------------------------------
Daniel Murray
Solution Architect
DXC
Europe/London
------------------------------

[NabinTimalsina]

Hello, 

Any Update on this?

------------------------------
Nabin Timalsina
Infrastructure Engineer
------------------------------

[DanielMurray]

BP stil working on it as far as I am aware, at our end. All I know is it is defintly something to do with the GPO settings, as it works on our un-harden build, when we apply the CIS level 1 benchmark, it starts to fail.

------------------------------
Daniel Murray
Solution Architect
DXC
Europe/London
------------------------------

[PetriKaukua]

We have same issue, no fix from BP yet. LoginAgent process gets stuck to Authenticate stage randomly and LoginAgent log is filled with the following information:

TSS(Local) 8: ERROR BluePrismProvider.cpp(212): CreateNamedPipe failed: 231
TSS(Local) 8: ERROR BluePrismProvider.cpp(100): Failed to create named pipe. retrying.... - 183

This is claimed to be fixed with 6.6 and later but we still see this issue happening on 6.6, 6.7.2 and in 6.8, Windows 10 versions 180x and 190x.
No security hardening in our case.

------------------------------
Petri Kaukua
Certified Blue Prism Architect
Digital Workforce
Europe/Helsinki
------------------------------