ESS Absence request  Error : Lock Exception

Hi,
     When a user is trying the absence request application , she is getting the following error, she is the only user getting the error.
We did a server restart but that didn't solve the problem.Please suggest
#2#sap.com/pb/PageBuilder#com.sap.tc.webdynpro.services.session.LockException: Thread SAPEngine_Application_Thread[impl:3]_36 failed to acquire exclusive lock on client session ClientSession(id=(J2EE258694500)ID0000822451DB11319429603123595159End_1457644797). Existing locks: LockingManager(ThreadName:SAPEngine_Application_Thread[impl:3]_36, exclusive client session lock: ClientSessionLock(SAPEngine_Application_Thread[impl:3]_35), shared client session locks: ClientSessionSharedLockManager([]), app session locks: ApplicationSessionLockManager([]), current request: sap.com/pb/PageBuilder).Hint: Take a thread dump of the server node to find the blocking thread that causes the problem.
     at com.sap.tc.webdynpro.clientserver.session.ClientSession$LockingManager.lock(ClientSession.java:1511)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:233)
     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.doGet(DispatcherServlet.java:46)
     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: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:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Hi,
    Have you deleted the locks from system administration->Monitoring and under portal check object locking. see if there are any locks and see if you could delete the locks.
If the system is hanged you can restart the server0 (or server<n>) node to resolve the issue, but the issue may recur. Permanent solution is described in the note 1234847. There is a ppt attached to the note, you can proceed as described there.
Cheers!!!
Umang

