30-03-23 10:27 AM
Hi, Community
Can any one provide possible causes of the following symptom where the Connection status appears "Disconnected"?
The server and client is deployed on a different subnet.
When the RR is invoked along with the Interactive Client by enabling the local device setting, it looks normal but the scheduling doesn't work. When the RR is invoked separately, it's Connection status appears as "Disconnected".
TCP connection using Test-NetConnection from the Client side towards the Server with port number 10000 is true and so is the same test from the Server side towards the Client with port number 8181.
The ASCR is using default values i.e., gRPC(default), 10000 port and hostname. The corresponding hosts file has also been checked from the Client side.
Can this be a network issue? Then what test needs to be done to PROVE it.
or, did I miss something in this configuration?
Best regards
30-03-23 06:37 PM
Hello,
we faced similar issues when introducing V7.x with ASCR. In our case the issue has been in DNS resolution. I recommend you try hard wiring the machines using the host file and see if this solves the issue to start with. If it does you may want to check on your DNS.
31-03-23 12:46 AM
Hi, @Felix Gerdwilker
Thank you for thre response.
Yes, we have set the host file with the hostname of the Server and also checked the network route from the Client PC towards the Server PC port 8199 has no problem according to the TcpNetConnection testing. Blue Prism functions normally except scheduling.
The scheduling is to do with ASCR setting as far as I understand it. The ASCR configuration is set with hostnanme=<hostname>, port=10000(default) and gRPC. Accordingly, the Blue Prism Client connects to the Server using the hostname for sure.
Is there any other point to check out?
Best regards
------------------------------
HongJoo Choi
------------------------------