Resource VM showing Offline and Not Connected

[mfortunato]

Architecture (DB server, Application Server, Interactive Server and then Runtime Resources build on VM's)

Yesterday I upgraded my BP version from 6.3.1 (that worked perfectly with Login Agent) to 6.8.1, as well as updated the Login Agent that comes with 6.8.1. But now I'm faced with a dilemma of were all the RTR (run time resources) VM's state are showing Offline and the connection is Not Connected within the Interactive Control Room. But if I manually log onto one of the VM's, the service starts up automatically and the state of the VM shows Idle and the connection shows Yes - Connected, but as soon as I logout of the VM or restart, the state goes to Offline and the connection to Not Connected.

Help needed urgently.

------------------------------
[Mario] [Fortunato] [Mr]
[RPA Manager]
[First National Bank]
[Windhoek] [Namibia]
------------------------------

[BalazsRoman]

Hi @mfortunato, did​ you reinstall Login Agent on all the RTRs? If you check the services on the logged out VMs, is Login Agent running? Did you change the name of the connection you're trying to use within the interactive client? If yes, you'll need to update it for Login Agent as well.

------------------------------
Balazs Roman
RPA Consultant
human+
Europe/London
------------------------------

[mfortunato]

Hi @Balazs Roman yes reinstall Login Agent on all RTRs. Herewith the steps I took.
1. Back up all processes via packages
2. Back up DB
3. Install V6.8.1 on App server
4. Install 6.8.1 on IC
5. Install 6.8.1 on all RTR as well as the new Login Agent

Yes Login Agent is running and is installed on all RTR. No I haven't changed the ​name within the IC.  There is no Login Agent installed on IC.

------------------------------
[Mario] [Fortunato] [Mr]
[RPA Manager]
[First National Bank]
[Windhoek] [Namibia]
------------------------------

[mfortunato]

I managed to resolved the issue..

------------------------------
[Mario] [Fortunato] [Mr]
[RPA Manager]
[First National Bank]
[Windhoek] [Namibia]
------------------------------

[DaveMorris]

Can you share the solution in case others come across this in the future and feel that they have a similar issue?

------------------------------
Dave Morris
Cano Ai
Atlanta, GA
------------------------------

[mfortunato · Accepted solution]

@Dave Morris ​well no issues, below is what happened and how I managed to resolve it.

Step 1.
Kindly note when you upgrade your BP application version, there is a chance that the parameters will be reset within the LoginAgentService.config file, which is located <C:\ProgramData\Blue Prism Limited\Automate V3>.

Upon opening the file I noted the below:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <workingdirectory path="NOTINSTALLED"/>
  <startuparguments>
    <argument name="resourcepc"/>
    <argument name="public"/>
    <argument name="port">
      <value>8181</value>
    </argument>
  </startuparguments>
</configuration>

From the above configuration file <LoginAgentService.config> one could clearly see that the working path is not defined/set <workingdirectory path="NOTINSTALLED"/> and that the dbconname argument tag is missing. I edited the file <LoginAgentService.config> with the correct values, as per   below. Restarted the RTR and noticed the pc icon with a key and the status become Logged Out as well as Yes-Connected within the IC Room.

<?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>Application Server</value>
</argument>
</startuparguments>
</configuration>

Step 2.
There is a second file that needed to be edited in order for the two files to communicate. This file is located <C:\ProgramData\Blue Prism Limited\Automate V3> and is called <Automate>. See below configuration.

<?xml version="1.0" encoding="utf-8"?>
<config>
<editsummariesarecompulsory>True</editsummariesarecompulsory>
<startprocessengine>True</startprocessengine>
<maxundolevels>10</maxundolevels>
<currentconnection>
</currentconnection>
<sqlcommandtimeout>30</sqlcommandtimeout>
<archivepath>C:\Users\Administrator\Documents</archivepath>
<connections>
<connection>
<bpserver />
<port>8199</port>
<callbackport>0</callbackport>
<connectionmode>0</connectionmode>
<name>Application Server</name>
<server>your application server name or ip address should be placed here</server>
<extraparams>
</extraparams>
</connection>
</connections>
<businessobjects />
</config>

I hope that the above will help someone out there.

Kind regards
MF

------------------------------
[Mario] [Fortunato] [Mr]
[RPA Manager]
[First National Bank]
[Windhoek] [Namibia]
------------------------------