SAP Knowledge Base Article - Preview

3104343 - Receive 404 error for all BI applications after upgrade

Symptom

  • Attempts to repair installation or redeploy result in the same error
  • examining the stderr.log reveals application failures 

SEVERE: Context [/biprws] startup failed due to previous errors
SEVERE: Context [/BOE] startup failed due to previous errors
SEVERE: Context [/MobileBIService] startup failed due to previous errors

  • Details on the application failures show the following...

SEVERE: Exception sending context initialized event to listener instance of class [org.springframework.web.context.ContextLoaderListener]
java.lang.NoClassDefFoundError: org/opensaml/xml/Configuration : cannot initialize class because prior initialization attempt failed

Caused by: java.lang.ExceptionInInitializerError: java.lang.NoClassDefFoundError: javax/crypto/JceSecurity : cannot initialize class because prior initialization attempt failed
Caused by: java.lang.ExceptionInInitializerError: java.lang.ExceptionInInitializerError
caused by: java.lang.SecurityException: Can not initialize cryptographic mechanism
caused by: java.lang.SecurityException: The jurisdiction policy files are not signed by the expected signer! (Policy files are specific per major JDK release.Ensure the correct version is installed.)


Read more...

Environment

SAP BusinessObjects Business Intelligence Platform 4.3 SP1 patch 8 (this could potentially occur on other later patches)


Product

SAP BusinessObjects Business Intelligence platform 4.3

Keywords

KBA , BI-BIP-AUT , Authentication, ActiveDirectory, LDAP, SSO, Vintela , 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.