on 01-12-2007 11:17 AM
Hello,
Please can someone assist with this problem?
I am trying to test the ReportLaunchpadPcdApp Application directly from the Web Dynpro console
However I have come across 2 warning messages associated with the application:
Failed to read resource bundle "com/sap/xss/fin/lpa/model/types/Fpb_Rl_S_Objtype.dtstructure" for locale "en". Check trace for details.
Failed to read resource bundle "com/sap/xss/fin/lpa/model/types/Fpb_Rl_S_Objtype.dtstructure" for locale "en_US". Check trace for details.
When i run the Launchpad application i get the following error message:
com.sap.tc.webdynpro.progmodel.controller.MessageManager$AbortMessageManagerException: Role: null instance: null NOT_FOUND
at com.sap.tc.webdynpro.progmodel.controller.MessageManager.raiseException(MessageManager.java:430)
at com.sap.xss.fin.lpa.reportlaunchpad.BLpaReportLaunchpadComp.LPAInit_Start(BLpaReportLaunchpadComp.java:684)
at com.sap.xss.fin.lpa.reportlaunchpad.wdp.InternalBLpaReportLaunchpadComp.LPAInit_Start(InternalBLpaReportLaunchpadComp.java:704)
at com.sap.xss.fin.lpa.reportlaunchpad.BLpaReportLaunchpadCompInterface.LPAInit_Start(BLpaReportLaunchpadCompInterface.java:217)
at com.sap.xss.fin.lpa.reportlaunchpad.wdp.InternalBLpaReportLaunchpadCompInterface.LPAInit_Start(InternalBLpaReportLaunchpadCompInterface.java:649)
... 40 more
Help?
Many thanks in advance
Jo-lize
Hi Jo-lize,
This is a MSS Application which cannot work stand alone.
Check this link
http://help.sap.com/saphelp_erp2005/helpdata/en/b6/9055408f611059e10000000a155106/frameset.htm
So you need to call it from the Portal or from Stanalone MSS Areapage
If you have not configured the reports, check the following links 'Reports in the Launchpad' section to add example entries. http://help.sap.com/saphelp_erp2005/helpdata/en/e4/2eb47fed444bb885c244f5ff979f16/frameset.htm
Regards,
Shubham
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shubham
Thanks you for your help, I have used the link that you provided and every time I click on one of the links on the page I get the following error message:
The initial exception that caused the request to fail was:
Com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must not be triggere with an URL when running in portal. Use portal navigation instead to navigate to the another application.
Any ideas why this is happening?
Thanks
Jo-lize
Hi Shubham
<u>
Here is the error :</u> Thanks again for all your help.
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponentWindowInterfaceView.wdFirePlugExitPlug(InternalFPMComponentWindowInterfaceView.java:145)
at com.sap.pcuigp.xssfpm.wd.Navigation.navigate(Navigation.java:304)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalNavigation.navigate(InternalNavigation.java:124)
... 36 more
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-05:15:08:24[UTC], changelist=413534, host=pwdfm101), build date: Sun Nov 26 11:05:58 SAST 2006
J2EE Engine 7.00 patchlevel
Java VM Java HotSpot(TM) Server VM, version:1.4.2_11-b06, vendor: Sun Microsystems Inc.
Operating system Linux, version: 2.6.9-22.ELsmp, architecture: i386
Session & Other
Session Locale en
Time of Failure Thu Jan 18 10:12:27 SAST 2007 (Java Time: 1169107947828)
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponentWindowInterfaceView.wdFirePlugExitPlug(InternalFPMComponentWindowInterfaceView.java:145)
at com.sap.pcuigp.xssfpm.wd.Navigation.navigate(Navigation.java:304)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalNavigation.navigate(InternalNavigation.java:124)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.navigate(FPMComponent.java:990)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.navigate(FPMComponent.java:973)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.navigate(FPMComponent.java:1130)
at com.sap.xss.ser.xssmenu.vc.areagroup.VcXssMenuAreaGroup.gotoAreaPage(VcXssMenuAreaGroup.java:204)
at com.sap.xss.ser.xssmenu.vc.areagroup.wdp.InternalVcXssMenuAreaGroup.gotoAreaPage(InternalVcXssMenuAreaGroup.java:235)
at com.sap.xss.ser.xssmenu.vc.areagroup.AreaGroupViewStatic.onActionGotoAreaPage(AreaGroupViewStatic.java:361)
at com.sap.xss.ser.xssmenu.vc.areagroup.wdp.InternalAreaGroupViewStatic.wdInvokeEventHandler(InternalAreaGroupViewStatic.java:226)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.