SAP Knowledge Base Article - Preview

2473479 - Fiori com.sap.portal.navigation.flp.resources application does not start automatically

Symptom

  • Start the Enterprise Portal system via SAPMMC, sapcontrol, startsap etc.
  • When system is started, the Fiori Framework Page functionality is not working
  • Under the Netweaver Administrator -> Operations -> Start and Stop - Applications tab, com.sap.portal.navigation.flp.resources shows as Implicit Stopped (dependency failed)
  • It is possible to start the com.sap.portal.navigation.flp.resources manually from within the NWA, and the Fiori Framework Page will work properly thereafter.
  • checking the server Default Trace files you may see an error such as:
    "ConnectorLazyMBeanProvider.isSupportedExpression(ObjectName), Could not init supported object name properties, reason: 

    [EXCEPTION]
    java.lang.NullPointerException
    at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
    at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)"


Read more...

Environment

  • SAP NetWeaver Application Server for Java 7.3x and higher releases
  • Enterprise Portal

Product

SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.3

Keywords

flp@ep, flp, fiori, ep, portal, startup, restart, service, services, application, applications, start, stop, force, lazy, deploy, controller , KBA , EP-PIN-NAV-FFP , Fiori Framework Page , EP-PIN-NAV , Navigation , EP-PIN-PRT , Portal Runtime , BC-JAS-TRH , Transactions and Resource Handling , 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.