Error in mss

Hi all,
we are using ECC 6.0 and it has integration with MSS. In the MSS portal for the paths, my staff => statistics, under all the iviews like 'Headcount by employment status' , 'Headcount by personal area' etc, it is showing an error - 'do not enter a date'. but in R/3 if we look at our queries, they are running absolutely fine. What could be wrong????
What portal content settings we should check?
Please suggest. Points would be rewarded.
Regards,
Ronnie

Hi Sheetal,
When I am previewing the iview, its showing the following error :
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
Unable to lookup System 'SAP_BW'. Please check the system object and the alias..
See the details for the exception ID in the log file
Please suggest what could be the reason.
Thanks.

Similar Messages

Error in MSS PEOPLE RELATED FORM IVIEW

Hi Expert,
I am getting an error in MSSonline formPeople related. Once I am selecting the radio button of the particular employee name and clicking on it ,it showing the error like (because of hyper link in each and every employee).
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 09:55_11/01/11_0055_513756950
Refer to the log file for details about this exception.
But once I am selecting the employee name in corresponding radio button and clicking on TO FORM SELECTION button, itu2019s working fine.
I want to remove the hyper link from the employee name list to resolve this error.
Can someone help me for the same to achieve it?
Thanks in advance,
Kundan

Hi,
Still i am waiting for the replay which help me to get the solution of this error.
Thanks,
Kundan

Error in MSS requisition 'No personnel number is assigned to your user in SAP E-recruiting '

Hi ,
We are getting error in MSS requisition in E recruiting system that 'No personnel number is assigned to your user in SAP E-recruiting '
while clicking on next button in the requisition form.We have assigned all specified roles for the E-rec related things with authorisation for 'P' and all
other objects.Please comment on this if anybody faced the same issue

Hi, just want to add to this issue might be useful for somebody else.
We had the same issue, it turns out that the person who is raising the requisition has 2 Business partners in the system. We set one business partner to be "not released" and in addition to that we added the NA relation as this is missing with the CP
MfG.

Getting portal runtime error in MSS

Hi guys ,
I am getting portal runtime error in mss in Team, Budget ,headcount
the error is saying about some jmx authorizations .....
what to do in this case..
please help me ..
thanks in advance

11:22_06/10/11_0048_2907850
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bw/BEx?sap-client=<System.client>&sap-language=<Request.Language>&accessibility=<User.Accessibility[SAP_BOOL]>&style_sheet=<LAF.StylesheetUrl[url_ENCODE]>&<TrayInformation[IF_true PROCESS_RECURSIVE]>&<Authentication>&<Report>&<BusinessParameters>'; the problem occured at position 82. Cannot process expression <System.client> because Invalid System Attribute:
System: &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:523)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:412)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
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)

Portal Run time error in MSS iView

Hi,
I am getting portal run time error in MSS iView when i am navigating MSS>Online form>People related form and clicking on the employee name in the table which has hyper link. How to remove the hyper link from the employee name?
When i am selecting the same employee from radio button and clicking on To Form Selection button ,it's working fine.
Someone can help me to resolve this error.
Thanks,
Kundan

Still my question is open. Someone can provide the solution for the same?
Thanks,
Kundan.

Critical error on MSS

Hi all,
User gets critical error on MSS saying" criitical error has occured. Unsaved data has been lost'
"No data exists in this period for infotype 105 & employee 25379". She gets this when shei s trying to view team absences on MSS.
Employee 25379 belongs to inactive pernr. HR has now corrected the relationships which were active even when inactive action was taken.
I have checked all the records & relations between this pernr & user, but i do not see any reason.
Please help.
Thanks
Deepali
Moved from HCM forum to ESS for Better results

Any replies please??
I have made this pernr completely inactive by performing the leaving action, 105 is also delimited.
But still the manager gets this error on MSS while looking at team absences.
Strangely the problem is partly resolved, but user says she is still
1.   unable to view July Holidays in total
2.    August - Can view Page 1 only
3.    September - Can view Pages 1 and 2 only
4.    October - Can only view Page 1
5.    November and December - Can view all pages.

Component Usage error in MSS Leave Request approval

Hi All,
We are getting the below mentioned error only for few users while approving the leave request in MSS.
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)
    ... 41 more
Kindly share your views on the same.
Thanks and Regards,
Vivek.

