connection status as"validating" in control room>>resource

[ankitbass]

After logging into BP in runtime resource & then navigating to control room, the runtime resource connection status is "validating" under Resource section (see attachment). Can you help me out in resolving the issue so that app server connection status shows connected. This occurs for other runtime resources also.

Other points:-
1)App server in place
2)connection mode: message
3) BP server service running.
4) Using SSO


------------------------------
ankit bass
sme
s and p global
Asia/Kolkata
------------------------------

[TomaszSukiennik]

Hi,

try to find the solution in the documentation below, there is a communication problem between Runetime Resource <-> BP Server <-> Interactive Client. I guess some ports are probably closed. You could check it by ping or telnet command in cmd.

Testing for Network Connectivity Guide (blueprism.com)

Kind regards

------------------------------
Tomasz Sukiennik
RPA Developer
Digital Teammates
Europe/Lodz
------------------------------

[ankitbass]

runtime resources are connected to app server via F5 Load balanacer (LB). To perform all tests do i need to do ping/telnet LB DNS name or app server dns name

------------------------------
ankit bass
sme
s and p global
Asia/Kolkata
------------------------------

[TomaszSukiennik]

Could you past logs from runtime resource console (from machine where error occurs)? In my opinion port 8181 is closed (if you use default port) in machine where RR is running.

------------------------------
Tomasz Sukiennik
RPA Developer
Digital Teammates
Europe/Lodz
------------------------------

[ankitbass]

fyi: i am able to log inside BP  from the runtime resource but in control room the app server and other runtime resources connection status is shown as "validating". 

Logs from runtime resource:

BluePrism.AutomateAppCore.Resources.ResourceRunnerBase
[2020-12-09 07:14:22Z] Listener failed : failed to update resourcepc details on the database - System.TimeoutException: The request channel timed out while waiting for a reply after 00:00:59.9400000. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: The request operation did not complete within the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout.
at System.ServiceModel.Channels.ReliableRequestSessionChannel.SyncRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
--- End of inner exception stack trace ---

Server stack trace:
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at BluePrism.AutomateAppCore.IServer.RefreshResourcePC(String name, ResourceDBStatus status, Int32 runningSessions, Int32 activeSessions)
at BluePrism.AutomateAppCore.clsListener.RefreshDBWithCurrentState()

------------------------------
ankit bass
sme
s and p global
Asia/Kolkata
------------------------------

[TomaszSukiennik]

Check if ports are open. For Runetime Resource the default port is 8181, for Interactive Client (where is Control Room) the default port is 8199.  You can also use command netstat -a in this machine to check active connections. Check also connection with Runetime Resource: TELNET  <runtime name> <port number> , e.g. TELNET runtimeresource01 8181

------------------------------
Tomasz Sukiennik
RPA Developer
Digital Teammates
Europe/Lodz
------------------------------

[Deva393]

Hello Ankit bass,

Did your  connection "Validating" problem got resolved ? if yes can you please share us the solution.


Thanks !

Dev

------------------------------
Peeleti Devendra RPA Developer
Senior Software Engineer
Wipro
Asia/Kolkata
------------------------------

[ankitbass]

I checked ports 8199, 8181 from both runtime resource and app server and able to make successful connections. However, the issue still persists.
in Control Room>>other runtime resources or app server is shown as validating.

Does it has to do anything with BP user roles. Ex: We have AD Groups -SSO concept to login to BP in client VM's. is their any possibility that user roles access to AD group impacting the issue ?

------------------------------
ankit bass
sme
s and p global
Asia/Kolkata
------------------------------

[CKOMORO]

you also checked the firewall settings? 

Incoming Rules BluePrism Port 8181?

And AppServer and Loadbalancer all in the same networkzone? BP doenst like different Networkzones.

------------------------------
Christoph Komorovski
Technical Architect
Daimler AG
Europe/London
------------------------------

[ankitbass]

yeah... firewall nt blocking anything; 8181 also tried.
App server, LB, client vm all in same network domain.

------------------------------
ankit bass
sme
s and p global
Asia/Kolkata
------------------------------