Skip to main content
Kofax

Most frequent errors from RoboServer

3021814

 

Information: 

The table below contains the most frequent errors. If you see an error not in this table, please contact Kofax Technical Support

 
Error Message Details Location (where the error could be found)
Deactivating RoboServer. The server has not been activated for more than 24 hours.

The RoboServer gets its license from the Management Console. If the RoboServer loses connection to the Management Console then it will still keep it license for 24 hrs more (so it can run robots). When the 24 hr mark is hit, the RoboServer will lose its license and this message will be logged.
However, version 10.3 contains a bug (ID 1254673) where the RoboServer can lose its license even if it's connected to the Management Console at the time. To recover from this the RoboServer has to be restarted.
This bug has been fixed in the following versions (including backported fixes):

10.3.0.8
10.3.1.2
10.3.2.3
10.4.0.1
10.5 and later

Management Console > Logs tab

or

RoboServer Log Database > Server_Message table

RoboServer is being activate by multiple Management Consoles The RoboServer is added in at least two Management Consoles (look at the "current activator" and "other activators" in the error details - these are the Management Consoles that contain this RoboServer). Management Console > Logs tab > RoboServer
ERROR kapow.robot.rqlserver.RoboServer - Unable to register to the <clusterName> cluster: java.net.ConnectException: Connection refused: connect. Retrying...

Possible reasons:


- Management Console (where the RoboServer should register) is not responding (not started, unable to connect)
- there is no license on the Management Console (yet)

RoboServer command line

or

Even viewer (when RoboServer runs as Windows service)

Unable to register to the <clusterName> cluster: Unexpected Error: No cluster found for name '<clustrName>'.. Retrying... A cluster with the specified name doesn't exist. Please note that the cluster name is case sensitive. same as above
Unable to register to the <clusterName> cluster: Repository responded with an error: HTTP/1.1 404  [Content-Type: text/html;charset=utf-8, Content-Language: en, Content-Length: 1105, Date: Thu, 09 Apr 2020 19:54:42 GMT] org.apache.http.conn.BasicManagedEntity@<id>. Retrying...

Possible reasons:

- the Management Console to which the RoboServer should register is incorrect. E.g. ManagementConsole is deployed into Tomcat and it's running, but the url has been mistyped.

- Management Console has been corrupted because it was not allowed to start completely on first start; please see the related article (Embedded Management Console Fails to Start Up the First Time).

RoboServer command line

or

Even viewer (when RoboServer runs as Windows service)

or

RoboServer log files (under the user's application data folder)

When user management is enabled -mcUrl must be specified.

ERROR kapow.robot.rqlserver.RoboServer   - RoboServer failed to start. null

When using Management Console embedded mode (e.g. started by "RoboServer -MC") and User Management is enabled in RoboServer Settings, you must also set Register to a Management console (General tab of RoboServer Settings)
To avoid error: enable "Register to a Management Console" in RoboServer Settings and enter MC path and credentials

RoboServer command line

or

Even viewer (when RoboServer runs as Windows service)

When user management is disabled -mcUrl may not be specified.

ERROR kapow.robot.rqlserver.RoboServer   - RoboServer failed to start. null

When using Management Console embedded mode (e.g. started by "RoboServer -MC") and User Management is enabled in RoboServer Settings, you must NOT set Register to a Management console (General tab of RoboServer Settings).

To avoid error: disable "Register to a Management Console" in RoboServer Settings

same as above

mcUrl must be used to register the RoboServer when running RoboServer as standalone.

ERROR kapow.robot.rqlserver.RoboServer   - RoboServer failed to start. null

This error is generated when starting a standalone RoboServer (i.e. without a -MC parameter) and not specifying a Management Console to which to register.

To avoid error: set a Management Console either in RoboServer Settings or with the -mcUrl parameter in the RoboServer command.

same as above

Applies to:  

Product Version
RPA Any

 

 

  • Was this article helpful?