Hi Anup,
Please find the complete Trace below.
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; MS-RTC LM 8)
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.20080611120129.0000 (release=NW04S_13_REL, buildtime=2008-09-11:17:05:50[UTC], changelist=42127, host=pwdfm114), build date: Wed Nov 19 19:21:28 CET 2008
J2EE Engine     7.00 patchlevel 109044.44
Java VM     IBM J9 VM, version:2.3, vendor: IBM Corporation
Operating system     AIX, version: 5.3, architecture: ppc64
Session & Other
Session Locale     en
Time of Failure     Sat Jan 02 12:26:56 CET 2010 (Java Time: 1262431616916)
Web Dynpro Code Generation Infos
sap.com/ess~lea
SapDictionaryGenerationCore     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore     7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon     7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore     7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary     7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro     7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
SapWebDynproGenerationCore     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
sap.com/pcui_gp~xssutils
SapDictionaryGenerationCore     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore     7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon     7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore     7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary     7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro     7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
SapWebDynproGenerationCore     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
sap.com/tcwddispwda
No information available     null
sap.com/pcui_gp~xssfpm
SapDictionaryGenerationCore     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore     7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon     7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore     7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary     7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro     7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
SapWebDynproGenerationCore     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
sap.com/tcwdcorecomp
No information available     null
sap.com/pcui_gp~tecl
SapDictionaryGenerationCore     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates     7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore     7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon     7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore     7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary     7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro     7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
SapWebDynproGenerationCore     7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates     7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
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: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:150)
       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: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)
Thanks and Regards,
Vivek.

Error in MSS HCM Processes and Forms Overview

Hi all,
Currently we are working on ESS/MSS from NW 7.3 portal.
When i open HCM Processes and Forms Overview from MSS, it prompt me to change the password again and again.
And on some user HCM Processes and Forms Overview not shown properly.
Error while processing your query
What has happened?
The URL call http://<host name>:1080/sap/bc/webdynpro/sap/asr_pa_pd_processes_display was terminated because of an error.
Note
The following error occurred in system BEQ : Parameter has invalid value: Parameter TSTMP1 has invalid value 0 .
The error occurred on application server MUMSAP02_BEQ_00 and in work process 8 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: SUBTRACT of program CL_ABAP_TSTMP=================CP
Method: SUBTRACT_TIMESTAMPS of program CL_HRASR00_PROCESS_UTILITIES==CP
Method: GET_CURRENT_TIME_DATA of program CL_HRASR00_PROCESS_UTILITIES==CP
Method: START_TRACKING of program /1BCWDY/LA89BHH7CSECCUXGQD7Z==CP
Method: IF_COMPONENTCONTROLLER~START_TRACKING of program /1BCWDY/LA89BHH7CSECCUXGQD7Z==CP
Method: HANDLEDEFAULT of program /1BCWDY/LA89BHH7CSECCUXGQD7Z==CP
Method: HANDLEDEFAULT of program /1BCWDY/LA89BHH7CSECCUXGQD7Z==CP
Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/LA89BHH7CSECCUXGQD7Z==CP
Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_IF_VIEW=====CP
Method: DISPLAY_TOPLEVEL_COMPONENT of program CL_WDR_CLIENT_COMPONENT=======CP
What can I do?
If the termination type is RABAX_STATE, you will find more information on the cause of termination in system BEQ in transaction ST22.
If the termination type is ABORT_MESSAGE_STATE, you will find more information on the cause of termination on the application server MUMSAP02_BEQ_00 in transaction SM21.
If the termination type is ERROR_MESSAGE_STATE, you can search for further information in the trace file for the work process 8 in transaction ST11 on the application server. MUMSAP02_BEQ_00 . You may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system adminmistrator.
Error Code: ICF-IE-http -c: 350 -u: ISHAJI -l: E -s: BEQ -i: MUMSAP02_BEQ_00 -w: 8 -d: 20130514 -t: 133514 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION -X: D4AE5218F8121ED2AF8DA00F61FBEAC0_D4AE5218F8121ED2AF8DA00F5D19EAC0_1 -x: 006DBCE20F7BF1E58AC0D4AE5218F812
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
Please suggest me the solution.
Regards,
Devendra

