Can't authenticate using Login Agent

[JoséMaurício_de]

Good afternoon,

Have any of you ever experienced an error of timeout when trying to login using Login Agent?

I've told the company about the policies required and after those were applied, I cannot perform a login because the authenticate stage exceeds the timeout. Already tried with a timeout uo to 10minutes, unsuccessfully.

Can anyone help me?

Thanks

------------------------------
José Maurí­cio de Carvalho
Consultant
EY
------------------------------

[AmiBarrett]

I've seen this before on systems which were previously connected to via RDP. RDP will unfortunately break Login Agent, due to the type of session that is active on the system.

You can either get around this by connecting to the box using an alternate method (I highly recommend TeamViewer, but there's also VNC), or using a script to force the session back to desktop on RDP disconnect via scheduled task. I'm attaching a batch file as a .txt file to assist with this. Please note that this must be run with elevated permissions. If it causes issues, you can RDP in as any other user and disable the scheduled task that triggers it.

------------------------------
Ami Barrett
Lead RPA Software Developer
Solai & Cameron
------------------------------

[PeterTarrant]

Also, according to this article on the support site, there were network communication improvements in 6.3.2 and in 6.4 that were supposed to mitigate this issue.

https://portal.blueprism.com/customer-support/support-center#/path/Automation-Design/Login-Agent-Automation-Design/1141034952/Why-do-I-get-Error-The-operation-has-timed-out-when-using-Login-Agent.htm​

------------------------------
Peter Tarrant
Blue Prism Operations Specialist
Agilify
------------------------------

[AjayGhodke1]

Hi Peter,

When using login agent have you modified necessary settings on VM. Like Enabling "Do not require ctrl + alt + del", any message should not be displayed while logging into machine. These settings are given in guide for Login Agent by BP. When you don't modify these setting then you get this error. We use RDP and login agent it works fine.

------------------------------
Ajay Ghodke
Associate Consultant
wipro
Europe/London
------------------------------

[PeterTarrant]

Of course. All of those settings are applied. These timeouts in earlier versions occurred intermittently. It would fail once with a timeout and then succeed the next time it was run 5 minutes later, with no changes being made. The support article refers to Login Agent timing out when all other things were done correctly from a configuration standpoint.​

------------------------------
Peter Tarrant
Blue Prism Operations Specialist
Agilify
America/Detroit
------------------------------

[JesperHededam1]

We seem to be experiencing the same. Windows 10. We experience that half of the VDIs daily fail to login due to Login Agent getting timeout errors.

------------------------------
Jesper Hededam
Developer
Codan
Europe/Copenhagen
------------------------------

[MikeWright2]

Hi Jesper,

Did you manage to resolve this issue in Win10?  Having same problem.


Thanks,

Mike

------------------------------
Mike Wright
Delivery Manager
Fonterra
Europe/London
------------------------------

[JesperHededam1]

Hi Mike.

Yes, we actually resolved our issue. The issue was due to our VDIs (VMs) having been migrated from Windows 8 to 10 rather than having been given a clean Windows 10 install by our server team.

What happened was that upon restart of our VDIs the LogonUI.exe thread which is present when at the login screen, was being duplicated over and over again on the VDIs, so ever few minutes a new thread would popup, leaving after a short while, tens if not hundreds of copies of the LogonUI.exe thread.
This in turn made it impossible for Blue Prism to attach and interface with the "correct" thread of LogonUI.exe. But that was not all really, since a "true" LogonUI.exe thread consumes around 10-30 Mb of memory, these fake ones only consumed on the order of 400-800 Kb of memory. So something was fundamentally broken in the LogonUI.exe thread. Funny thing though, doing a RDP to one of the VDIs would login the machine correctly for some reason.

Reinstalling Windows 10 from scratch fixed this issue, and this fixed our LoginAgent issues. Your issue may of course be different, but this is what happened in our case.


Best regards,
Jesper

------------------------------
Jesper Hededam
Developer
Codan
Europe/Copenhagen
------------------------------

[PSSupport]

Most likely you are executing the Runtime Resource automate.exe script configured to run at login through the Task Scheduler. 


Regards, 


------------------------------
PS Support
PS Support Account for all of Professional Services
Blue Prism
Europe/London
------------------------------