User unable to access Leave Request in Portal

Hello guys,
A user can't access the leave request via Enterprise Portal 7.0 - the view works perfectly with the other users thus the issue seems to be isolated to this particular user. IE version being used is IE 6.0 - so that shouldn't be the cause of the problem. Also, the roles have been cross-checked and synchronized with the other users who are able to access the Leave Request function. Yet, it appears the roles are correctly assigned
Could it be possible that this is a problem with the user's data? Which component should I also look into?
Thank you in advance!
Regards,
Jan

As for the IE patch problem, we're conducting an http-trace to check with this. But I see this as very unlikely, since the user also tried accessing it via a different workstation but the problem persists.
The 'resolution' for similar cases was to recreate a user account - even just a direct copy of the same user works. This could be an SAP application bug perhaps? The target is for a long term fix to the problem.
Thanks!
Regards,
Jan

Similar Messages

Error in accessing Leave request

Hi Guys,
We are implementing ESS - MSS. I m trying to access leave request I m getting following error.
I have maintened 105 0001 infotype. ie assigned user to the ess user. Also given Essuser to SAP_ALL authorization.
And also I maintained webmo feature for my employee and employee sub group.
this is error I m getting
A critical error has occured. Processing of the service was terminated. Unsaved data has been lost.
Contact your system administrator.
Broken delta link - object type = id = portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.13.ess.employee_self_service/com.sap.pct.erp.srvconfig.13.lea/com.sap.pct.erp.srvconfig.13.fpmapplications/com.sap.pct.erp.srvconfig.13.LeaveRequestEnhCE_13/com.sap.xss.config.fpmviews/BlockCale.
com.sap.xss.config.FPMInconsistentObjectException: Broken delta link - object type = id = portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.13.ess.employee_self_service/com.sap.pct.erp.srvconfig.13.lea/com.sap.pct.erp.srvconfig.13.fpmapplications/com.sap.pct.erp.srvconfig.13.LeaveRequestEnhCE_13/com.sap.xss.config.fpmviews/BlockCale.
     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:64)
     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObject(PcdObjectBroker.java:47)
     at com.sap.xss.config.domain.PersistentObjectManager.retrieveObjectInternal(PersistentObjectManager.java:106)
     at com.sap.xss.config.domain.PersistentObjectManager.retrieveRelatedObjects(PersistentObjectManager.java:172)
     at com.sap.xss.config.domain.PersistentObjectManager.retrieveObjectInternal(PersistentObjectManager.java:132)
     at com.sap.xss.config.domain.PersistentObjectManager.retrieveObject(PersistentObjectManager.java:80)
     at com.sap.xss.config.FPMRepository.retrieveObjectInternal(FPMRepository.java:83)
     at com.sap.xss.config.FPMRepository.retrieveObject(FPMRepository.java:66)
     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.initializeConfiguration(FcXssPcd.java:816)
     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.loadConfiguration(FcXssPcd.java:250)
It would be grate full If some body help me to resolve this issue.
Thanks in advance
Sanju.

This issue has already been resolved earlier. Take a look here:
leave application delta link
regards, Lukas

Unable to process leave request due to WORKFLOW Status in ERROR in ESS Portal.

Dear Experts,
I'm facing an issue with the leave request of an user. The user has applied leave a week ago but still it has not got auto approved.While analyzing the database of leave request in PTARQ, it has been found that the WORKFLOW STATUS is in ERROR and the DOCUMENT STATUS is in SENT condition.
Kindly help me in this case.
Please refer the screenshot below.
Thanks & Regards,
Surendhar

Hi surendha,
That particular leave request might have gone into error because of worklfow issue at the point of time.
You can simply check with workflow if any issue with workflow was there in that tenure , leave request was being raised,
Now solution is to delete the leave request from PTARQ which is in SENT status and workflow is errored out.
Also take that work item id and get it deleted by workflow consultant (T code SWI5).
Once that leave request/work item got deleted , ask user to again apply leave and it would go to manager for approval.
Once leave request is approved, leave request would be in Posted status and will get updated in IT 2001.
Hope it helps you,
Thanks.
Priya

Error in ESS while Accessing Leave Request

