Unable to connect with robot error

Hello

Whenever I try to run a bot in Workfusion Studio, the following error happens: “Unable to connect with robot”

This happened suddenly, a couple hours ago I was working just fine with the bots running without trouble

Version is 2.3.1 of WorkFusion RPA Express, the detailed log of the error is as follows:

Unable to connect with robot
com.workfusion.studio.rpa.recorder.player.driver.DriverInitializationException: Unable to connect with robot
at com.workfusion.studio.rpa.recorder.player.driver.RpaUniversalDriver.connect(RpaUniversalDriver.java:127)
at com.workfusion.studio.rpa.recorder.player.driver.RpaUniversalDriver.initialize(RpaUniversalDriver.java:64)
at com.workfusion.studio.rpa.recorder.player.PlaybackLogic.run(PlaybackLogic.java:75)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Build info: version: ‘9.3.1.0’, revision: ‘ef4b445edf’, time: ‘2019-05-29T11:53:16.301Z’
System info: host: ‘5CG85193LS-W10’, ip: ‘127.0.0.1’, os.name: ‘Windows 10’, os.arch: ‘amd64’, os.version: ‘10.0’, java.version: ‘1.8.0_121’
Driver info: driver.version: RpaUniversalDriver
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:762)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:265)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:247)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:148)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:185)
at com.freedomoss.crowdcontrol.webharvest.selenium.wrapper.RemoteDriverWrapper.(RemoteDriverWrapper.java:39)
at com.workfusion.studio.rpa.recorder.player.driver.RpaUniversalDriver.connect(RpaUniversalDriver.java:125)
at com.workfusion.studio.rpa.recorder.player.driver.RpaUniversalDriver.initialize(RpaUniversalDriver.java:64)
at com.workfusion.studio.rpa.recorder.player.PlaybackLogic.run(PlaybackLogic.java:75)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.http.conn.HttpHostConnectException: Connect to localhost:15444 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused: connect
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:71)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
at org.openqa.selenium.remote.internal.ApacheHttpClient.fallBackExecute(ApacheHttpClient.java:139)
at org.openqa.selenium.remote.internal.ApacheHttpClient.execute(ApacheHttpClient.java:87)
at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:337)
at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:135)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:142)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:741)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:265)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:247)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:148)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:185)
at com.freedomoss.crowdcontrol.webharvest.selenium.wrapper.RemoteDriverWrapper.(RemoteDriverWrapper.java:39)
at com.workfusion.studio.rpa.recorder.player.driver.RpaUniversalDriver.connect(RpaUniversalDriver.java:125)
at com.workfusion.studio.rpa.recorder.player.driver.RpaUniversalDriver.initialize(RpaUniversalDriver.java:64)
at com.workfusion.studio.rpa.recorder.player.PlaybackLogic.run(PlaybackLogic.java:75)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:74)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:71)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
at org.openqa.selenium.remote.internal.ApacheHttpClient.fallBackExecute(ApacheHttpClient.java:139)
at org.openqa.selenium.remote.internal.ApacheHttpClient.execute(ApacheHttpClient.java:87)
at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:337)
at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:135)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:142)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:741)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:265)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:247)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:148)
at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:185)
at com.freedomoss.crowdcontrol.webharvest.selenium.wrapper.RemoteDriverWrapper.(RemoteDriverWrapper.java:39)
at com.workfusion.studio.rpa.recorder.player.driver.RpaUniversalDriver.connect(RpaUniversalDriver.java:125)
at com.workfusion.studio.rpa.recorder.player.driver.RpaUniversalDriver.initialize(RpaUniversalDriver.java:64)
at com.workfusion.studio.rpa.recorder.player.PlaybackLogic.run(PlaybackLogic.java:75)
at java.lang.Thread.run(Thread.java:745)

If it helps, the errors began to show up after I stopped a process in the control tower due to me skipping manual tasks accidentally and not being able to run them anymore.

Thanks

@kberrocal have you tried restarting the application?

For restarting you mean closing and reopening or reinstalling entirely?

I’ve done the former a lot of times already and the later not yet

I mean stopping the server component, closing and reopening the application.
Have you tried restarting the system, too?

Yes, to both, I’ve restarted the server component (which just in case, is local), reopening the application and restarted the computer multiple times without result

However, today the bot is responding properly, the computer was turned off for the rest of the day but technically I didn’t do anything different from what I’ve been trying before, I’m still curious of what might have happened so that I can possibly prevent the issue in the future.

I’ll keep the thread updated in case of further issues

Thanks

1 Like

Thank you @kberrocal please let us know if you have this issue again.

Thanks a lot, still, you know why that happened and how I can prevent it from happening again?