SAP Knowledge Base Article - Preview

2497642 - Tomcat does not start post BI 4.2 upgrade

Symptom

  • Tomcat does not start after performing a BI Upgrade where the bundled Tomcat version gets updated from Tomcat 7 to Tomcat 8
  • The below error is observed in the Tomcat's stderr.log

    "org.apache.catalina.startup.Catalina load
    WARNING: Catalina.start using conf/server.xml: Error at (27, 66) : org.apache.catalina.core.JasperListener

    org.apache.catalina.startup.Catalina start
    SEVERE: Cannot start server. Server instance is not configured"

    SEVERE: Protocol handler instantiation failed
    java.lang.ClassNotFoundException: org.apache.catalina.core.JasperListener
    at java.net.URLClassLoader.findClass(URLClassLoader.java:444)

Read more...

Environment

  • SAP BusinessObjects BI Platform 4.1 SP09+
  • SAP BusinessObjects BI Platform 4.2 SPx
  • Microsoft Windows Server
  • Tomcat 8 

Product

SAP BusinessObjects Business Intelligence platform 4.1 ; SAP BusinessObjects Business Intelligence platform 4.2

Keywords

org.apache.catalina.core.JasperListener, tomcat does not start, BI 4.2, Tomcat 8, server.xml , KBA , BI-BIP-DEP , SBOP Web Application Deployment, Wdeploy , BI-BIP-INS , Enterprise (BI platform) installation, upgrade, patching , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.