Skip to main content
Inspiring
April 9, 2025
Question

Not able to Enable RPA Agent

  • April 9, 2025
  • 2 replies
  • 2 views

I am not able to enable the RPA agent from my system, I have followed all the instructions mentioned in appian documentation like JAVA_HOME setup, Certificates everything. One time it got enabled and and after that I am not able to enable it again so I have tried uninstall and install several times but no luck.

Please see the attached log

2025-04-09 09:25:19,418|INFO|com.novayre.jidoka.client.JidokaClient.parseArgs:447|Using the default reset after long connection fault value: 0|main|0|242/4,096|
2025-04-09 09:25:19,418|INFO|com.novayre.jidoka.client.JidokaClient.parseArgs:449|Using the default connection timeout value: 600|main|0|242/4,096|
2025-04-09 09:25:19,418|INFO|com.novayre.jidoka.client.JidokaClient.parseArgs:450|Using the default lock runnable value: true|main|0|242/4,096|
2025-04-09 09:25:19,418|WARN|com.novayre.jidoka.client.JidokaClient.readConfigurationFromPropertiesFile:652|An optional property has not been read: configuration.log.level|main|0|242/4,096|
2025-04-09 09:25:19,418|WARN|com.novayre.jidoka.client.JidokaClient.readConfigurationFromPropertiesFile:652|An optional property has not been read: connection.userAgent|main|0|242/4,096|
2025-04-09 09:25:19,501|INFO|com.novayre.jidoka.client.AuthManager.<init>:75|Hash file to use tmp-hashNotSet.tmp|main|83|241/4,096|
2025-04-09 09:25:23,777|INFO|com.novayre.jidoka.client.windows.WorkstationLockListening.run:116|Lock window sucessfully created|lock|4359|236/4,096|
2025-04-09 09:25:23,777|INFO|com.novayre.jidoka.client.windows.WorkstationLockListening.run:123|Lock window notification sucessfully registered|lock|4359|236/4,096|
2025-04-09 09:25:24,184|WARN|com.novayre.jidoka.client.ClientManager.clearCookies:1111|Cookies could not be cleared|main|4766|231/4,096|
2025-04-09 09:25:24,184|INFO|com.novayre.jidoka.client.JidokaClient.isHashInitialized:1320|Using robot key as authentication system since there is not any hash set as parameter.|main|4766|231/4,096|
2025-04-09 09:25:24,214|INFO|com.novayre.jidoka.client.JidokaClient.getInitialCommand:1269|[[10f02202-ffae-40e6-ad70-208c5069106c]] Robot key to be sent to console is 92F4ACFFDC...|main|4796|230/4,096|
2025-04-09 09:25:24,440|INFO|com.novayre.jidoka.client.ClientManager.communication:1506|Sent REQ_JK_ROBOT_KEY_AUTH (543)|main|5022|227/4,096|
2025-04-09 09:25:24,558|WARN|com.novayre.jidoka.client.ClientManager.internalSendCommand:1243|IOException sending command: REQ_JK_ROBOT_KEY_AUTH. Retrying...|main|5140|50/4,096|
java.net.SocketException: Connection reset
at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:320)
at java.base/sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:347)
at java.base/sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:800)
at java.base/java.net.Socket$SocketInputStream.read(Socket.java:966)
at java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
at java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
at java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
at java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1500)
at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1415)
at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
at java.base/sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:578)

Please guide me how can i resolve this.

Thanks in advance

2 replies

kishorej1999
Participating Frequently
April 21, 2025

Hii [mention:59914399cb9c425d812a48b4c232d982:e9ed411860ed4f2ba0265705b8793d05] ,

There are some steps you can follow:
-> Add your JRE Path in environment variable and check from the console.
-> Try to Restart from the operation console, if it still not work please create the new one and check the connection from the connected system.

Thanks!

Participating Frequently
April 22, 2025