SPM Startup Failed with FATAL Error SPEND_ANALYTICS_STARTUP_FAILED

[Former Member]

Hello Experts,

I am getting FATAL Error SPEND_ANALYTICS_STARTUP_FAILED while starting the SPM Application.

I have checked and found there is no compatibility issue like explained in the the thread :

As this Application is working fine in my Development Environment.

Earlier it was also working in the Quality Environment but now getting the same error in Quality, the one which I am getting in the Production.

It is explaining some iView not found, the name "xapps.analytics.ds_par.core" In the Configuration manual we have opened the permission for this.

Kindly provide your inputs to investigate. I have checked the Corresponding services they are working fine.

Trace :

#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: iView not found: xapps.analytics.ds_par.core

at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1937)

at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:222)

at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)

at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)

at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:488)

at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)

at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)

at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)

at java.security.AccessController.doPrivileged(Native Method)

at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Regards,

Amit Singh

[Former Member]

Hi Amit,

This specific error has also been seen in another post.

Have you checked the patch versions of your Java component?

check this note.

1397195

Kind regards,

Neil

[Former Member]

Hi Amit,

You would receive this error if certain configurations are not set up correctly. Please check to make sure all the steps mentioned in the 'Install & configuration guide' are complete. Also on service marketplace there is a document called 'Problem analysis guide'.

If you still feel this is an error, please open up a customer message with system connection to look into the system for more details. But typically the above documents should resolve the issue.

Regards,

Rohit