BPC EPM_ADDIN_Launcher Broken after Restart

[Former Member]

We did a restart of our production BW system. This was to change a value for abap/heap_memory_dia. After the restart we began receiving reports of BPC no longer working from the web launch link. When one clicks on the link the following message is displayed.

Nothing else about the system was changed. I have no experience with BPC. Unfortunately this part of the system is not managed by us but we have inherited support for it on this issue. All other systems are functioning fine.

One clue that is strange to us is that the server url used in the connection of the excel login changed from working on port number 8000 to 8001.

https://fqdn:8001/sap/bpc (New working link)

http://fqdn:8000/sap/bpc (Old broken link)

[Former Member · Accepted solution]

Hi ,

You can verify the HTTP port configured for your ABAP system using transaction "SMICM".

Thanks,

Peter

[Former Member · Accepted solution]

I'm not entirely certain what all to look for but in drilling down through the HTTP plugin info everything looks good. If you have more details about what to look for let me know. Thanks for your help.

[Former Member · Accepted solution]

Hi Robert,

Did you look at the link I posted?

The first point in chapter 4.6 is SMICM, and you give points to the 2nd poster?

In the documents it clearly instruct you how to change from http to https, you will get more info by looking at that document.

Andy

[Former Member · Accepted solution]

Hi Andy,

Thanks for the reply. I did look at the document and saw where you were referring to. That does address one part of the issue I was curious about but does not address the lingering issue I posted more about below.

The most pressing issue at this point is that the SAP Portal that provides SSO for using AD credentials is not working consistently as it was deployed before the problem.

Before the error that occurred after the server restart all a person needed to do was click a desktop shortcut to the link:

[server]:[port]/PCNW10_SSO_WP/EPM_AddIn_Launcher

This would launch a window that would ask for their AD credentials and then fire up the BPC module in Excel.

As I mentioned below I redeployed an EAR file in accordance with this document given to us by SAP support during initial implementation. http://scn.sap.com/docs/DOC-20003

This fixed it so we no longer see the error screen in my first post but now see a 500 error that I posted below. This only happens if someone clicks on the link before going into the portal first.

The problem is essentially this. When someone clicks on the link on their desktop it is no longer prompting them to login with their AD credentials. The mechanism works though if they sign into the portal first with their AD credentials then click the link.

It's my guess that the token process is not complete but I'm not sure where/how it is broken.

Thanks again for all your help.

[Former Member]

So yesterday I redeployed an ear file on the Portal Server since this has been about fixing the SSO portion so that users can use their AD credentials.

After redeploying the ear file we now are somewhat back to what we had before. A link from the portal launches Excel with the addon. What is not working is if you click on the direct link it will fail with a 500 error. If you click on the link from the portal it works fine.

For some reason it is not kicking back to the portal in the absence of the logon ticket.

The error linked is below.

Cannot process an HTTP request to servlet [EPM_AddIn_Launcher] in [PCNW10_SSO_WP] web application. 
[EXCEPTION] 
java.lang.NullPointerException: while trying to get the length of a null array loaded from local variable 'c' 
at com.sap.csa.bpc.EPM_AddIn_Launcher.hasSSOCookie(EPM_AddIn_Launcher.java:170) 
at com.sap.csa.bpc.EPM_AddIn_Launcher.handleRequest(EPM_AddIn_Launcher.java:73) 
at com.sap.csa.bpc.EPM_AddIn_Launcher.doGet(EPM_AddIn_Launcher.java:41) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) 
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152) 
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38) 
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466) 
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210) 
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441) 
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430) 
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38) 
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) 
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81) 
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) 
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278) 
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) 
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81) 
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) 
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) 
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60) 
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) 
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) 
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27) 
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) 
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) 
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29) 
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) 
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) 
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26) 
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) 
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) 
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57) 
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) 
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) 
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43) 
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) 
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) 
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475) 
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269) 
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56) 
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122) 
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101) 
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)  

[former_member193143]

Hello Robert,

I don't know what exactly happens when we restart the production system. I don't have any idea if we restart the system the URL link will change or not. if its change their is way to get the new URL link

from BW system.

enter the t-code--> SICF -->Choose hierarchy type as services and execute

Next drill down default/host, choose EPM-BPC, then choose web and right click on it and then select "Test services" and give you credentials. see the below image as reference.

Regards,

Saida Reddy G

[former_member182709]

Robert, do you mean BPC Web URL https://fqdn:8001/sap/bpc/web is not working. Or you cannot log on EPM Add-in using https://fqdn:8001/sap/bpc.

Can you attach the detailed steps on reproducing the error.

Best regards,

Charlie

[Former Member]

The web launching for SSO stopped working like in the screenshot below but the direct link in the EPM addon still worked with SAP credentials but it required a sudden change in url. Two distinct but related issues at once.

[former_member182709]

If URL is sudden changed, you can check if the setting below selected to "switch to https" or "logon via https".

[Former Member]

Hi Robert,

Check the installation guide chapter 4.6 on page 27, make sure those are set up corretly.

SAP Business Planning and Consolidation 10.0, Version for SAP NetWeaver – SAP Help Portal Page

it is better to use https:\\ than http:\\

Andy