SEVERE: Could not prestart executor: RMI executor could not be started,

We are trying to upgrade our KNIME ServerLite from 4.1 to 4.2.3, and at the same time upgrading the Executor to 3.1. We managed to update the server, and log in to it from a client.

We could not update the Executor from 2.12.1 to 3.1, so we installed from a fresh download. We are installing on Windows 64bit. This installation works as a stand alone Analytic Platform. It could run the workflows in the server workflow repository.

The server cannot start the Executor. We encounter the error

SEVERE: Could not prestart executor: RMI executor could not be started.

When a client try to execute a job on the server, the same RMI executor could not be started error occurs.

The error log messages are below. It says "Also check log file in C:\Program Files\KNIME Analytics\configuration". I don't find any log files in that directory.

What are we missing in this? Is there a way to check? All the server side extensions are installed.

=========== log messages from apache-tomee*/logs/catalina-DATE.log

Mar 01, 2016 9:59:50 PM com.knime.enterprise.server.rmi.KNIMEExecutorImpl startSlave
WARNING: The RMI process terminated unexpectedly with exit code 1
Mar 01, 2016 9:59:50 PM com.knime.enterprise.server.rmi.KNIMEExecutorImpl reportStartupError
SEVERE: RMI executor could not be started. Command executed:
C:\Program Files\KNIME Analytics\knime.exe --launcher.suppressErrors --launcher.ini R:\KSR\runtime\runtime_knime-rmi-50100\knime-rmi.ini
Last 3 lines of log output follow:
Knime:
The Knime executable launcher was unable to locate its
companion shared library.
Also check log file in C:\Program Files\KNIME Analytics\configuration
Mar 01, 2016 9:59:50 PM com.knime.enterprise.server.application.KNIMEServerApplication initializeServices
SEVERE: Could not prestart executor: RMI executor could not be started, see log file for details
com.knime.enterprise.utility.ExecutorException: RMI executor could not be started, see log file for details
at com.knime.enterprise.server.rmi.KNIMEExecutorImpl.reportStartupError(KNIMEExecutorImpl.java:397)
at com.knime.enterprise.server.rmi.KNIMEExecutorImpl.startSlave(KNIMEExecutorImpl.java:349)
at com.knime.enterprise.server.rmi.KNIMEExecutorImpl. (KNIMEExecutorImpl.java:184)
at com.knime.enterprise.server.rmi.RMIManagerImpl.startNewRMI(RMIManagerImpl.java:268)
at com.knime.enterprise.server.rmi.RMIManagerImpl.getRMIInstance(RMIManagerImpl.java:349)
at com.knime.enterprise.server.application.KNIMEServerApplication.initializeServices(KNIMEServerApplication.java:293)
at com.knime.enterprise.server.application.KNIMEServerApplication.start(KNIMEServerApplication.java:167)
at com.knime.enterprise.war.ServerInitListener.contextInitialized(ServerInitListener.java:73)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4992)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5490)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:672)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1862)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Hi David,

It looks like the installation might be broken.

Perhaps you could try to run: C:\Program Files\KNIME Analytics\knime.exe --launcher.suppressErrors --launcher.ini R:\KSR\runtime\runtime_knime-rmi-50100\knime-rmi.ini

Do you get an error message?

Best,

Jon

I shall give this a try as soon as I can. Unfortuantely we needed to revert to our original 4.1 version with 2.12.1 to allow for production server scheduled tasks to runI hope to get a window to go through the upgrade process again, and will give you the information.

Many thanks for looking at it, appreciate your attention.

Best wishes

David