Similar Messages

  • ESS Leave Request - Error while creating a leave record

    Hi Friends,
      Some of the ESS leave request(not workflow) has gone into error when the system tryies to create a leave record in background. I can view these error request using the report RPTARQDBVIEW. This happens when the background program(PTARQPOST) tries to create a leave record. In some cases  the status of the leave request is set to error(the status attribute of the container element(Req) has the value Error),but we are not able to find what is actual error.Is there any log where we can check what is the problem? Please advice.

    May be
    Internally the pernr might not be locked or some one may be maintaing the pernr for whom you are trying to post.

  • Team Calendar in ESS Leave Request (Error)

    Hello,
      we are configuring the Leave request in ESS and MSS in the portal (EP 7.0, ECC 6.0, latest release). The Leave Request process and application, Time accounts and Workflows all working fine and the customizing is done in the IMG.
      Only under ESS -> Leave Request -> Team Calendar we are getting this Error:
    java.lang.Exception: No Views found: Missing customizing
         at com.sap.xss.ser.tecl.fc.FcTeamCalendar._checkData(FcTeamCalendar.java:799)
         at com.sap.xss.ser.tecl.fc.FcTeamCalendar._getData(FcTeamCalendar.java:751)
         at com.sap.xss.ser.tecl.fc.FcTeamCalendar.initialReadData(FcTeamCalendar.java:385)
         at com.sap.xss.ser.tecl.fc.wdp.InternalFcTeamCalendar.initialReadData(InternalFcTeamCalendar.java:319)
         at com.sap.xss.ser.tecl.fc.FcTeamCalendarInterface.initialReadData(FcTeamCalendarInterface ....etc.
    I have maintained the Customzing in IMG for Team Calendar as the following:
    00000001     SAP Standard     01.01.1800     31.12.1999     Approval Mode     View Group (MSS)     MSS_LEA_EE
    00000001     SAP Standard     01.01.1800     31.12.1999     Attendance Overview     View Group (MSS)     MSS_LEA_EE
    00000001     SAP Standard     01.01.1800     31.12.1999     Administrator Mode     View Group (MSS)
    00000001     SAP Standard     01.01.1800     31.12.1999     Request Mode     View Group (MSS)     ESS_LEA_EE
    00000001     SAP Standard     01.01.1800     31.12.1999     Team View Mode     View Group (MSS)
    Would you please help?
    Many Thanks and Regards,
    Nazih

    Hi Bryan,
    1. First of all make sure that the Internet Graphic Server is activated + up and running on your SAP ERP System (see also SAP Note  704604)
    2. Then you have to set the Customizing Parameters for the Team Calendar in IMG (SAP ERP System):
    a. Tcode: PTARQ -> Customizing
    b. Working Time -> Team Calendar
    c. Node Create Rule Group -> Example: 00000001 (SAP Standard)
    d. Node Adjust WEBMO Feature -> Assign all Nodes to your Rue Group
    e. Node Spec. Absecne to be displayed -> Here i assume you have set up the Leave Request Process and WF already, so you only need to assign this to your Rule Group:
    Example.
    00000001     SAP Standard     01     0100     Leave     01.01.1800     31.12.9999
    f. Node Select Employee -->
    Here you need to set the Group of your Employee which should be displayed in the team calendar:
    Example.
    00000001     SAP Standard     01.01.1800     31.12.9999     Approval Mode     View Group (MSS)     MSS_LEA_EE
    00000001     SAP Standard     01.01.1800     31.12.9999     CATS Approval     View Group (MSS)     MSS_LCA_EE
    00000001     SAP Standard     01.01.1800     31.12.9999     Attendance Overview     View Group (MSS)     MSS_LEA_EE     PPOME_P
    00000001     SAP Standard     01.01.1800     31.12.9999     Administrator Mode     View Group (MSS)     MSS_LEA_EE     PPOME_P
    00000001     SAP Standard     01.01.1800     31.12.9999     Request Mode     View Group (MSS)     ESS_LEA_EE
    00000001     SAP Standard     01.01.1800     31.12.9999     Team View Mode     View Group (MSS)     MSS_LEA_EE     PPOME_P
    ---> Tipp: Check all Settings and Leave Types also with an HR Consultant before maintaing these in the ESS Customizing...
    Regards,
    Nazih

  • ESS Leave Request error - Processing of the service was terminated.

    Dear All,
    I am getting the below error on the leave request page in ESS
    A critical error has occured. Processing of the service was terminated. Unsaved data has been lost.
    Contact your system administrator.
    Index: 0, Size: 0
    java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    let me know what could be the reason for this error?
    Thanks

    Suresh,
    Please search in scn this has been discussed many times
    Thanks
    Bala Duvvuri

  • HTTP web request error (Web exception for remote server)

    To whom it may concern,
    I have recently applied a few patches for my client's server for IE9 but then one application starts to malfunction right after upgrade return successful. The program affected is CyberTech player which make use of Microsoft Silverlight. 
    My client currently uses Wind 2008 R2 x64, patches applied are below:
    MS13-009-IE9-Windows6.1-KB2792100-x64
    MS13-010_IE9-Windows6.1-KB2797052-x64-sp1
    MS13-021_IE9-Windows6.1-KB2809289-x64
    MS13-028IE9-Windows6.1-KB2817183-x64
    MS13-037_IE9-Windows6.1-KB2829530-x64
    MS13-038_IE9-Windows6.1-KB2847204-x64
    MS13-047_IE9-Windows6.1-KB2838727-x64
    MS13-069_IE9-Windows6.1-KB2870699-x64
    Please let me now if any further information is needed.
    Your prompt response will be much appreciated.

    Hi,
    Based on your description, I would like to suggest you try to uninstall and reinstall the latest version of Microsoft Silverlight.
    http://www.microsoft.com/silverlight/
    I also would like to suggest you update the CyberTech player so that it can be compatible with this update.
    Meanwhile, the http web request error was caused by IE itself:
    1. Improperly install or configure updates
    2. Security website authentications issue
    3. IE settings
    You may try the following steps to check the issue:
    1. Run IE with no add-ons. Click Start -> All Programs -> Accessories -> System Tools -> Internet Explorer (with no add-ons). 
    2. Try to use compatibility mode (go to tools --> Compatibility View Settings) to check the issue.
    For further research, it would be kind of you to capture a screenshot of the error page.
    Hope it helps.
    Regards,
    Blair Deng
    Blair Deng
    TechNet Community Support

  • ESS Leave Request error when launched from the portal

    Hi guys
    When i try to launch the Leave request from ESS tab in portal i am getting the following error
    I have checked the backend and i can process a leave request from there. It is failing on the portal side.
    A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
    Please contact your system administrator.
    Index: 0, Size: 0  
    java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
         at java.util.ArrayList.RangeCheck(ArrayList.java:507)
         at java.util.ArrayList.get(ArrayList.java:324)
         at com.sap.aii.proxy.framework.core.JcoBaseList.get(JcoBaseList.java:268)
         at com.sap.aii.proxy.framework.core.AbstractList.get(AbstractList.java:230)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCList.get(DynamicRFCList.java:281)
         at com.sap.tc.webdynpro.progmodel.context.Node$ModelElementList.getElement(Node.java:2549)
         at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:621)
         at com.sap.tc.webdynpro.progmodel.context.Node.setLeadSelection(Node.java:753)
         at com.sap.xss.hr.lea.form.FcForm.setLeadSelectionForSubtype(FcForm.java:700)
         at com.sap.xss.hr.lea.form.FcForm.setVisibility(FcForm.java:943)
         at com.sap.xss.hr.lea.form.FcForm.prepareCommand(FcForm.java:308)
         at com.sap.xss.hr.lea.form.wdp.InternalFcForm.prepareCommand(InternalFcForm.java:2041)
         at com.sap.xss.hr.lea.form.FcFormInterface.prepareCommand(FcFormInterface.java:116)
         at com.sap.xss.hr.lea.form.wdp.InternalFcFormInterface.prepareCommand(InternalFcFormInterface.java:1887)
         at com.sap.xss.hr.lea.form.wdp.InternalFcFormInterface$External.prepareCommand(InternalFcFormInterface.java:1983)
         at com.sap.xss.hr.lea.form.edit.VcFormEdit.onInit(VcFormEdit.java:299)
         at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEdit.onInit(InternalVcFormEdit.java:1084)
         at com.sap.xss.hr.lea.form.edit.VcFormEditInterface.onInit(VcFormEditInterface.java:165)
         at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEditInterface.onInit(InternalVcFormEditInterface.java:204)
         at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEditInterface$External.onInit(InternalVcFormEditInterface.java:280)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)

    This error occurs due to the following customisaton, Please
    check this :
    Check the Feature WEBMO is activated or not?
    Is the pernr assigned correctly?
    Please can you check if the Pernr used
    has correct information like It0105 etc, also the rules are
    correctly defined.
    For the Employee, First of all check the Period Work Schedule also
    the Quotas of the pernr needs to maintained in 2006, Please do
    this customisation and it should solve the issue.
    Maintain the absence quota in the IT2006 and then try once.
    Also make sure that the Settings in Webmo and PTARQ etc all is done
    The pernr belongs to the a Rule and have absences defined for him.

  • ESS Leave Request Error

    Hi Experts,
    We have implemented ESS in our organisation.
    In the leave request view i am getting the following error.
    For ex : If the leave request pending is 10.
    If i approved 1 it should reduce to 9 .....Its getting refreshed as 9 in R/3end but in the portal page its remains the same(Showing pending request : 10)
    Can anyone pls throw some light on this issue.
    Thanks in Advance,
    Dharani

    Hello,
    Please, I have the same issue!
    How did you resolve this problem?
    Thanks in advance

  • ESS deleting an Absence request before approving it.

    Hello,
    I have problems stopping the ESS Absence Request workflow after the user deletes it before the manager approves.
    Reproduction scenario:
    - The requestor creates an Absence request.
      ... the workflow (a copy of WS12300111) is instantiated
      ... the manager of the requestor gets a work item
    Now the requestor decides to delete the absence request...
    - Requestor deletes the absence request.
      The user now gets the information message:
      ... the ESS application now tries to complete (FM: <b>SAP_WAPI_WORKITEM_COMPLETE</b>)  the Work item of the manager.
      No administrator found for the task
      (By debugging, I found out that this was message 5W 141.)
    The <b>result</b> is that the request document is ended with <b>status WITHDRAWN</b>, which is correct, however the workflow has still a READY work item for the manager which he cannot start anymore.
    Analysis:
    The error message is a little bit weird, because it actually ment that the requestor is not an agent for the work item of the manager.
    I could solve this problem by giving the requestors more authorization. When I added SAP_ALL to the requestor, the error does not occur.
    The transition table determines:
    Documentstatus: SENT
    Status transition: DELETE
    Workflow control: CONTINUE Continue Workflow
    ...that's why it start FM: SAP_WAPI_WORKITEM_COMPLETE
    I hope you have an answer to my problem.
    Kind regards,
    Alwin van de Put
    (I expected that ESS would make use of events for terminating work items in stead of using SAP_WAPI_WORKITEM_COMPLETE.)

    Hello Ravi,
    Thank you for answering.
    The standard task is a General Task.
    The main problem is, that the agent determined in the step (in my case: Expression: &AGENT_0001.AGENTS&) is not the one who will complete the task.
    This is the case when the Requester deletes (withdraw) the absence request, than the ESS function module tries to complete the work item of the Manager with the user of the Requester.
    We could solve this problem by giving all requesters the following rights:
    S_CODE id TCD field SWIA.
    But we don't want to give all users rights to transaction SWIA.
    Kind regards,
    Alwin.

  • Axis adapter : Bad Request error

    Hi,
    I have a File to SOAP scenario (PI 7.0) where I am using AXIS adapter in the receiver SOAP adapter for NTLM authorisation. In the xml that I am trying to post, i have characters like &amp; because of which I am getting a Bad Request error. Is there a way to resolve this? thanks!
    Regards
    Pushpinder

    In file sender channel, i am using binary mode, so no encoding specified.
    I see the error in the receiver SOAP adapter -
    Error Axis: error in invocation: (400)Bad Request
    Error Exception caught by adapter framework: (400)Bad Request
    Error MP: Exception caught with cause (400)Bad Request
    Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: (400)Bad Request: (400)Bad Request.
    Error The message status set to NDLV.

  • Error Not enough quota 30 for attendance/absence in ESS Leave Request

    Good Morning
    I am trying to create a "Leave Request" using ESS with  "Floating Days".  It has a cuota manual.  When trying to create the leave request in ECC all works fine, but when trying to create the same leave request in ESS the following error occurs:
    Not enough quota 30 for attendance/absence 0261 on 05.03.2008 for personnel no. 20001140
    Some can help me?
    Best Regards,
    Wilman

    Hi,
    I would suggest the following :
    Step1: Check your IT 2006/IT 2007 for your Absence and Attendance Quotas.
    Step 2: You can also verify the same information using the PT50 transaction ( quota Overview)
    Step 3: By doing the above you ensure that the person has the required quotas.
    Step4: logon to ESS and do the request for leave.if it does not let you, then there is some problem in the config in the ESS. I cannot tell you this from top of my head. We need to look into the portal to see what exactly the problem.
    regards
    Vijay

  • Error while accessing ESS Loan Request.

    Hi Experts,
    While accessing ESS Loan request for Country grouping 40 India am getting below mentioned error saying that 500 Internal Server Error.
    I have maintained the settings for Leave request and maintained Infotype 45 Loans for employee.
    But it is giving the below mentioned error.
    500   Internal Server Error
      SAP NetWeaver Application Server 7.00/Java AS 7.00 
    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).
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.dictionary.runtime.DdException: Type com.sap.model.loan.types.Extdl does not exist
        at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
        at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:596)
        at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:296)
        at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:94)
        at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
        ... 74 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2)
    Version null
    DOM version null
    Client Type msie8
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0205.20100813133935.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:28:44[UTC], changelist=91834, host=pwdfm256), build date: Fri Feb 11 16:31:03 IST 2011
    J2EE Engine 7.02 PatchLevel 91789.
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_28-b03, vendor: Sun Microsystems Inc.
    Operating system Windows Server 2008 R2, version: 6.1, architecture: amd64
    Session & Other
    Session Locale en_US
    Time of Failure Fri Feb 18 11:17:24 IST 2011 (Java Time: 1298008044828)
    Web Dynpro Code Generation Infos
    sap.com/pb
    SapDictionaryGenerationCore 7.0205.20100813133727.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:18:36[UTC], changelist=91776, host=PWDFM256.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0205.20100813133727.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:18:40[UTC], changelist=91776, host=PWDFM256.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0205.20100813133737.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:08:53[UTC], changelist=91781, host=PWDFM256.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0205.20100813133926.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:22:53[UTC], changelist=91832, host=PWDFM256.wdf.sap.corp)
    SapMetamodelCommon 7.0205.20100813133815.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:09:28[UTC], changelist=91800, host=PWDFM256.wdf.sap.corp)
    SapMetamodelCore 7.0205.20100813133815.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:09:25[UTC], changelist=91800, host=PWDFM256.wdf.sap.corp)
    SapMetamodelDictionary 7.0205.20100813133729.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:16:20[UTC], changelist=91777, host=PWDFM256.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0205.20100813133929.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:20:37[UTC], changelist=91833, host=PWDFM256.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0205.20100813133935.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:30:09[UTC], changelist=91834, host=pwdfm256)
    SapWebDynproGenerationCore 7.0205.20100813133926.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:22:57[UTC], changelist=91832, host=PWDFM256.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0205.20100813133935.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:30:09[UTC], changelist=91834, host=pwdfm256)
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.sap.model.loan.types.Extdl could not be loaded: com.sap.dictionary.runtime.DdException: Type com.sap.model.loan.types.Extdl does not exist
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:268)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:231)
         at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:940)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:141)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createBLCComponentUsage(FPMComponent.java:761)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
         at com.sap.ess.in.loan.overview.VcOverviewESS.onInit(VcOverviewESS.java:244)
         at com.sap.ess.in.loan.overview.wdp.InternalVcOverviewESS.onInit(InternalVcOverviewESS.java:611)
         at com.sap.ess.in.loan.overview.VcOverviewESSInterface.onInit(VcOverviewESSInterface.java:162)
         at com.sap.ess.in.loan.overview.wdp.InternalVcOverviewESSInterface.onInit(InternalVcOverviewESSInterface.java:144)
         at com.sap.ess.in.loan.overview.wdp.InternalVcOverviewESSInterface$External.onInit(InternalVcOverviewESSInterface.java:220)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
         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:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:876)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:222)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1355)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:357)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
         at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:597)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:870)
         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:333)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         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: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)
    Caused by: com.sap.dictionary.runtime.DdException: Type com.sap.model.loan.types.Extdl does not exist
         at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
         at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:596)
         at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:296)
         at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:94)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:260)
         ... 72 more
    Please suggest me the solution for this.
    Regards,
    Ksanj.

    Please   check that the ESS/ERP packages fit together according to
    the page
    https://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACK+
    MISMATCH+ISSUES
    Please check again the componentinfo and the SPlevels of the testlandsca
    pe, that the same level is used on the prod landscape.
    So ensure you are on correct levels!

  • Portal Runtime Error : An exception occurred while processing a request

    Hello friends,
    After upgradation of my portal to the following patch level, SAP J2EE 6.20:
    <b>Portal Version :</b> EP 6 SP 2 patch 29 hotfix 0
    <b>Content Mgmt and Collaboration  version</b> : 6 SP2 patch 5
    i faced many performance related issues. Portal seems to be <b>very slow</b>. After logging in, most of the time I get 2 errors:
    <b>Either</b>
    <b>1></b> Iview remains blank.
    <b>Or
    2></b> Portal Runtime Error : An exception occurred while processing a request. Portal Runtime exception occured. Please check the System Log.
    But when I refresh that particular iview, it works fine.
    I went through the portal.log file (/usr/sap/PEP6/j2ee/j2ee_00/cluster/server/managers/log/portal/logs). And found <b>the root cause of most of the exceptions as "com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found."</b>Aug 18, 2005 6:07:42 PM # PRT-Async 2          Fatal           Exception ID:06:07_18/08/05_0669
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/ACCContent/ACCContent.Roles/Company/R.Employee/W.MyWork/P.MyWork.DesktopTools/I.Contacts
    Component class : com.sapportals.portal.prt.pom.RootComponentNode
    User : tempuser
            at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:853)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:311)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
            at java.lang.Thread.run(Thread.java:479)
    Caused by: com.sapportals.portal.prt.component.PortalComponentException: PortalComponentException
            at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:153)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
            at java.lang.Thread.run(Thread.java:479)
    Caused by: com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found.
            at com.inqmy.services.servlets_jsp.server.ServletContextFacade.loadServletLocal(ServletContextFacade.java:3660)
            at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:81)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:275)
            at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.include(RequestDispatcherImpl.java:384)
            at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:144)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
            at java.lang.Thread.run(Thread.java:479)
    <b>Help needed.(</b>as i am helpless now.)
    Regards,
    Nilz

    Anthony,
      I had check it. It was correct. But the thing when I saw in the component Inspector of portal, my iview did not appear.
    I created like this
             project-> rightclick->   export-> par ->selecting project-> givint protal password-> and finish.
    The NW didn't give any error, but the par file didn't appear in the portal componet Inspect.
    but the par file is  created in the NW studio Navigation bar.
      Let me know any help regarding this
    thanks
    venkat

  • Request Error - The server encountered an error processing the request. The exception message is 'Unable to retrieve the requesting user's identity

    I'm trying to create an Orchestrator Connector in Service manager, It is not going well.
    The most resent alarm is
          <p class="heading1">Request Error</p>
          <p>The server encountered an error processing the request. The exception message is 'Unable to retrieve the requesting user's identity.'
       For the Orchestrator Web Service URL: I have http://Server_Name:81/Orchestrator2012/Orchestrator.svc/
    I created a new Run As account that uses Windows authentication, when I test the connection thats the alarm I get.
    Paul Arbogast

    Hi,
    Can you access the URL using a browser? Does it work with the credentials used for the RunAs account?
    Strange error message though - are the account you are running the console with, present in the SCSM CMDB?
    Regards
    //Anders
    Anders Asp | Lumagate | www.lumagate.com | Sweden | My blog: www.scsm.se

  • About a exception: Invalid request., error key: RFC_ERROR_SYSTEM_FAILURE

    Hello:
       <b>I am using an adaptive RFC model inside a Web Dynpro Application.i encountered  a exception:</b>
       com.sap.tc.webdynpro.
    modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Invalid request., error key: RFC_ERROR_SYSTEM_FAILURE
            at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
            at com.sap.shineway.InputField.exec(InputField.java:169)
            at com.sap.shineway.wdp.InternalInputField.exec(InternalInputField.java:291)
            at com.sap.shineway.ShineWay_InputView.onActionGoCreate(ShineWay_InputView.java:192)
            at com.sap.shineway.wdp.InternalShineWay_InputView.wdInvokeEventHandler(InternalShineWay_InputView.java:248)
            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(ApplicationSessionMessag
    eListener.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(AccessController.java:214)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Invalid request., error key: RFC_ERROR_SYSTEM_FAILURE
    what it means??
    thank you
                            yours
                                           zunxian.cheng

    Zunxian,
    The error message "Invalid request., error key: RFC_ERROR_SYSTEM_FAILURE" makes it seem like there's something wrong with the request. You generally get an error message of the group  RFC_ERROR_SYSTEM_FAILURE when there's something wrong with the backend system, or when you send a request that makes it dump.
    What Bapi/RFM are you trying to call?
    have a look at <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/f6/daea401675752ae10000000a155106/content.htm">this explaination of different JCO Exceptions</a> for more information.
    Regards
    Mattias

  • Error after second level approval in ESS leave request

    Hi Experts
    I am using custom workflow for Ess Leave request process which is copied from WS21500001.
    I have added custom class methods to change status from approved to sent.
    Then another method i have set next appovaer.
    The problem i m facing is that I am getting an error on portal after second approval approves the request.
    i.e Field syomol has not been assigned yet.
    from st22 i found its generating from
    Include LPT_ARQ_REQUEST_UIAF06  - Form   execute_approver_update
    By debugging i found that Its not getting next approval with status T as there is only first approval with status 'A'
    This results in unassigned field symbol. and then error.
    Please help me resolve this issue.
    Please confirm why next approver is not found in method.

    Hi All
    Thanks for your reply.
    I checked why it was giving a dump.
    This execute_approver_update subroutine takes approval data from table ptreq_approver .
    I filled this with resp actor id after request is approved and status is changed to sent.
    For every emp its unique actor id is saved in ptreq_actor table agaist his pernr.
       SELECT SINGLE actor_id FROM PTREQ_ACTOR INTO actor_id WHERE objid = nextApprover_pernr.
        wa_appr-mandt = sy-mandt.
        wa_appr-request_id = Request_ID. "Req.requestID ( from Workflow )
        wa_appr-version_no = version_no. "Req.Version ( from Workflow )
        wa_appr-seqnr = seqnr. "Same as version no but in char
        wa_appr-approver_ins = actor_id. "Employee actor id from ptreq_actor
        wa_appr-status = 'T'. "Manual
        append wa_appr to it_appr.
        INSERT PTREQ_APPROVER FROM TABLE it_appr .
        commit work and wait.
    This resolved my issue.
    Thanks

Maybe you are looking for

  • Cost of restore 10.3 disk

    what is the cost of a restore disk for Panther 10.3

  • How to get out of tex edit mode with a single button?

    Hey, Is there a way to escape from text edit mode with a single click or button? So far I always hit CTRL+Enter, then V and then I click away from the canvas so that the paragraph ain't higlighted no more. But thats a pain in the butt! Cant there be

  • Member load error from EIS

    I'm loading data into essbase from eis. After member load following error is given EssbaseAPI: You have been logged out due to inactivity or explicitly by the administrator. When I try the same thing using user 'admin' it works fine. but the error is

  • OSX Yosemite 10.10.2 Server - DNS Issue

    I am trying to set up Yosemite server a home server for the family - 5 macs.  I have a public domain name which is forwarded to a Draytek ADSL router.  The Mac Mini running Yosemite (server) sits behind the Draytek on a private network (192.168.6.X).

  • Music is missing in iTunes.  HELP!

    I came to work yesterday, opened iTunes and all of my music is gone.  I've rebooted, searched everywhere and it's nowhere to be found.  HELP!!