06-08-24 04:59 PM
Hello, I am reaching out for some assistance with the Login Agent. I have read a lot of pages on this and tried everything I can think of but I cannot resolve this issue.
I have 13 Remote workers and 12 of them are working with the Login agent, 1 of them does not.
The machine has a status of Logged Out and has the Key icon so it is ready to be logged in.
I have configured the Credentials in the same way as I have in the other 12 environments (also recently removed and recreated to make sure correct)
I have Environment Variable for the Windows Login set on all control and remote workers.
I have exported the local security policy (gpedit.msc) from a working worker to this worker and compared in notepad++ - they are identical. For clarification I have set the Interactive Logon: Do not Require CTRL + ALT + DEL = Enabled
This is all that is required on other machines. We do not have any other message text enabled. I have also recently also Enabled the Don’t display last signed-in and Don’t display username at sign-in
Restarted the Worker after changes before retesting.
I have compared the config for the Login Agent Service and that is the same in both.
We do not send SAS to simplify this.
I read about enabling logs by setting the registry to do this – HKEY_LOCAL_MACHINE\SOFTWARE\Blue Prism Limited\LoginAgent
I set the LogLevel to 7 as indicated this would provide all logs. However in the location specified in LogFileDir nothing is available.
I did look in the normal log location - …\Blue Prism Limited\Blue Prism\Logs\ and checked the timestamp - ResourcePC-LoginAgent_log.txt seems to be updating. However, I do manually log on to server after failed logon with BP to check this file.
2024-08-06 16:58:58.1312+02:00 vStoMhBp14-1 INFO BluePrism.AutomateAppCore.TcpListener processid=6024 thd=13 Listener started.
2024-08-06 16:59:57.7982+02:00 vStoMhBp14-1 INFO BluePrism.AutomateAppCore.Resources.ResourceRunnerBase processid=6024 thd=5 [2024-08-06 16:59:57Z] Activity log set to log externally
2024-08-06 17:01:34.9775+02:00 vStoMhBp14-1 INFO BluePrism.AutomateAppCore.TcpListener processid=6024 thd=13 Created session: 1f79cb29-87b2-4068-9f7b-c5f6f2fb122b; process: Login; Run Mode: Exclusive
2024-08-06 17:01:34.9775+02:00 vStoMhBp14-1 INFO BluePrism.AutomateAppCore.TcpListener processid=6024 thd=13 Created session: 1f79cb29-87b2-4068-9f7b-c5f6f2fb122b; process: Login; Run Mode: Exclusive
2024-08-06 17:01:34.9775+02:00 vStoMhBp14-1 INFO BluePrism.AutomateAppCore.Resources.ResourceRunnerBase processid=6024 thd=13 [2024-08-06 17:01:34Z] Created session: 1f79cb29-87b2-4068-9f7b-c5f6f2fb122b; process: Login; Run Mode: Exclusive
2024-08-06 17:01:43.8216+02:00 vStoMhBp14-1 INFO BluePrism.AutomateAppCore.TcpListener processid=6024 thd=17 Session (ID: 1f79cb29-87b2-4068-9f7b-c5f6f2fb122b) started. Process Name: Login
2024-08-06 17:01:43.8216+02:00 vStoMhBp14-1 INFO BluePrism.AutomateAppCore.Resources.ResourceRunnerBase processid=6024 thd=17 [2024-08-06 17:01:43Z] Session (ID: 1f79cb29-87b2-4068-9f7b-c5f6f2fb122b) started. Process Name: Login
2024-08-06 17:01:58.9153+02:00 vStoMhBp14-1 WARN BluePrism.AutomateAppCore.TcpListener processid=6024 thd=17 Session (ID: 1f79cb29-87b2-4068-9f7b-c5f6f2fb122b) terminated. Process Name: Login; Reason: Exception : 0x80131505: The operation has timed out.
2024-08-06 17:01:58.9153+02:00 vStoMhBp14-1 WARN BluePrism.AutomateAppCore.Resources.ResourceRunnerBase processid=6024 thd=17 [2024-08-06 17:01:58Z] Session (ID: 1f79cb29-87b2-4068-9f7b-c5f6f2fb122b) terminated. Process Name: Login; Reason: Exception : 0x80131505: The operation has timed out.
Just provides the same, it times out.
Can someone give me any answers/ help/ ideas please?
Answered! Go to Answer.
09-08-24 02:23 PM
Hello to anyone looking for help and finding this.
I have continued to work on this issue and have had my first success. I will schedule it over the weekend and if ok Monday then I'm happy it is working.
The solution seems to be a reinstallation of the Login Agent. It was a very quick process to do also. After installation, I reset the Service "Log On As" account for the user I needed and restarted the Server.
I watched through the control/ App server as it came back to Logged out. I sent the Login process and this time it worked.
Hope this helps if anyone gets stuck
09-08-24 02:23 PM
Hello to anyone looking for help and finding this.
I have continued to work on this issue and have had my first success. I will schedule it over the weekend and if ok Monday then I'm happy it is working.
The solution seems to be a reinstallation of the Login Agent. It was a very quick process to do also. After installation, I reset the Service "Log On As" account for the user I needed and restarted the Server.
I watched through the control/ App server as it came back to Logged out. I sent the Login process and this time it worked.
Hope this helps if anyone gets stuck