Dear All,
We are having the ESS in EP 7.0 and ECC 6.0, We have deployed the ESS components. Everything working fine for one User only,But for other users we are facing problem Leave Request. This is the error we are getting:::
com.sap.xss.config.FPMConfigurationException: Read of object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest failed.
*     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:92)*
*     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObject(PcdObjectBroker.java:47)*
*     at com.sap.xss.config.domain.PersistentObjectManager.retrieveObjectInternal(PersistentObjectManager.java:106)*
*     at com.sap.xss.config.domain.PersistentObjectManager.retrieveObject(PersistentObjectManager.java:80)*
*     at com.sap.xss.config.FPMRepository.retrieveObjectInternal(FPMRepository.java:83)*
*     at com.sap.xss.config.FPMRepository.retrieveObject(FPMRepository.java:66)*
*     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.initializeConfiguration(FcXssPcd.java:816)*
*     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.loadConfiguration(FcXssPcd.java:250)*
*     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcd.loadConfiguration(InternalFcXssPcd.java:178)*
*     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcdInterface.loadConfiguration(FcXssPcdInterface.java:138)*
*     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface.loadConfiguration(InternalFcXssPcdInterface.java:148)*
*     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface$External.loadConfiguration(InternalFcXssPcdInterface.java:240)*
*     at com.sap.pcuigp.xssutils.ccpcd.CcXssPcd.loadConfiguration(CcXssPcd.java:282)*
*     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcd.loadConfiguration(InternalCcXssPcd.java:184)*
*     at com.sap.pcuigp.xssutils.ccpcd.CcXssPcdInterface.loadConfiguration(CcXssPcdInterface.java:115)*
*     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface.loadConfiguration(InternalCcXssPcdInterface.java:124)*
*     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface$External.loadConfiguration(InternalCcXssPcdInterface.java:184)*
*     at com.sap.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:205)*
*     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXss.loadConfiguration(InternalCcXss.java:153)*
*     at com.sap.pcuigp.xssutils.ccxss.CcXssInterface.loadConfiguration(CcXssInterface.java:112)*
*     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface.loadConfiguration(InternalCcXssInterface.java:124)*
*     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface$External.loadConfiguration(InternalCcXssInterface.java:184)*
*     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:172)*
*     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:429)*
*     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)*
*     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)*
*     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)*
*     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:731)*
*     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:667)*
*     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.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)*
*     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:879)*
*     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:222)*
*     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1280)*
*     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)*
*     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:552)*
*     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:596)*
*     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:827)*
*     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:299)*
*     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:683)*
*     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)*
Caused by: com.sapportals.portal.pcd.gl.PermissionControlException: Access denied (Object(s): portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest)
*     at com.sapportals.portal.pcd.gl.PcdFilterContext.filterLookup(PcdFilterContext.java:421)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1177)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookupLink(PcdProxyContext.java:1282)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookup(PcdProxyContext.java:1229)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:996)*
*     at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:68)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:989)*
*     at com.sap.xss.config.pcd.PcdObjectBroker.getPcdContext(PcdObjectBroker.java:305)*
*     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:53)*
*     ... 69 more*
Please let me know what might be the problem, and y its not working for other ESS users.
Expecting solution and Ideas as soon as possible as its very are in crucial time.
Thanks
Ravi.S

This is a permission issue.
Please go to Content Admin> Portal C D> ...Provided by SAP> End User C> ESS> you will see the ESS object> Right click on it and select Permission and you will see the roles present on the right hand side.
Check it and save it.
Regards
Prashant

User unable to access OWA

