SAP Knowledge Base Article - Preview

3403274 - BOE/CMC failing to start after patch update

Symptom

  • Unable to access CMC and BI Launchpad post upgrade from BI 4.2 SP09 Patch 13 to Patch 16.
  • Tomcat cache for BOE is always empty or 0 KB
  • Clearing BOE cache (0kb) and restarting tomcat does not help
  • Tried replacing server.xml and BOE web.xml  from working systems 
  • Tried redeploying BOE webapp with command line 
  • From task manager - when tomcat is restarted, it gets to 99% CPU, 1.5-1.5 GB RAM at one point but then immediately plunges to 0% and stays there - indicating perhaps the BOE thread got killed.
  • Reviewed logs and see errors in stderr log related to BOE not starting due to previous errors 
    18-Nov-2023 18:13:15.775 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
    18-Nov-2023 18:13:15.847 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [/BOE] startup failed due to previous errors
  • Repair fixed the problem but the behavior is back after SAML configuration related xml files were replaced. 


Read more...

Environment

  • SAP BusinessObjects BI 4.2 SP09 Patch 16 [ updated from Patch 13]
  • Server O/s: Windows 2016
  • RAM on Tomcat Nodes: 16GB
  • 6 Nodes (2 Tomcat webtier nodes and 4 CMS)
  • NOTE: Issue is possible in 4.2 and 4.3 as well 

Keywords

BOE CMC BI launchpad not working tomcat Cache empty 0kb securitycontext.xml SAML configuration , 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 for Me (Login required).

Search for additional results

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