Dear Andrea,
I reset the password of backend user and gave sap_all and sap_new role.
Last time it prompt the screen in mss as to change the password. (See above screen shot).
But after reset the password...error showing instead of login screen in mss as below:
Error while processing your query
What has happened?
The URL call http://<host name>:1080/sap/bc/webdynpro/sap/asr_pa_pd_processes_display was terminated because of an error.
Note
The following error occurred in system BEQ : Parameter has invalid value: Parameter TSTMP1 has invalid value 0 .
The error occurred on application server MUMSAP02_BEQ_00 and in work process 7 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: SUBTRACT of program CL_ABAP_TSTMP=================CP
Method: SUBTRACT_TIMESTAMPS of program CL_HRASR00_PROCESS_UTILITIES==CP
Method: GET_CURRENT_TIME_DATA of program CL_HRASR00_PROCESS_UTILITIES==CP
Method: START_TRACKING of program /1BCWDY/LA89BHH7CSECCUXGQD7Z==CP
Method: IF_COMPONENTCONTROLLER~START_TRACKING of program /1BCWDY/LA89BHH7CSECCUXGQD7Z==CP
Method: HANDLEDEFAULT of program /1BCWDY/LA89BHH7CSECCUXGQD7Z==CP
Method: HANDLEDEFAULT of program /1BCWDY/LA89BHH7CSECCUXGQD7Z==CP
Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/LA89BHH7CSECCUXGQD7Z==CP
Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_IF_VIEW=====CP
Method: DISPLAY_TOPLEVEL_COMPONENT of program CL_WDR_CLIENT_COMPONENT=======CP
 What can I do?
If the termination type is RABAX_STATE, you will find more information on the cause of termination in system BEQ in transaction ST22.
If the termination type is ABORT_MESSAGE_STATE, you will find more information on the cause of termination on the application server MUMSAP02_BEQ_00 in transaction SM21.
If the termination type is ERROR_MESSAGE_STATE, you can search for further information in the trace file for the work process 7 in transaction ST11 on the application server. MUMSAP02_BEQ_00 . You may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system adminmistrator.
Error Code: ICF-IE-http -c: 350 -u: IKHASU -l: E -s: BEQ -i: MUMSAP02_BEQ_00 -w: 7 -d: 20130514 -t: 175940 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION -X: D4AE5218F8121ED2AF923E065A39EAC0_D4AE5218F8121ED2AF923E394271EAC0_1 -x: F091BCE2D132F1D58AC0D4AE5218F812
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
I checked log in ST22 as below
What happened?
 The exception 'CX_PARAMETER_INVALID_RANGE' was raised, but it was not caught
 anywhere along
 the call hierarchy.
 Since exceptions represent error situations and this error was not
 adequately responded to, the running ABAP program
 'CL_ABAP_TSTMP=================CP' has to be
 terminated.
Error analysis
 An exception occurred that is explained in detail below.
 The exception, which is assigned to class 'CX_PARAMETER_INVALID_RANGE', was not
 caught in
 procedure "SUBTRACT_TIMESTAMPS" "(METHOD)", nor was it propagated by a RAISING
 clause.
 Since the caller of the procedure could not have anticipated that the
 exception would occur, the current program is terminated.
 The reason for the exception is:
 Parameter has invalid value: Parameter TSTMP1 has invalid value 0.
Regards,
Devendra

Error in MSS: Area MSS_HCM_AREA_RELATEDACTIVITY does not exist

Hello Experts,
We are currently looking at implementing simple MSS functionality to display PA data. We are interested in using the "General Information" iView with enabled "Related Activities."
Currently we have basic ESS functionality implemented, so Related activities would be limited to Addresses, Emergency Contacts and Personal Data.
The General information page comes up blank and the following error is displayed in the log:
Area MSS_HCM_AREA_RELATEDACTIVITY does not exist.
Error##Java###07:49_28/04/09_44495850 An error occured in iView: N/A in component: N/A##
Error##Java###07:49_28/04/09_44495850 An error occured in iView: N/A in component: N/A##
Error##Java###07:49_28/04/09_44495850 An error occured in iView: N/A in component: N/A##
Error##Java###07:49_28/04/09_44495850 An error occured in iView: N/A in component: N/A##
In checking the homepage framework configuration, the Area does exist and has not been altered from SAP Standard. Resources, Subareas, Services have also been configured as Standard.
Please advise. What is causing this error?

