Login agent service started and then stopped

[RajeshSrirambha]

Hi,

We have created new Blue Prism test and production environments (Test2 & Prod2) for new group of processes and completed all necessary configurations both in test2 and prod2. Example: DB configuration, server configuration and all other Blue Prism configurations are completed along with new runtime resource and login agent configurations.

However, when we tried to start login agent services in prod2 environment we get an error message "The Blue prism login agent service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs". Whereas this works fine in the test2 environment.

Not sure what we are missing here. Please find more information on setup and what we have tried as part of solution steps.

Additional Information:

1. Environments configured with Multi-authentication and enabled SSO.
2. Login agent service configured to run with service account.
3. The service account is part of local client group (Logon as service).
4. Setup works fine on existing/old test, prod environments and also on test2 environment which is copy of the new prod2 environment.
5. We have added 'sso' argument and prod2 BP connection name (dbconname) in 'LoginAgentServices.config file'.
6. The service account that try to run login agent services has user access level as 'runtime resource' in Blue Prism user roles.
7.  We are able to run SAS services with the same service account.
8. We couldn't see any logs on 'LoginAgentService' in event log viewer.

Any help would be appreciated.

Best Regards,

Rajesh

[JerinJose]

Hi Rajesh,

are you using the same version of login agent as that of your Blueprism Application?
check the Loginagent config file in Programdata for the session working directory path it might be pointing to the Programfiles x86 path

config file can be found in location "C:\ProgramData\Blue Prism Limited\Automate V3\LoginAgentService.config"

<?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>
</startuparguments>
</configuration>​

[RajeshSrirambha]

@Jerin Jose - Hi Jose, Sorry I have clicked on 'Inappropriate answer' accidentally. But please find my reply​ to your answer.

We are using the same version of login agent as that of our Blue Prism Application. (We have installed login agent which is available in 'Installers' folder under Blue Prism Automate)

The 'Workingdirectory path'  in the LoginAgentService.config file in Programdata is pointing to the right program files directory: "<C:\Program Files\Blue Prism Limited\Blue Prism Automate\>".

Best Regards,
Rajesh