topic Login Agent not working when the Windows account is logged out in Product Forum

Login Agent not working when the Windows account is logged out

KateKryvenko — Fri, 30 Jul 2021 13:21:52 GMT

Hi,

We are having an issue with the Login Agent on the Runtime Resource on our client's environment . BluePrism version 6.10.1

First, I will describe how the Runtime Resource was set up:
We installed the BluePrism client on the Runtime, connected it to the BluePrism server. Everything worked perfectly fine. After that we installed the Login Agent from the "C:/Program Files/Blue Prism Limited/BluePrism Automate/Intallers" (so the version of the LoginAgent should be correct). While installing the Login Agent, we specified the correct connection name (the one we connected with to the BP Server). After that the windows service for the Login Agent was successfully created and started running without issues.

Also, we have set up all the required Security Policy (Ctrl+Alt+Del, On-screen pre-login message, Display lock screen). After that the .bat file was added to the Windows StartUp folder with Automate.exe /resource /public command. It's also working, as when we connect to the Runtime Machine through RDP, the Listener starts and connection to the BP server is created successfully. After that the machine in Control Room is showing in state 'Idle'.

But the issue appears when we run the 'Logout' or 'Restart Machine' processes. After that machine goes to 'Offline' state and it never appears in 'Logged Out' state.

The event viewer is showing the following warnings (it shows only when machine is in Logged Out state, not when it's working unders the account):

We have tried everything so far. So, I would really appreciate any help 🙂

Re: Login Agent not working when the Windows account is logged out

krishna.kodimurali9 — Mon, 02 Aug 2021 11:51:59 GMT

Seems an issue with the Login agent configuration, as you have mentioned all other things seem perfect.
Can you try reconfiguring the login agent?

Re: Login Agent not working when the Windows account is logged out

KateKryvenko — Mon, 02 Aug 2021 13:11:25 GMT

Hi,

Actually, we have already tried both reconfiguring & reinstalling the Login Agent. Is there anything we should pay attention to besides Connection Name when installing the Login Agent.

Now LoginAgentService.config looks like this. Our connection name to the BluePrism Server is called 'Default'.

<?xml version="1.0" encoding="utf-8"?>

<configuration>

<workingdirectory path="C:\Program Files\Blue Prism Limited\Blue Prism Automate\"/>

<startuparguments>

<argument name="resourcepc"/>

<argument name="public"/>

<argument name="port">

<value>8181</value>

</argument>

<argument name="dbconname">

<value>Default</value>

</argument>

</startuparguments>

</configuration>

Re: Login Agent not working when the Windows account is logged out

ritansh.jatwani — Mon, 02 Aug 2021 13:17:27 GMT

Hi @KateKryvenko,

Did you start the listener or configured the listener to start automatically once the bot logins to the machine?
It can be achieved either by placing the batch script (containing the command to run listener) in the start up folder or by creating a windows task scheduler.

Re: Login Agent not working when the Windows account is logged out

KateKryvenko — Mon, 02 Aug 2021 13:26:51 GMT

Hi @ritansh.jatwani,

Yes, we do start the Listener from the batch file, and it's working without issues. The issue is that when the Windows user logs out, the machine does not appear in the state 'Logged out' and the LoginAgentService is throwing the errors that you can see above on the screenshots.

Re: Login Agent not working when the Windows account is logged out

ritansh.jatwani — Mon, 02 Aug 2021 16:08:19 GMT

Hi @KateKryvenko,

Does that mean logging out is working fine but after logging off, the machine doesn't come to logged out state?
I also recently setup the login agent for a client. I also faced the similiar issues.
When you placed the batch file in startup folder, it will be placed in the startup folder of a user specific account. Do you have multiple user accounts to login to the same machine?
I would prefer creating a windows task scheduler to trigger the listener file rather than placing the file at startup folder to accomodate as many users as possible.

Re: Login Agent not working when the Windows account is logged out

krishna.kodimurali9 — Tue, 03 Aug 2021 06:28:34 GMT

Helo Kate,

Please try changing the Port to 8182,8189 etc.. in the config file.
post that it should appear with an updated VM name with the port as a suffix.

Re: Login Agent not working when the Windows account is logged out

JerinJose — Tue, 03 Aug 2021 07:08:37 GMT

Hi Kate,

Issue is with currupted user.config file. This file stores your last established connection details. here is what you could do.
1.Delete user.config file
2.Relogin to Blueprism interactive client (to default bpserver connection) this will recreate user.config
3.close Blueprism and restart machine
4.when the runtime resource shows connected using login agent run the Login process
5.Login might take 1-2 mints depending on the number of applications in startup folder. once machine shows connected in control room through the public runtime resource launched from the batch script execute the logout process. machine should appear online again in less than one minute connected through login agent service

Re: Login Agent not working when the Windows account is logged out

JerinJose — Tue, 03 Aug 2021 07:16:49 GMT

@ritansh.jatwani

you can place the startup file in Common startup (Shell:common startup) so that the runtime resource launching will not be user profile dependent

Re: Login Agent not working when the Windows account is logged out

IsmoLehtiniemi — Tue, 03 Aug 2021 09:50:42 GMT

If none of the other suggestions help you to resolve the issue, you could try enabling anonymous public Runtime Resources from the System -tab:

Re: Login Agent not working when the Windows account is logged out

KateKryvenko — Wed, 04 Aug 2021 15:46:34 GMT

Hi @JerinJose,

We tried this approach, but after deleting the User.config and then relogging into the interactive client, the User.config was not recreated,

Maybe you know what can possibly prevent this config file from being created?

Re: Login Agent not working when the Windows account is logged out

JerinJose — Thu, 05 Aug 2021 06:44:45 GMT

Hi Kate,

if the user config is not created there are some permission issues. launch interactive client with elevated privilege's (as administrator) and see if the file is getting created.
Also is your login agent running under Local System logon? or any specific account? if its running under different account change logon to local system account and try after restarting the login agent service.

Re: Login Agent not working when the Windows account is logged out

JerinJose — Thu, 05 Aug 2021 06:54:14 GMT

and the location of the User.Config surprises me. usually it get created in "C:\Users\XXXXXXXX\AppData\Roaming\Blue Prism Limited\Automate V3" in your case it got created in a privilaged folder which normal user account cant access. may be whole issue lies there.

I'm starting to get an impression that you should raise a support ticket with blueprism team to do an analysis of your installation. community wont be able to help here much without seeing how your set it up i guess.

Re: Login Agent not working when the Windows account is logged out

TelmoSantos — Fri, 29 Oct 2021 15:54:09 GMT

Hi Kate,
I also ran into this issue. In our case, when the logout was performed, windows did not have enough time to release port 8181, that was occupied by the runtime started by the batch file in the startup folder.
We increased the Logout Delay variable on the Logout process to 15 secs and it is now ok.

We also had the same issue while logging in, when the batch file kicked in the port wasn't released in time, but Automate.exe already has a control for this, to try again after 2 minutes.
We ended up putting a timeout (pause in batch files) of 15 secs before starting the runtime to allow sometime for the port to be released.