Skip to main content
Kofax

MC fails when opening

Article # 3030738 - Page views: 39

Issue

I have some problems when opening MC, the web page cannot be loaded. An error is shown:

ERR_SSL_PROTOCOL_ERROR

MC has been configured as embedded mode:

Bellow information raised when running Robserver via CMD:

Unable to write to the configured log directory: C:\Program Files\Kofax RPA 11.0.0.1 241 x64\bin (Acceso denegado. (0x5))
The Wrapper may also have problems writing or rolling the log file.
Please make sure that the current user has read/write access.
--> Wrapper Started as Console
Launching a JVM...
WrapperManager: Initializing...
Kofax RPA RoboServer 11.0.0.1 241
(C) 1999-2020 Kofax.

RoboServer detected the following plugins:
Common Plugin 11.0 (compatible)

WARNING: running the MC embedded is deprecated and *not* intended for production usage, refer to the Administrators Guide for information about how to install in a Tomcat instance or run the MC in a Docker container.

WARNING: when running the MC embedded the file access restrictions from RoboServer settings are ignored. The embedded MC uses a filesystem based database and requires file system access.

Preparing embedded Management Console server...
Starting web server...
Jun 28, 2021 11:09:59 AM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector
INFO: Using a shared selector for servlet write/read
Jun 28, 2021 11:10:15 AM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
HTTP Connector started on port 50080.
Web server started.

Starting RoboServer...
Starting RQL service 'Socket-based RQL Service. Port: 50000'...
Failed to start RoboServer. Failed to start Socket-based RQL Service. Port: 50000: The server socket could not bind to the specified port number 50000. The port may already be in use. Exception: Address already in use: JVM_Bind

Press any key to exit.

 

Solution

The important message in console log is:

Port: 50000: The server socket could not bind to the specified port number 50000. The port may already be in use. Exception: Address already in use: JVM_Bind

 

This means that there is already other process running that listens on port 50000.

On Windows you can run following command:

netstat -ANO | find ":50000"

If you see any row with status LISTENING, then the number in the last column is the Process ID (PID) of process that is listening on port 50000, so you can try to find it in Task Manager and analyze what kind of process it is.

 

Level of Complexity 

Moderate

 

Applies to  

Product Version Build Environment Hardware
Kofax RPA Any      

References

Add any references to other internal or external articles