Resource PC goes to offline state after the logout process runs

[AkshayaR1]

Hi All,

We recently upgraded the blue prism from 6.3 to 6.6 and post which I have observing this issue on the runtimes resources often.
We have our schedule that goes like this Logout->login->actual process which a post completion delay of 150 seconds between each of these runs.

After the logout process runs, the runtime resource goes to "Offline" state and never allowing the login process to run. On manual login to the machine or restarting it temporarily fixes the issue. One or two times schedule runs fine. Again third time I see the resource machine going to offline after the logout process.

Other one is post the logout process, "Logged Out" state shows up which is expected. But login process never runs until restarting the machine. These two issues have been repeating randomly over the last few days.
Prior to the upgrade we had so issues with runtime resources.

Could someone let me know where I am going wrong and what is the resolution to both these issues?

Thanks in advance!

Regards,,
Akshaya 


------------------------------
Akshaya R
RPA Developer
------------------------------

[Simon_AndrePede]

Hi Akshaya,

To me it sound like the Login Agent(LA) is not functioning correctly. 

After upgrading from BP version 6.3 to 6.6, i suggest try reinstall the LA. Further, if you are using the SAS function of LA instead of having disabled the Ctrl + Alt+ Delete screen and the disclaimers, you might want to verify the SAS is enabled correctly. 

One thing i often find an issue, in new installations is the Login Agent service is not started, you need to make sure it's actually running after logging out. 

------------------------------
Simon Andre Pedersen
Manager
PWC
Asia/Hong_Kong
------------------------------

[AkshayaR1]

Hi Simon,

Thanks for sharing!

I have twice re-installed the login agent suspecting that there could an issue during the installation.

Also I am not using the SAS functionality and I have set it to false as Ctrl+Alt+Del is already disabled on the resource machines. Login agent service is running as well. But is there any possibility of the service stopping after the log out? I am asking this since you have asked me to check on whether the service is running after logout.

------------------------------
Akshaya R
RPA Developer
------------------------------

[expertcr]

I have a few tips for you.
Check your LoginAgentService.config located in C:\ProgramData\Blue Prism Limited\Automate V3

1. Check that your folder is valid (IN RED), if you install in a different folder or drive, just change this line to reflect that.
2. Validate your connection in your Interactive Client (GREEN), need to have the same name that you are using on that computer.
3. If you are using SSO, please add the last line (BLUE) to allow SSO to work.
If you using SSO, your service in the Runtime Resource for LOGIN AGENT needs to run with a valid user from your AD (most the time the save bot account).

If you keep having issues, please contact our Technical Support team to review in deep your case.
I hope you have a nice weekend.



------------------------------
Luis Lopez
Customer Support Engineer English and Spanish
Blue Prism Ltd
------------------------------

[AkshayaR1]

Hi Luis,

Thanks for the suggestion.

I got this issue resolved. Additionally added a decision logic to login agent object-->logout page to check if the resource has already been logged out before forcing it to log off. Looks like this has to be manually added to login agent 6.6 process.

Thanks all for your valuable time.

------------------------------
Akshaya R
Developer
Cognizant
Europe/London
------------------------------

[Kristine_MarieB]

Hi Akshaya, I know this thread has been solved for a long time now but can you kindly share a screenshot (additional logic you implemented) on how you resolved this problem?

Thanks!

------------------------------
Kristine Marie Bataan
------------------------------