Hi Aneez,
Please check whether the Area MSS_HCM_AREA_RELATEDACTIVITY is present in your backend customizing.
Regards,
Shubham

Portal Runtime Error for MSS Iviews

Hi all,
Though this topis has been discussed several times in our forum, i could not make anything from it.
Portal Runtime Error

An exception occurred while processing a request for :
iView : pcd:portal_content/com.ssmcehr.ssmcehr/com.ssmc.pct.ehr.mss.folder.mss/com.ssmc.pct.ehr.mss.folder.roles/com.ssmc.pct.ehr.mss.role.mss_mgrs/com.ssmc.pct.ehr.mss.workset.manager_self_service/manager_self_service/com.ssmc.pct.ehr.mss.worksets.employee_information/com.ssmc.pct.ehr.mss.page.employee_career/com.ssmc.pct.ehr.mss.iview.pay_actions
Component Name : com.sap.pct.hcm.eeprofilegenericiviewtable.default
The exception was logged. Inform your system administrator..
Exception id: 09:51_08/12/06_0067_101532150
See the details for the exception ID in the log file

and the error log file ...

#1.5#00142216FF7C00640000003F000022F80004240E23838D08#1165543050906#com.sap.security#sap.com/irj#com.sap.security.logToFile#Guest#19####76b39fa0865f11db815c00142216ff7c#SAPEngine_Application_Thread[impl:3]_16##0#0#Error#1#/System/Security/Audit#Plain###Guest | LOGIN.ERROR | NONE = null | | Login Method=[default], UserID=[jothi], IP Address=[137.55.161.180], Reason=[Access Denied.]#
#1.5#00142216FF7C006100000031000022F80004240E23BE4303#1165543054765#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#Guest#19####790075d0865f11dba82400142216ff7c#SAPEngine_Application_Thread[impl:3]_15##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##

This occurs only for the LDAP users,if we create user in EP(manually) it's working fine..
Thanks in Advance,
Jothi.P

It got resolved by itself after restarting the Java server.

Portal runtime error in MSS / employee review --- all the links

Hi
I got an portal runtime error
Here is the error that I am getting.
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/WEB_GROUP.cra.ca.WEB_GROUP/roles/cra.mss.MSS/cra.mss.MSS/cra.mss.EmployeeReview/cra.mss.GeneralData/com.sap.pct.hcm.teamviewer_1
Component Name : com.sap.pct.hcm.teamviewer.default
The exception was logged. Inform your system administrator..
Exception id: 07:47_02/02/07_0031
See the details for the exception ID in the log file

Hi,
You need to locate the defaulttrace. Check out this help file:
http://help.sap.com/saphelp_nw04/helpdata/en/a0/58db515b95b64181ef0552dc1f5c50/frameset.htm
If you open the trace file, you can search for the exception id as mentioned in your 1st post.
cheers,
Noë

Portal runtime error in MSS

In MSS portal -->Work Overview --> Key Figure Monitor section displays Portal runtime error as follows.
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 03:45_24/10/11_0126_6285950
Refer to the log file for details about this exception.
When I Traced the Log file I got the trace as follows
03:28_24/10/11_0125_6285950
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:434)
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)
I am new to MSS Portal. Can anyone help me figure out the cause of this error.

