cancel
Showing results for 
Search instead for 
Did you mean: 

ESS Problem

MarkusKlein
Active Contributor
0 Kudos

Hello everybody,

i have installed the ESS Business Package to our EP6, when trying to run one of the installed iviews/pages in preview mode i get the following exception

com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Ausnahmebedingung "PROFILE_NOT_FOUND" ausgelöst, error key: RFC_ERROR_SYSTEM_FAILURE

at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)

at com.sap.xss.ser.xssmenu.fc.ModelHandler.onInit(ModelHandler.java:204)

at com.sap.xss.ser.xssmenu.fc.wdp.InternalModelHandler.onInit(InternalModelHandler.java:378)

at com.sap.xss.ser.xssmenu.fc.FcXssMenu.onInit(FcXssMenu.java:253)

at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenu.onInit(InternalFcXssMenu.java:422)

at com.sap.xss.ser.xssmenu.fc.FcXssMenuInterface.onInit(FcXssMenuInterface.java:169)

at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface.onInit(InternalFcXssMenuInterface.java:368)

at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface$External.onInit(InternalFcXssMenuInterface.java:505)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:740)

at com.sap.xss.ser.xssmenu.vc.header.VcXssMenuHeader.onInit(VcXssMenuHeader.java:196)

at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeader.onInit(InternalVcXssMenuHeader.java:216)

at com.sap.xss.ser.xssmenu.vc.header.VcXssMenuHeaderInterface.onInit(VcXssMenuHeaderInterface.java:162)

at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeaderInterface.onInit(InternalVcXssMenuHeaderInterface.java:139)

at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeaderInterface$External.onInit(InternalVcXssMenuHeaderInterface.java:215)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:464)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:353)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:180)

at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:105)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)

at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:346)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:352)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)

at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)

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

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

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

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

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

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

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

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

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

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

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

at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)

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:94)

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

Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Ausnahmebedingung "PROFILE_NOT_FOUND" ausgelöst, error key: RFC_ERROR_SYSTEM_FAILURE

at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)

at com.sap.pcuigp.xssutils.xssmenu.model.MenuModel.hrxss_Ser_Getmenudata(MenuModel.java:171)

at com.sap.pcuigp.xssutils.xssmenu.model.Hrxss_Ser_Getmenudata_Input.doExecute(Hrxss_Ser_Getmenudata_Input.java:137)

at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)

... 44 more

any ideas?

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Markus,

Are you sure that your SSO connectivity works? I would re-check your ITS/SAP Backend connectivity.

Also, check your ESS configuration in relation to the guide on blog.

Regards,

James

MarkusKlein
Active Contributor
0 Kudos

Hello James,

im not using the ITS solution, but the new webdynpro one.

Regarding the SSO connection. There is indeed a problem with it. When i try to test the JCos i have created using logon ticket i get the following error message:

[code]

com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Es wurde ein nicht interpretierbares SSO-Ticket empfangen [/code]

Es wurde ein nicht interpretierbares SSO-Ticket empfangen = something like 'A non interpretable SSO-Ticket was received'

MarkusKlein
Active Contributor
0 Kudos

Hello,

the SSO connection is working now, but the problem provided above remains. Thus its more of a ESS then a common Portal problem. Im sure something is wrong on the backend side (ERP) of the ESS-scenario.

Any ideas, hints what could be wrong?

MarkusKlein
Active Contributor
0 Kudos

The exception PROFILE_NOT_FOUND comes due to a missing entry in table 'tcats' at the backend system. After adding the entry 'ESS' using the IMG, i got it working.

Former Member
0 Kudos

Hello Markus

How did you solved the problem with 'non interpretable Ticket'? See my thread

Thanks for any hint.

Regards

Robert