BusinessObjects Board

HTTP Status 500 - can't access CMC or Launchpad

server administration XI Server Discussion
#1

Hi,

We managed to install SAP BI Platform 4.2 SP4 on a Windows 2008 R2 machine. The installation itself went smoothly, however, we are encountering a problem with accessing the CMC and the Launchpad: We can’t make it to the Login Screen!

I checked with the CCM and saw all SIA servers were running, Tomcat was running as well and we were able to go to the 8080 Tomcat site. It’s just the CMC and Launchpad we’re encountering an error, whether we’re accessing them from the localhost or a computer over the network.

We’ll be trying the solution in https://archive.sap.com/discussions/thread/1996536. In the mean time, has anyone else encountered this error?

The full error is listed below (this is what we are greeted with the moment we try accessing either LP or CMC):


HTTP Status 500 – Internal Server Error
Type Exception Report

Message Servlet.init() for servlet equinoxbridgeservlet threw exception

Description The server encountered an unexpected condition that prevented it from fulfilling the request.

Exception

javax.servlet.ServletException: Servlet.init() for servlet equinoxbridgeservlet threw exception
	org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:478)
	org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:80)
	org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:341)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:799)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:861)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1455)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.lang.Thread.run(Thread.java:812)
Root Cause

java.lang.RuntimeException: Could not find framework
	org.eclipse.equinox.servletbridge.FrameworkLauncher.buildInitialPropertyMap(FrameworkLauncher.java:475)
	org.eclipse.equinox.servletbridge.FrameworkLauncher.start(FrameworkLauncher.java:314)
	org.eclipse.equinox.servletbridge.BridgeServlet.init(BridgeServlet.java:148)
	javax.servlet.GenericServlet.init(GenericServlet.java:158)
	org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:478)
	org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:80)
	org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:341)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:799)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:861)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1455)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.lang.Thread.run(Thread.java:812)
Note The full stack trace of the root cause is available in the server logs.

Apache Tomcat/8.5.13

hueysantiago (BOB member since 2015-08-03)

#2

After installation we couldn’t access BI Launchpad and the CMC (4.2 SP05). After undeploy and deploy it worked (deploy took a long time).

RikDeclercq :belgium: (BOB member since 2006-09-28)

#3

Yes! I have encountered the same issue when performing in place upgrades to both 4.2 SP4 as well as 4.2 SP5. Here is what I did to resolve:

  1. Navigate to your E:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\wdeploy directory in a CMD prompt.

  2. wdeploy tomcat8 deployall

Then check to see if that fixed it. At this point you may get a 404 error.

If there are still issues:

  1. Stop Tomcat.

  2. Navigate to E:\Program Files (x86)\SAP BusinessObjects\tomcat\work\Catalina

  3. Rename localhost folder to localhost.old

  4. Start Tomcat. This should recreate the localhost folder.

  5. Test.

  6. Delete localhost.old folder.

Edit - I was in a hurry and provided sloppy instructions. Please refer to SAP KB doc 2034315 - Deploying or Re-Deploying Tomcat Web Applications to SAP BusinessObjects Business Intelligence Platform 4.X.

clarence (BOB member since 2005-11-18)

#4

Always a good idea to drop the work directory during a redeploy…

joepeters :us: (BOB member since 2002-08-29)

#5

Hi all, thanks for the suggestions. The first part of https://archive.sap.com/discussions/thread/1996536 (rebuilding the localhost folder in Catalina) was enough to fix the issue. It weirded us out because this was a fresh install.

hueysantiago (BOB member since 2015-08-03)

#6

I just wanted to say “Thanks” for this thread and the link to the SAP KB article. I did a fresh install of Data Services IPS 4.2 SP7 (aka BOE lite) and encountered this exact error. The same error was encountered on an in-place upgrade also.

The instructions in the KB article resolved our issue. It did end up taking longer than the instructions suggested, but we’re on Windows Server 2019 and not Linux.

eganjp :us: (BOB member since 2007-09-12)