topic RE: Connection Status is: No in Product Forum

Connection Status is: No

EricLi — Sun, 26 Apr 2020 05:36:00 GMT

After upgrade resource system from Win7 to Win10, this resource's connection status keep in "No", the last connection message as below. Check the port 8181 on this machine, it is listening. How to fix this issue?

TCP 0.0.0.0:8081 0.0.0.0:0 LISTENING 3588

TCP 0.0.0.0:8181 0.0.0.0:0 LISTENING 14364

TCP [::]:8081 [::]:0 LISTENING 3588

------------------------------
Eric Li
Operation Analysis
AIG
Asia/Hong_Kong
------------------------------

RE: Connection Status is: No

KaranSareen — Thu, 30 Apr 2020 01:05:00 GMT

Hello Eric

If the message is seen in the Control Room when the status of a Runtime Resource is being queried then it may indicate that the connection between the two machines is blocked. Typically, firewall rules may be blocking the Runtime Resource's configured port. Try connecting the listening port on the Runtime Resource from the App Server and see if you can reach it.

The Runtime Resource firewall will need to allow Outbound connections on the configured startup port, and on the Callback Port, and the machine which is querying the status (via Control Room) will need to accept Inbound connections on the same port numbers.

For more information, you can refer the Knowledge Base as linked below:

How do I fix error "An operation was attempted on something that is not a socket" in Blue Prism event logs?

------------------------------
Karan Sareen
Solution Support Engineer
Blueprism
Australia/Sydney
------------------------------

RE: Connection Status is: No

EricLi — Thu, 07 May 2020 03:35:00 GMT

Thanks Karan

We have tried to open all ports (inbound and outbound, TCP and UDP) on runtime resource, but the issue keep existing. It is quite strange that other machines install OS by using the same ghost file, but they are work well without any firewall configuration.

------------------------------
Eric Li
Operation Analysis
AIG
Asia/Hong_Kong
------------------------------