Hi,
I am also facing the same issue .Getting runtime Erorr (Whilce Click on MSS--Budget/Projects/recruitment/team..etc...
Is this related to backend Configuraiton issue or Portal installtion error
Portal runtime error
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID 05:48_09/06/12_0165_22331150
See log file for details about this exception
we have installed the below BP's on (Netweaver 7.3 and backend EHP5)
BP_ERP5COM 1.51
BP_ERP5ESS 1.41
BP_ERP5MSS 1.51
BPERPESSWDA 1.50
SAP_ESS 633
SAP_MSS 630
SAPPCUI_GP 633
Please adivce..
thanks
Matt

Error in MSS Report (Using MSS Reporting Launch Pad)

Hello,
I'm currently using the convert manager's desktop data to MSS report launch pad for the portal.
When trying to run the report in MSS, I'm getting the error below:
"Error in Manager Self Service. When calling the report, the following error occured. Error when executing query Z_ABCD." This is from an SAP Query report and I could not determine what caused this error.
Have anyone encounter this and if you are able to resolve it?
Any information would be greatly appreciated.
Thank you,
Tam Ly
County of Sacramento

hi,
Go to transaction RSCUSTV27 and check if any standard template is maintained.
Use
In this activity you can make the following settings (for systems with a Release higher than SAP BW 3.x):
You can set your own Web template as the standard Web template for ad hoc analysis.
You can set your own Web template as a standard Web template for BEx Broadcasting.
You can set a Web template that is used during BEx Broadcasting for queries for generating documents.
You can specify a Web template that is used during BEx Broadcasting for enterprise reports.
You can set your own Web template as a standard Web template for reports.
Standard settings
The delivered standard Web template (0ANALYSIS_PATTERN) is used for ad hoc analysis.
The delivered standard Web template 0BROADCASTING_TEMPLATE is used for BEx Broadcasting.
The delivered standard Web template 0QUERY_TEMPLATE_BROADCASTING70 is used for broadcasting queries.
The delivered standard Web template 0REPORT_TEMPLATE_BROADCASTING is used for broadcasting reports.
The delivered standard Web template 0REPORT_DEFAULT_TEMPLATE is used for executing enterprise reports.
Activities
To set your own Web template as a standard Web template for ad-hoc analysis, enter the technical name of the Web template under Ad-hoc Analysis. If you do not specify anything, the delivered standard Web template (0ANALYSIS_PATTERN) will be used for ad-hoc analysis.
To set your own Web template as a standard Web template for BEx Broadcasting, enter the technical name of the Web templates under Broadcasting.
To set your own Web template as a standard Web template for BEx Broadcasting for queries for the generation of documents, enter the technical name of the Web templates under Query Precalculation.
To set your own Web template as a standard Web template for reports, enter the technical name of the Web template under Enterpr. Reports.
Note that if you change settings, you have to restart the J2EE Engine before the changes become effective.
Regards,
Kams

Error in MSS-Create Requisition Request, form ISR_MSSRCF_SRQ3

Hi,
We are trying to configure MSS app, create requisition request using standard adobe form ISR_MSSRCF_SRQ3.
We have configured standard HCM process HR_MSSRCF_REQUISITION for it. When entering all
the mandatory fields in the form and clicking on 'check and send' , it displays an error
"you must enter a requisition title'
although we have already entered req. title in the field.
Anyone faced this issue before?
Please provide your inputs...
regards,
Smit

Hello smit ,
You can find out the enhancement ( BADI defnition ) that corresponds to MSS Requisition request .
Debugging the same will let you know why the error is coming .
You could also be due to config done under MSS -> recruitment.
hope this helps.
thanks,sahiba

Error in MSS iViews - Urgent

Hello All,
I've imported the MSS BP 60.1.5 (Based on Java) into the Portal Successfully. After creating a System Object 'SAP_R3_HumanResources' i'm trying to run the iviews however am getting a message "Could not connect to the R/3 System". I checked my DefaultTrace.trc file and found this:-
#SAPEngine_Application_Thread[impl:3]_39##0#0#Warning#1#/System/Server#Java###JCOClientService.getJCOClientPoolEntry: An exception occurred while connecting the client, forget this client: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed
Connect_PM TYPE=B MSHOST=qwamain.wdf.sap.corp GROUP=us0305.wdf.sap.corp R3NAME=QWA MSSERV=3311 PCS=1
ERROR       internal error
TIME        Wed Oct 26 15:44:04 2005
RELEASE     640
COMPONENT   MS (message handling interface, multithreaded)
VERSION     4
RC          -101
COUNTER     6
SAPEngine_Application_Thread[impl:3]_5##0#0#Error#1#/System/Server#Plain###[LoggerManager] Logger com.sap.pct.hcm.manager - definition not found! All mesagges will be send to the location com.sap.portal.portal. Please define the locationName in logger.xml. Method call stack - see trace message in com.sap.portal.runtime#
Please help in this as this is very urgent.
Regards
Vaibhav Dua

Hello Martin,
Thanks for helping me however this is not helpful to me as this discussion was about ESS/MSS based on WebDynPro where you have to configure the SLD as well.
I'm trying to run the MSS based on Java where no SLD is required (If i'm not wrong). Any other hints on this.
Regards
Vaibhav Dua

Error in mss

Similar Messages

Maybe you are looking for