LoginAgent process prevents ResourcePC process from starting with static callback port of BP Server

[TetsujiJunicho]

LoginAgent is installed in ResourcePC and it starts SystemPC process once the PC gets running. That's fine. Once it is logged in, the ResourcePC process should start and send shutdown instruction to the SystemPC process, but it doesn't start and the SystemPC process keeps alive. I confirmed that when the Blue Prism Servers have default callback port, i.e. 0, it works fine as long as dynamic porting is permitted in the firewall settings. However, when the Blue Prism Servers have static callback port such as 8197, which is opened in receiving client machine, the ResourcePC process cannot start. It says "*** Cannot start - no database - Connection failed - Another property by this name already exists.". It is vital the callback port be static. Automate.config and LoginAgentService.config file image is attached. Additional info: users are authorized via Active Directory. Thanks in advance.

[TetsujiJunicho]

[Self solved] One callback port(such as 8197) for ResourcePC and another callback port(such as 8198) for SystemPC. Need two identical connection info except for callback port .

[Anonymous]

tjunicho, It seems that files didn't attached correctly. Can you please paste the content of the ""Automate.config"" and ""LoginAgentService.config"" files? Thanks.

[TetsujiJunicho]

Attatchment doesn’t work for this forum. It’s known issue, sorry!