Machines getting disconnected when trying to run a process

[mcamungol]

Hi BP Community, I want to inquire if anybody has encountered this problem. When dragging and dropping a process to a machine, that machines will be tagged disconnected when viewing from control room connected via AppserverA but still connected and can still run processes when viewed from control room connected via AppserverB. (Sometimes its the other way around)

Setup:

*We have 2 application servers under an azure internal load balancer.

*All runtime resources have setup the login agent the same and tried to reinstall as well on the problematic resources.

*All certificates are aligned and setup properly.

*Connection Type of Runtime resources is Blue Prism Server and the server is pointed to the Load Balancer.

Problem:

*Some runtime resources are encountering this problem but most of the runtime resources are working fine.

*Checking in the runtime resources, resource PC window, it always gets connected to AppServerA:

*Logging in the resource, and checking on the runtime resource window, when it gets disconnected it shows this error "An SSL/TLS authentication error occurred. Please contact your administrator for assistance", and also, the automatic connections to the both app servers shows like this, AppServerB shows the full hostname and with IP but when it gets connected to AppServerA it just shows Unknown then the IP:

Checking on the event logs of server:

checking event logs of runtime resource:

"BluePrism.AutomateAppCore.clsListener
An SSL/TLS authentication error occurred. - Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
BluePrism.Server.Domain.Models.SslAuthenticationException: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ---> System.IO.IOException: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond"

Seeking help to identify the main cause of this problem and how to possibly fix this.

Thanks.

[steven.boggs]

Based on your statement that sometimes AppServer A experiences this issue and other times it's AppServer B, this sounds to me like an issue with the load balancer. The error message "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond" typically indicates a networking issue, sometimes due to a firewall or in this case, perhaps the load balancer blocking communications from BPServerService.exe and not from BPServer.exe.

Check into your load balancer's settings to see if BPServerService.exe comms are being blocked and disable any firewalls in this environment to test to see if that helps resolves the issue.

[SayeedBinAbdullah]

Hi @mcamungol ,

JFYI, we have faced similar issue long back in BP version 6.4,

Upon investigating we found that Symantec endpoint was not updated in few of the virtual machines due to which the connection was getting blocked, stopping BOT's from triggering.

Below link for reference.

BOT Triggering Issue - SS&C Blue Prism Community

Sayeed Bin Abdullah

[mcamungol]

Based from your inputs, although it is not yet fixed, I think we are on the right track as we are currently checking the firewall comparing problematic and non problematic machines. 

Also, we are using v7.1.2

Thanks Sayeed.