Skip to Content
author's profile photo Former Member
Former Member

RFC_ERROR_SYSTEM_FAILURE while opening Clock-in/out in ESS

Dear Gurus,

I am getting this short dump error while opening the clock-in/out option in ESS.

Regards,

Rajasekar

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Feb 20, 2009 at 04:07 AM

    Rajasekhar,

    please post the entire error

    Thanks

    Bala Duvvuri

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.

      Please contact your system administrator.

      The current application triggered a termination with a short dump., error key: RFC_ERROR_SYSTEM_FAILURE

      com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: The current application triggered a termination with a short dump., error key: RFC_ERROR_SYSTEM_FAILURE

      at java.lang.Throwable.<init>(Throwable.java:179)

      at java.lang.Exception.<init>(Exception.java:29)

      at com.sap.exception.BaseException.<init>(BaseException.java:131)

      at com.sap.tc.cmi.exception.CMIException.<init>(CMIException.java:65)

      at com.sap.tc.webdynpro.progmodel.model.api.WDModelException.<init>(WDModelException.java:68)

      at com.sap.tc.webdynpro.modelimpl.rfcadapter.WDRFCException.<init>(WDRFCException.java:54)

      at com.sap.tc.webdynpro.modelimpl.rfcadapter.WDExecuteRFCException.<init>(WDExecuteRFCException.java:57)

      at com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException.<init>(WDDynamicRFCExecuteException.java:71)

      at com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException.<init>(WDDynamicRFCExecuteException.java:43)

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

      at com.sap.xss.hr.wtcor.fcoverview.FcOverview.ReadCalendar(FcOverview.java:232)

      at com.sap.xss.hr.wtcor.fcoverview.wdp.InternalFcOverview.ReadCalendar(InternalFcOverview.java:504)

      at com.sap.xss.hr.wtcor.fcoverview.FcOverviewInterface.ReadCalendar(FcOverviewInterface.java:135)

      at com.sap.xss.hr.wtcor.fcoverview.wdp.InternalFcOverviewInterface.ReadCalendar(InternalFcOverviewInterface.java:481)

      at com.sap.xss.hr.wtcor.fcoverview.wdp.InternalFcOverviewInterface$External.ReadCalendar(InternalFcOverviewInterface.java:549)

      at com.sap.xss.hr.wtcor.vcoverview.VcOverview.onBeforeOutput(VcOverview.java:278)

      at com.sap.xss.hr.wtcor.vcoverview.wdp.InternalVcOverview.onBeforeOutput(InternalVcOverview.java:924)

      at com.sap.xss.hr.wtcor.vcoverview.VcOverviewInterface.onBeforeOutput(VcOverviewInterface.java:156)

      at com.sap.xss.hr.wtcor.vcoverview.wdp.InternalVcOverviewInterface.onBeforeOutput(InternalVcOverviewInterface.java:302)

      at com.sap.xss.hr.wtcor.vcoverview.wdp.InternalVcOverviewInterface$External.onBeforeOutput(InternalVcOverviewInterface.java:414)

      at com.sap.pcuigp.xssfpm.wd.FPMComponent.callOnBeforeOutput(FPMComponent.java:603)

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

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

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

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

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

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

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

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

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

      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:753)

      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:276)

      at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)

      at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)

      at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

      at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

      at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:70)

      at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:818)

      at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)

      at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1288)

      at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)

      at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:548)

      at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:592)

      at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:864)

      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)

      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)

      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)

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

      at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)

      at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

      at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

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

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

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

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

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

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

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

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

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

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

      Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: The current application triggered a termination with a short dump., error key: RFC_ERROR_SYSTEM_FAILURE

      at java.lang.Throwable.<init>(Throwable.java:179)

      at java.lang.Exception.<init>(Exception.java:29)

      at com.sap.aii.util.misc.api.BaseException.<init>(BaseException.java:96)

      at com.sap.aii.proxy.framework.core.FaultException.<init>(FaultException.java:34)

      at com.sap.aii.proxy.framework.core.SystemFaultException.<init>(SystemFaultException.java:29)

      at com.sap.aii.proxy.framework.core.BaseProxyException.<init>(BaseProxyException.java:39)

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

      at com.sap.xss.hr.wtcor.time_event_corr_adaptivemodel.TimeEventCorrAdaptiveModel.ptcor_Uia_Weekly_Calendar(TimeEventCorrAdaptiveModel.java:410)

      at com.sap.xss.hr.wtcor.time_event_corr_adaptivemodel.Ptcor_Uia_Weekly_Calendar_Input.doExecute(Ptcor_Uia_Weekly_Calendar_Input.java:137)

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

      ... 60 more

  • author's profile photo Former Member
    Former Member
    Posted on Feb 20, 2009 at 05:38 AM

    Hi

    Dump says RFC Failure error.

    Could you check the intial SPRO level settings of check in-out applications of ESS means usecases.....etc .

    Rgads

    -SS

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 20, 2009 at 10:23 AM

    check the calendar settings for the rule group, Go to configure calendar for clock in clock out

    in ptcor. This will solve it

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 25, 2009 at 12:27 PM

    Thanks, there was some issue in rule groups....finally resolved

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.