Critical Error in ESS page due to no entry in V_T554S_WEB

Hi all,
I have hit this error due to no entry in this table V_T554S_WEB. The requirement of user is not to apply leave via ESS and they would like to remove all entry of leave type in ESS. Is there any possible solution for me to consider.
Kindly, please assist.
Thanks.

Hi,
The process is you create a rule group and you assign which leave type you want to show in ESS to the rule group.
If you don't want users to apply leave through ESS then delete the entry from the table for the rule group in discussion.
Either you can do it using the method Sandip said or you can do the same using the SPRO
SPRO - Personnel Management - Employee Self- Services - Service-Specific Settings - Working Time - Leave Request - Processing Processes - Specify processing processes for types of leave.
And also delete the WEBMO feature fo rthe country.
Cheers-
Pramod

Similar Messages

Error in ESS page

Hi Experts,
Iam having problem with my ESS page while iam clicking on it its showing error like this please help me in this.
Overview
500   Internal Server Error
SAP NetWeaver Application Server 7.00/Java AS 7.00
Failed to process request. Please contact your system administrator.
[Hide]
Overview
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.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
    at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:861)
    ... 58 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type     HTML Client
User agent     Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30)
Version     null
DOM version     null
Client Type     msie6
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.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Thu May 29 11:29:48 IST 2008
J2EE Engine     7.00 patchlevel 109044.44
Java VM     Java HotSpot(TM) 64-Bit Server VM, version:1.4.2 1.4.2.13-070317-20:54-IA64W IA64W, vendor: Hewlett-Packard Company
Operating system     HP-UX, version: B.11.31, architecture: IA64W
Session & Other
Session Locale     en
Time of Failure     Fri Aug 29 11:57:24 IST 2008 (Java Time: 1219991244104)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore     7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:42[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates     7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:50[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore     7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:44:42[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer     7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:26[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon     7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:30[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore     7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:23[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary     7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:54:53[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro     7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:00:50[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates     7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
SapWebDynproGenerationCore     7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:37[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates     7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
sap.com/tcwddispwda
No information available     null
sap.com/pb_api
SapDictionaryGenerationCore     7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:42[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates     7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:50[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore     7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:44:42[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer     7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:26[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon     7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:30[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore     7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:23[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary     7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:54:53[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro     7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:00:50[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates     7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
SapWebDynproGenerationCore     7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:37[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates     7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
sap.com/tcwdcorecomp
No information available     null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:861)
     at com.sap.pcuigp.xssfpm.java.MessageManager.handleException(MessageManager.java:258)
     at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:103)
     at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModelInternal(BackendConnections.java:323)
     at com.sap.pcuigp.xssfpm.wd.BackendConnections.initBackend(BackendConnections.java:256)
     at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModel(BackendConnections.java:154)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.connectModel(InternalBackendConnections.java:237)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.connectModel(FPMComponent.java:841)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.connectModel(FPMComponent.java:1071)
     at com.sap.pcuigp.xssfpm.wd.BackendConnections.init(BackendConnections.java:141)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.init(InternalBackendConnections.java:233)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:182)
     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:748)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
     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:1246)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
     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:313)
     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: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:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                                                                                Failed to process request. Please contact your system administrator.
Regards,
Shilpa.
Edited by: pasumarthi shilpa on Sep 1, 2008 6:40 AM

hi Shilpa,
Please go to transaction SWFVISU and check whether the package name and all is correct or not
coz u'll see thr sometime package is diff.
and most of time u need change package name according to ur pkg.
And
check whether system object and aliases are properly mapped to the user.
Expecting your co-operation,If suggession becomes solution or useful to find the solution.
Thanks
mahendra

Critical Error in ESS Configuration ?

HI All,
When i am working on ESS custom Career and Job
I got the following error, when i open my Quick links .
Critical Error
A critical error has occured. Processing of the service was terminated. Unsaved data has been lost.
Contact your system administrator.
com.sap.pcuigp.xssfpm.java.FPMRuntimeException: User xxxxxx does not exist/not attached in this period.
     at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:112)
     at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:122)
     at com.sap.pcuigp.xssutils.pernr.EmployeeGroupInfo.init(EmployeeGroupInfo.java:140)
     at com.sap.pcuigp.xssutils.pernr.wdp.InternalEmployeeGroupInfo.init(InternalEmployeeGroupInfo.java:183)

Check whether infotype 105, subtype 0001 is maintained properly.
Thanks
Prashant

Error on ESS page

Hello everybody,
i implemented Travel Management in my ESS package.
when i navigate on page of Personal Info i have back the follow error:
Fatal error: Area EMPLOYEE_PERSINFO_ERP2005 does not exist
I found 1 other topic talking about this problem but was not helpfull and problem persist
/message/2390168#2390168 [original link is broken]
I checked on SPRO and PTARQ but i think everything is set correctly.
I have a DEVEL system too and there everything work correctly. I not found difference between both system.
any suggestion?
PS: i notifyed that if i change PCD path in V_T7XSSSERRES table, then when i log me on portal and i navigace in the page; if i look details page, she still to have same path.
It's necessary reboot portal?
I cleaned cache on my browser
Edited by: apederiva on Sep 28, 2009 6:35 PM

Hi,
Looks like this is a config issue. The system is not able to find the area as mentioned in the error.Please check your areas and subareas being defined and compare also you could have a look at this thread in which the same issue is discussed.
Re: Fatal error: Area EMPLOYEE_TRAVEL_ERP2005 does not exist
Good Luck!
Sandeep Tudumu

Critical Error in ESS Addresses iView

Getting the following error message when running the Address iView for employees
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.uk/com.sap.pct.erp.srvconfig.addr/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.per_address_gb failed.

Ashutosh is correct,
This location in your PCD portal_content/com.sap.pct/srvconfig requires additional permissions to be set.
Depending on how you want to go about this - you could start by assigning the Authenticated Users group to this directory. Dont forget to reset all the child permissions to force the permissions down the tree.
Haydn

Are there any problems accessing PeopleSoft 9.2/PeopleTools 8.54 ESS Pages from an external non-PeopleSoft Portal?

We are hearing indications that external non-PeopleSoft portals now have trouble linking to native PeopleSoft ESS pages for user data entry. Trouble perhaps related to change to fluid user interface. Any truth to that rumor? If so, where can I find material on fixes or work-arounds?

We are hearing indications that external non-PeopleSoft portals now have trouble linking to native PeopleSoft ESS pages for user data entry. Trouble perhaps related to change to fluid user interface. Any truth to that rumor? If so, where can I find material on fixes or work-arounds?

ERROR IN ESS AND MSS pages when deleting the superadmin role

hi all
According to my clent requirement i have worked with uwl for leave request.....for that i configured uwl and added uwl iview to the standard user role......after i have assigned standard user role to my manager.
but' after some time they told me that they need attendance overview and Reminder of dates and subordinate information.
After backend configuration i have assigned Mss role to the Manager,
i have made the settings for mss role with overview workset
Again overview contain-workoverview page it contains 1) uwl pabge 2)Attendance Overview   3)reminder of dates
                                        Team- General information and so on
now my manager has following roles 1)ESS   2)MSS 3)Home (from the standard user role)   4) Home( by default i think from MSS role)     5) superadmin role
when ever i am removing the super admin role and standard user role for the manager   i am unable to see the Attendance overview page and Reminder of dates page and i am unable to see the pages in ESS also.
getting error
Critical Error
A critical error has occured. Processing of the service was terminated. Unsaved data has been lost.
Contact your system administrator.
Read of object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.mss/com.sap.pct.erp.srvconfig.rod/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.reminderofdates failed.
plz ask me if any information is needed for this to solve my problem.
thankyou in advance.
if i am keeping that superadmin role(content ,user and system administration) All pages are opening.
thankyou

Swapna,
Pls refer below links,
Unable to view notofications in MSS
Re: Critical Error when running MSS Work Overview Page
Manager Self Service Content are not showing up
Hope it should work now...
To give points, select the radio buttons on the left side under the name of the replier.
Regards,
Amarnath S

Critical Error when running MSS Work Overview Page

Hi All,
I am experiencing a critical error when I open the MSS Overview Page in the portal. Attendance Overview, Reminder of Dates,
Team Calendar & Status Overview for Personnel Change Requests each display the following error message:
A critical error has occured. Processing of the service had to be terminated. Unsaved data has been
lost.
Please contact your system administrator.
Read of object with ID
portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.mss/com.sap.pct.erp.srvconfig.ato/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.attendanceoverview
failed.
I have made the following discoveries:
1. When I provide the role with Super_Administration rights, it works perfectly fine but once I remove this, it stops working.
2. When I assign the authenticated group as a child group to my customised MSS & ESS Group, the iViews work perfectly fine but ESS gains access to MSS roles.
I have had a read through the following Separate UWL Admin from System Admin? but I am not too sure whether this relates directly to my problem, if anyone can shed some light on this, please do.
Thanks in advance.
Oloy.

Hi Rajendra,
I have assigned the necessary permissions to both the default SAP MSS folder (Content Provided By SAP -> Line Manager -> Manager Self- Service)
and I have also assigned permissions to my custom folder however, this has still not helped.
I assigned Read/Write permissions with the end-user box ticked.
Any other suggestions?
Thanks,
Oloy.

I am unable to load some web pages, I get an error message saying unable to load page due to invalid or unsupported form of compression, this happens on the BBC news page for example. Any ideas how to overcome???

OS is Windows7. I'm using the latest version of Mozilla Firefox
I am unable to load some web pages, I get an error message saying unable to load page due to invalid or unsupported form of compression, this happens on the BBC news page for example. Any ideas how to overcome???

Reload web page(s) and bypass the cache.
* Press and hold Shift and left-click the Reload button.
* Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
* Press "Cmd + Shift + R" (MAC)
Clear the cache and the cookies from sites that cause problems.
"Clear the Cache":
* Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
"Remove Cookies" from sites causing problems:
* Tools > Options > Privacy > Cookies: "Show Cookies"

Safe mode did not start successfully. This page has encountered a critical error. Contact your system administrator if this problem persists.

Hi
I just now updated dec 2013 c.u to sharepoint server 2010 sp2
I get this error in event viewer when I browse web applications , they not open even
Load control template file /_controltemplates/TaxonomyPicker.ascx failed: Could not load type 'Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker' from assembly 'Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'.
SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure
Process Name: OWSTIMER
Process ID: 3836
AppDomain Name: DefaultDomain
AppDomain ID: 1
Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:548f72e6a39f401e95e92711aea13c45#authority=urn:uuid:9aebe976322541d280e4bd3799fa283f&authority=https://spfwf01:32844/Topology/topology.svc
Active Endpoints: 2
Failed Endpoints:1
Safe mode did not start successfully. This page has encountered a critical error. Contact your system administrator if this problem persists.
adil

This messge I get initially I get two times (1)
SharePoint Web Services Round Robin Service Load Balancer Event: EndpointFailure
Process Name: w3wp
Process ID: 4600
AppDomain Name: /LM/W3SVC/2141356646/ROOT-1-130405218187772398
AppDomain ID: 2
Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:548f72e6a39f401e95e92711aea13c45#authority=urn:uuid:9aebe976322541d280e4bd3799fa283f&authority=https://spfwf01:32844/Topology/topology.svc
Active Endpoints: 2
Failed Endpoints:1
Affected Endpoint: http://spfapp02:32843/548f72e6a39f401e95e92711aea13c45/MetadataWebService.svc
aftert this message three times (2)
The Managed Metadata Service 'Managed Metadata Service' is inaccessible.
and after (3)
The health service has removed some items from the send queue for management group "MOJOmanagement" since it exceeded the maximum allowed size of 15 megabytes.
after (4)
Safe mode did not start successfully. This page has encountered a critical error. Contact your system administrator if this problem persists.
and this time I seen I am unable to browse web applications
and
Load control template file /_controltemplates/TaxonomyPicker.ascx failed: Could not load type 'Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker' from assembly 'Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'.
adil

This page has encountered a critical error. Contact your system administrator if this problem persists.

I am getting this error while opening SharePoint site pages. I am getting this error if i edit Web.config file. If i Restore the old version of Web.Config i am getting this error.. Please help me

Hi UjwalaIDC,
Also can try enabling the stack trace (and ULS) for more information to solve issue.
http://blogs.msdn.com/b/souravd/archive/2009/06/23/sharepoint-2007-moss-2007-enable-stack-trace-for-better-logging-information.aspx
http://www.sharepointdiary.com/2012/01/fix-for-this-page-has-encountered-critical-error.html
Thanks
Daniel Yang
TechNet Community Support

Web Part Error: This page has encountered a critical error. Contact your system administrator if this problem persists

Hi there,
I am getting the following error in SharePoint 2007 site.
Web Part Error: This page has encountered a critical error. Contact your system administrator if this problem persists.
Show Error Details
Hide Error Details
[WebPartPageUserException: This page has encountered a critical error. Contact your system administrator if this problem persists.]
at Microsoft.SharePoint.ApplicationRuntime.SafeControls.RethrowExceptionIfNeeded()
at Microsoft.SharePoint.ApplicationRuntime.SafeControls.GetTypeFromGuid(Guid guid)
at Microsoft.SharePoint.WebPartPages.SPWebPartManager.CreateWebPartsFromRowSetData(Boolean onlyInitializeClosedWebParts)
There is no event logged related to this error. I have checked ULS log and nothing much I can find over there.
Any help would be highly appreciated.
Thanks,
Puli
Puli Bala

It is not only because of unsafe controls. Please refer the articles below.
http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2008/09/24/safe-mode-did-not-start-successfully-request-failed.aspx
http://blogs.edwardwilde.com/2009/12/22/safe-mode-did-not-start-successfully-could-not-load-file-or-assembly/
https://social.technet.microsoft.com/Forums/sharepoint/en-US/6d81f7b0-33c5-482b-b7aa-9f639c784dea/what-reason-can-cause-the-errorerror-failure-in-loading-assembly-microsoftsharepoint?forum=sharepointadminlegacy
https://paulsiu.wordpress.com/2008/07/24/sharepoint-loading-assembly-error-in-the-event-log/
Puli Bala

In ESS-Leave Request -A critical error has occured.

In ESS when tried to enter the Leave which is under Leave request the below error occured:
Critical Error
A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
Please contact your system administrator.
CREATE OBJECT: The class was not found., error key: RFC_ERROR_SYSTEM_FAILURE
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: CREATE OBJECT: The class was not found., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
     at com.sap.xss.hr.lea.blockcale.FcBlockCale.getBcData(FcBlockCale.java:232)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCale.getBcData(InternalFcBlockCale.java:250)
     at com.sap.xss.hr.lea.blockcale.FcBlockCaleInterface.getBcData(FcBlockCaleInterface.java:135)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCaleInterface.getBcData(InternalFcBlockCaleInterface.java:224)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCaleInterface$External.getBcData(InternalFcBlockCaleInterface.java:276)
     at com.sap.xss.hr.lea.blockcale.VcBlockCale.onInit(VcBlockCale.java:261)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCale.onInit(InternalVcBlockCale.java:275)
     at com.sap.xss.hr.lea.blockcale.VcBlockCaleInterface.onInit(VcBlockCaleInterface.java:163)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface.onInit(InternalVcBlockCaleInterface.java:144)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface$External.onInit(InternalVcBlockCaleInterface.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:150)
     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:1246)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
     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:321)
     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:150)
     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:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: CREATE OBJECT: The class was not found., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
     at com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel.pt_Arq_Eecale_Get(LeaveRequestAdaptiveModel.java:434)
     at com.sap.xss.hr.lea.model.Pt_Arq_Eecale_Get_Input.doExecute(Pt_Arq_Eecale_Get_Input.java:137)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
     ... 60 more