User is unable to access OWA any pointers.. getting the below error pls Thanks
The item can't be opened because it's become corrupted.
Request
Url: https://ukexchange.abc.com:443/owa/lang.owa
User: Wes, Aurélia
EX Address: /O=abc/OU=London/cn=Recipients/cn=AWes
SMTP Address: [email protected]
OWA version: 14.3.123.3
Exception
Exception type: Microsoft.Exchange.Data.Storage.CorruptDataException
Exception message: Can't save invalid object Wes, Aurélia.
Call stack
Microsoft.Exchange.Data.Storage.ExchangePrincipal.Save()
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchLanguagePostLocally(OwaContext owaContext, OwaIdentity logonIdentity, CultureInfo culture, String timeZoneKeyName, Boolean isOptimized, String destination)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchLanguagePostRequestFromProxy(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.PrepareRequestWithoutSession(OwaContext owaContext, UserContextCookie userContextCookie)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.AcquireAndPreprocessUserContext(OwaContext owaContext, HttpRequest request)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.OwaRequestEventInspector.OnPostAuthorizeRequest(Object sender, EventArgs e)
System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Inner Exception
Exception type: Microsoft.Exchange.Data.DataValidationException
Exception message: The property value Aurélia Wes is invalid. The value can contain only 'a', 'b', 'c', 'd', 'e', 'f', 'g', 'h', 'i', 'j', 'k', 'l', 'm', 'n', 'o', 'p', 'q', 'r', 's', 't', 'u', 'v', 'w', 'x', 'y', 'z', 'A', 'B', 'C', 'D', 'E', 'F', 'G', 'H',
'I', 'J', 'K', 'L', 'M', 'N', 'O', 'P', 'Q', 'R', 'S', 'T', 'U', 'V', 'W', 'X', 'Y', 'Z', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9', '"', ''', '(', ')', '+', ',', '-', '.', '/', ':', '?', ' '.
Call stack
Microsoft.Exchange.Data.Directory.ADSession.Save(ADObject instanceToSave, IEnumerable`1 properties)
Microsoft.Exchange.Data.Storage.ExchangePrincipal.Save()

Hi,
We can use the New-MailboxRepairRequest cmdlet to detect and repair mailbox corruptions. For more information about it, please refer to:
http://technet.microsoft.com/en-us/library/ff625221(v=exchg.141).aspx
Hope it helps.
Thanks,
Winnie Liang
TechNet Community Support

Users unable to access the internet sites

Hi Everyone,
We have users who are able to get the IP address but unable to access any internet sites.
I check the trap logs on the WLC
RADIUS server 192.168.50.1:1812 failed to respond to request (ID 16) for client 88:53:2e:99:24:b5 / user 'unknown'
RADIUS server 192.168.50.1:1812 activated on WLAN 1
RADIUS server 192.168.60.1:1812 deactivated on WLAN 1
RADIUS server 192.168.60.1:1812 failed to respond to request (ID 200) for client 88:53:2e:99:24:b5 / user 'unknown'
RADIUS server 192.168.60.1:1812 activated on WLAN 1
RADIUS server 192.168.50.1:1812 deactivated on WLAN 1
RADIUS server 192.168.50.1:1812 failed to respond to request (ID 15) for client 88:53:2e:99:24:b5 / user 'unknown'
RADIUS server 192.168.50.1:1812 activated on WLAN 1
RADIUS server 192.168.50.1:1812 failed to respond to request (ID 16) for client 88:53:2e:99:24:b5 / user 'unknown'
RADIUS server 192.168.50.1:1812 activated on WLAN 1
RADIUS server 192.168.60.1:1812 deactivated on WLAN 1
RADIUS server 192.168.60.1:1812 failed to respond to request (ID 200) for client 88:53:2e:99:24:b5 / user 'unknown'
RADIUS server 192.168.60.1:1812 activated on WLAN 1
RADIUS server 192.168.50.1:1812 deactivated on WLAN 1
RADIUS server 192.168.50.1:1812 failed to respond to request (ID 15) for client 88:53:2e:99:24:b5 / user 'unknown'
RADIUS server 192.168.50.1:1812 activated on WLAN 1
Need to know how can i troubleshoot this further?
Regards
Mahesh

I would do the troubleshooting in following sequence.
1. Put a wired PC on to the vlan allocated for WLAN1
2. Check whether wired PC gets an IP & can browse internet
3. If that works, then we know no issue of DHCP & not issue with L3/NAT routing to access internet
4. If step2, does not work then your issue is not within wireless, you have to change the focus of your troubleshoot.
5. If step2 works, then test a wireless client with OPEN Authentication (No ACS involvment).If this does not work,then it means wireless client does not get proper IP connectivity. Check dynamic interface configuration for this WLAN & make sure gateway addresses correctly configured. Also VLANs are trunk across to WLC from switch.
6. If step5 works, then try your client with ACS & see the client get successfully authenticated. If not it may be WLC to ACS issue. Troubleshoot that in that case.
Do some troubleshooting like this & let us know the outcome. I am sure you will abe to find out the issue easily in this way.
HTH
Rasika

Unable to access Admin Tools for portal after configuring LDAP realm

After setting weblogic to use the LDAP realm I am unable to access the Administration Tools. It does not take the username "administrator" and password "password". I've created the SystemAdministrator Group in LDAP as well as the appropriate "administrator" user but it still does not let me access the Administratotion Tools.

This thread is being discussed in the weblogic.developer.interest.portal
newsgroup under the same title. You can cross-post to multiple groups in
the future so that the thread develops in all newsgroups that you posted to.
"Wendy Kajiyama" <[email protected]> wrote in message
news:[email protected]..
After setting weblogic to use the LDAP realm I am unable to access theAdministration Tools. It does not take the username "administrator" and
password "password". I've created the SystemAdministrator Group in LDAP as
well as the appropriate "administrator" user but it still does not let me
access the Administratotion Tools.

Create Leave Request In portal doesn't load after logging in

He All,
we are facing an issue with some of the users of the E portal , after they log in and click on create leave request the loading icon appear and the portal stuck at that and nothing else happen like in the attached image , this issue happen with some users not all of the users however it was working with them before.
Please advice
Thanks in advance

Hi Ahmed,
I didnt suggest a browser issue.
But using such tool when problem happens can show your the exact request url that hangs.
Then from this, you can reach to where the problem resides on the server.
Google chrome contains it already (just click on F12) , you can see all requests:
When you see a request that doesnt have status 200 or without status, this can give you focus on where is the issue.
Best regards,
Tal

Error while applying ESS Leave Request in Portal

Hi,
I configured ESS in EP and i'am trying to apply a leave.I'am using the Workflow "WS12300111",i also assigned Agents to the WF.But when i try to apply a leave from EP it is giving me this error
"Unable to send the request"
"You are not one of the possible agents of task WS12300111"
In agent assignment of WF i had given the approver name in the Approval Process step but i dnt know why it is saying that you are not the possible agent, for a person who is applying for a leave.
Please guide me with a solution.
With Regards,
Pardeep.B

Hi,
I Solved my Problem.Actually in WF WS12300111 in Header agent assignment is not set to General task.Now i made it to general task and it solved my problem

Unable to Approve Leave Request

Hello guys, when trying to approve a leave request, this error was produced:
Please help. Is there an OSS Note to address this?
#1.5 #8AA34245D50201030000015B000A40B6000484C0320697E6#1271860914721#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#sap.com/tcwddispwda#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#G22705#410961#####SAPEngine_Application_Thread[impl:3]_122##0#0#Fatal#1#/Applications/Xss#Java###null
[EXCEPTION]
#1#com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Message type   is unknown., 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:206)
     at com.sap.xss.ser.xssmenu.fc.wdp.InternalModelHandler.onInit(InternalModelHandler.java:429)
     at com.sap.xss.ser.xssmenu.fc.FcXssMenu.setPersonnelNumber(FcXssMenu.java:583)
     at com.sap.xss.ser.xssmenu.fc.FcXssMenu.onInit(FcXssMenu.java:291)
     at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenu.onInit(InternalFcXssMenu.java:455)
     at com.sap.xss.ser.xssmenu.fc.FcXssMenuInterface.onInit(FcXssMenuInterface.java:165)
     at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface.onInit(InternalFcXssMenuInterface.java:388)
     at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface$External.onInit(InternalFcXssMenuInterface.java:545)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
     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.pcuigp.xssutils.navi.FcNavigation.onInit(FcNavigation.java:313)
     at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigation.onInit(InternalFcNavigation.java:358)
     at com.sap.pcuigp.xssutils.navi.FcNavigationInterface.onInit(FcNavigationInterface.java:145)
     at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface.onInit(InternalFcNavigationInterface.java:142)
     at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface$External.onInit(InternalFcNavigationInterface.java:282)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
     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.pcuigp.xssutils.roadmap.VcRoadmap.onInit(VcRoadmap.java:188)
     at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmap.onInit(InternalVcRoadmap.java:162)
     at com.sap.pcuigp.xssutils.roadmap.VcRoadmapInterface.onInit(VcRoadmapInterface.java:153)
     at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface.onInit(InternalVcRoadmapInterface.java:144)
     at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface$External.onInit(InternalVcRoadmapInterface.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:756)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
     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:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1289)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
     at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:193)
     at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
     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:756)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     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.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(AccessController.java:219)
     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.aii.proxy.framework.core.BaseProxyException: Message type   is unknown., 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:172)
     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)
     ... 76 more

Jan,
when the manager is trying to approve the leaves of his subordinate, he click on the single line approval request entry, and the RFC gets triggered. We usually think that the RFC will only run the particular leave request record and open the same for us. But internally the RFC reads all the pending leave request with the manager and then only displays the clicked record. When the RFC is triggered, if it finds some problem with some other record then it will fail and give the message as system faliure.
Even we had faced the same problem, In our case this employee had a leave request pending with him which belonged to some deleted employee code. As a result there was a system failure message. We deleted the workflow item from the list and the RFC was successfull.
This we check in T Code PTARQ, if u have full rights to this transaction then you can deleted the Workflow item from this list which is creating the problem.
but anywasy you can always check PTARQ for any Leave request related problems
Thanks n regards
Vedashree

VPN users unable to access internal network - ASA 8.3.1

Hello,
I have a base config of AnyConnect VPN below, however the ASA 8.3.1 code has deprecated some commands and the VPN/NAT/FW rule syntax is quite different. Can someone point out what's missing from the pertinent config below that prevents the VPN Pool from accessing the internal LAN?
The Core LAN router is 1.2.3.1.
ASA Version 8.3(1)
interface Ethernet0/0
nameif inside
security-level 100
ip address 1.2.3.2 255.255.255.0
ip local pool anyconnect-vpn-pool 1.2.9.10-1.2.9.20 mask 255.255.255.0
object network DataVLAN
subnet 1.2.3.0 255.255.255.0
object-group network Internal-Data
network-object object DataVLAN
nat (any,any) after-auto source dynamic Internal-Data Outside_INT
route inside 1.2.0.0 255.255.0.0 1.2.3.1 1
dynamic-access-policy-record DfltAccessPolicy
webvpn
enable outside
svc image disk0:/anyconnect-win-2.5.2014-k9.pkg 1
svc enable
group-policy DfltGrpPolicy attributes
vpn-tunnel-protocol IPSec l2tp-ipsec svc webvpn
address-pools value anyconnect-vpn-pool
group-policy GroupPolicy1 internal
group-policy GroupPolicy1 attributes
address-pools value anyconnect-vpn-pool
group-policy vpn-anyconnecct-policy internal
group-policy vpn-anyconnecct-policy attributes
vpn-tunnel-protocol svc webvpn
webvpn
url-list none
svc ask enable
tunnel-group vpn-users type remote-access
tunnel-group vpn-users general-attributes
address-pool anyconnect-vpn-pool
default-group-policy vpn-anyconnecct-policy
tunnel-group anyconnect2 type remote-access
tunnel-group anyconnect2 general-attributes
address-pool anyconnect-vpn-pool
TIA.
Mike

Hi Rohan,
Are you saying to replace "nat (any,any)" with "nat (inside,outside)"? I was wondering about this because I'd always done "nat (inside,outside)" but a colleague had performed the initial configuration which already contained "nat (any,any)" statement and I was not sure if this was just something new in 8.3.1. I also noticed the "global" command is no longer available.
I will give this a try. Thanks.
-Mike

Error while applying leave request in Portal

Hi All,
In portal Employee is unable to apply any leave. The system is giving the error message as
"As per policy, Casual Leave cannot be taken for more than 1 working day consecutively,
Please utilise Privilege leave for this purpose. In case you do not have Sufficient PL balance, Please apply for LOA."
But when trying to raise a "Privilege/ Sick" leave , he is still getting the same message.
So he is not able to raise any kind of leave.
So can anyone please suggest a solution.
Regards,
Muni.

Hi,
I Solved my Problem.Actually in WF WS12300111 in Header agent assignment is not set to General task.Now i made it to general task and it solved my problem

Users unable to access US content due to canadian external IP address

Hello there,
We have users in US who are required to access US websites for content searching but unable to do so because of their IP address is being Natted to external IP that is assigned in Canadian block.
We cannot use proxy servers due to legality.
any suggestions or recommendations ?
Thanks
M

Hi,
Here is my working solution that I have used for years with StrongVPN.
http://forum.strongvpn.com/forums/topic/3480/cisco-ios-l2tp-working-connection-config
Hope this helps.
Cheers.
Jason

Windows Users Unable to Access SL Server

I am attempting to have Windows clients access the SL server as AD users. I have AD/OD configured in a Magic Triangle with 10.5 and 10.6 clients being managed properly and accessing everything normally. smb services are enabled, all users and groups appear to have access according to Server Admin but I cannot login to the SL server as an AD user from a W2K machine. I'm probably missing something obvious, so I apologize for any ignorance on my part. Any ideas on how to gain access under Windows are welcome.

Hi
As per the information and details provided by you, to access OWA in Exchange 2007, please follow these steps: -
Open
Active Directory users and computers.
Click on the
View, and then click Advanced Features.
Note:
To make the
Security tab available at both the user level and the organizational unit level, You must enable the Advanced features option in Active directory Users & Computers.
This option will be available in the
View tab.
Open the properties for both the user level and the organizational unit level that the users are located in, and then locate the
Security tab.
Click on the
Advanced.
Make sure that the following check box is selected:
Allow inheritable permissions from the parent to propagate to this object and all child objects. Include these
with entries explicitly defined here.
Force Active Directory replication.
I hope this information will be helpful for you.
Thanks and regards
Shweta@G

Unable to approve leave request in ESS

Hi
    While trying to approve leave in ESS/MSSm getting the following error
    After clicking the link in SAP inbox / Universal Work List in MSS an error is encountered.
    In R3 we have analysed the error in ST22 transaction which says--
The current application triggered a termination with a short dump.
There is no data for infotype 0105,personnel no. 0 E .
Kindly suggest what to do..???

hi,
check the Infotype 105 subtype 0001 in Transaction PA30 for the Personnel no.
Regards,
Boobalan.

User unable to access Leave Request in Portal

Similar Messages

Maybe you are looking for