Receiving Throwable java.lang.RuntimeException: Could not find framework" after install

[former_member640902]

This is a reinstallation of SAP BO 4.2 SP6 on Server 2016. After completing the web install, and then rebooting the server, i get this error:

Nov 21, 2019 5:38:34 AM org.apache.catalina.core.ApplicationContext log
SEVERE: StandardWrapper.Throwable
java.lang.RuntimeException: Could not find framework
at org.eclipse.equinox.servletbridge.FrameworkLauncher.buildInitialPropertyMap(FrameworkLauncher.java:475)
at org.eclipse.equinox.servletbridge.FrameworkLauncher.start(FrameworkLauncher.java:314)
at org.eclipse.equinox.servletbridge.BridgeServlet.init(BridgeServlet.java:148)
at javax.servlet.GenericServlet.init(GenericServlet.java:158)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1183)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1099)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:989)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4931)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5241)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1107)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1841)
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:808)

Nov 21, 2019 5:38:34 AM org.apache.catalina.core.StandardContext loadOnStartup
SEVERE: Servlet [equinoxbridgeservlet] in web application [/BOE] threw load() exception
java.lang.RuntimeException: Could not find framework
at org.eclipse.equinox.servletbridge.FrameworkLauncher.buildInitialPropertyMap(FrameworkLauncher.java:475)
at org.eclipse.equinox.servletbridge.FrameworkLauncher.start(FrameworkLauncher.java:314)
at org.eclipse.equinox.servletbridge.BridgeServlet.init(BridgeServlet.java:148)
at javax.servlet.GenericServlet.init(GenericServlet.java:158)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1183)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1099)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:989)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4931)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5241)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1107)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1841)
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:808)

Note: This server had worked, but we are testing automated installations. I uninistalled, deleted all the files, history, registry, etc. We deleted the localhost directory and then restarted Tomcat. We still get this error and HTTP Error 500.

[denis_konovalov]

you forgot to mention where you see this error, or where exactly you see http 500.

I'm assuming the exception is from tomcat log

So, the suggestion then would be to try to manually redeploy webapps.
And if it doesn't help then review the installation logs for any irregularities.