I found out the solution and solved this issue.
Deleted the leave request which was created with error i.e: from the custom table zxx_vacr noted down the id initiater ( which had error) and in the Test Environment for Leave request (PTARQ) gave the PERNR and deleted the documents ( gave the id iniater in the document status ).
To check the error work flow go to SWIA and check for that Workflow (Leave) raised by the PERNR at that duration ( check in IT2001 for the duration) and give it here.
After deleting it check in the portal for the leave request.

ESS Leave request screen giving a critical Error in production server

Friends,
We are in a critical face of ESS implemetation.
We are doing an ESS MSS implementation for country grouping 99.
When we moved our changes to production server after succesful testing in quality, getting the following Critical error for Leave Request Screen.
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
     at java.util.ArrayList.RangeCheck(ArrayList.java:512)
     at java.util.ArrayList.get(ArrayList.java:329)
     at com.sap.aii.proxy.framework.core.JcoBaseList.get(JcoBaseList.java:272)
     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:2543)
     at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:621)
Other areas like personal Info & who is who are working fine.
Leave request was working fine in Development and Quality servers and it never worked in Production server.
It worked fine with same config, with same master data and same employee & org structure in quality server.
We tried the following things:
1. Checked and confirmed the sequence of transports for configs and Developments to Quality and Production.
Even compared the table level entries and ABAP codings B/n dev and Production. All are same.
2. Moved the workflow changes to production and activated the same. No change found after that.
3. Gave SAP all authorization in R/3 and full authorization from portal side as well.
4. Assigned the userid to different employees and checked the masterdata of employees.
5. Checked the note 1388426.Every thing mentioned in the note is there in the system.
6. Verified Rule groups and WEBMO feature are correct and same as in quality.
As our go live date is very near, request your help .Thanks in advance for your help.
Regards,

Customisation of Leave request is mising in your system, please check the rule group using PTARQ.

XML import - stopped due to "critical error"

Hi all. For the moment, I'm still working with FCS1/FCP 5.1.4, OS 10.4.11.
In the past, when I've needed to open a project I've started on other machines running 6.0.x, I've done an XML export, and imported said xml file into a new project on my machine. If I recall correctly, XML type 2 worked just fine.
Well, it doesn't work now, and I'm wondering why?
The machine I'm exporting from is running OS10.4.11, and FCP 6.0.3. I've exported the project out of there in all flavors of xml (1,2,3 and 4), with and without clip metadata. And I get nothing on import, bupkus, nada, zilch and zero...except for the oh-so-helpful message "XML import stopped due to critical error"
So who broke this?

I've had this happen to me when the original project contained sequences that used filters not supported by 5.1.4.
My solution was to strip out suspect filters until it worked.
Best,
Tom

Critical Error in ESS page due to no entry in V_T554S_WEB

Similar Messages

Maybe you are looking for