Portal runtime error under travel/ESS/MSS

Dear all,
When we see privew under Employee self service --> ERP 2005 EhP2 --> iviews -->travel and expenses --> create travel request
Here I'm getting
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 02:19_26/02/11_0006_39627050
Refer to the log file for details about this exception.
But it is working fine under Employee self service --> iviews -->travel and expenses --> create travel request.
What could be reason, any body reply me.
I appreciate if any one can share the resolution
Regards,
Mahee.

Hi,
I have checked the following thread,
Travel Management--Webdynpro ABAP Services
I Have added system alias. now I'm getting different error,
Internet Explorer cannot display the webpage
What you can try:
    Diagnose Connection Problems 
     More information
This problem can be caused by a variety of issues, including:
Internet connectivity has been lost.
The website is temporarily unavailable.
The Domain Name Server (DNS) is not reachable.
The Domain Name Server (DNS) does not have a listing for the website's domain.
There might be a typing error in the address.
If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section.
For offline users
You can still view subscribed feeds and some recently viewed webpages.
To view subscribed feeds
Click the Favorites Center button , click Feeds, and then click the feed you want to view.
To view recently visited webpages (might not work on all pages)
Click Tools , and then click Work Offline.
Click the Favorites Center button , click History, and then click the page you want to view.
Awaiting for your valuable response.
thanks in advance.
Regards,
Mahee.

Similar Messages

  • Portal runtime error, when click on ESS MSS

    Dear Gurus,
    Whenever I click on any link of MSS, it gives me runtime error. Please see the screenshot.
    Portal runtime error
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID 03:38_14/05/14_0019_13493050
    See log file for details about this exception
    Screen shot
    - SSO steps configured
    - ESS/MSS roles given in both of ABAP and JAVA side
    ITS, connector and WEB AS test successfully (screen shot maintaned below)
    Only Alias defined : SAP_R3_HumanResources
    Detalied Error Log;
    Failed to invalidate cached entry for user a368ecb2db6411e3a030000000cde33a Exception:java.rmi.RemoteException: Cannot clear ICM server cache by [a368ecb2db6411e3a030000000cde33a] etag.; nested exception is:
    com.sap.bc.proj.jstartup.icmadm.IcmAdmException: interface disabled
    [EXCEPTION]
    java.rmi.RemoteException: Cannot clear ICM server cache by [a368ecb2db6411e3a030000000cde33a] etag.; nested exception is:
    com.sap.bc.proj.jstartup.icmadm.IcmAdmException: interface disabled
    at com.sap.engine.services.httpserver.server.CacheManagementInterfaceImpl.clearCacheByEtag(CacheManagementInterfaceImpl.java:33)
    at com.sap.netweaver.rtmf.serverimpl.users.RTMFUser.clearICMCache(RTMFUser.java:231)
    at com.sap.netweaver.rtmf.serverimpl.users.RTMFUser.doLogout(RTMFUser.java:296)
    at com.sap.netweaver.rtmf.serverimpl.users.UserList.removeUser(UserList.java:123)
    at com.sap.netweaver.rtmf.serverimpl.services.UserManagerService.doLogout(UserManagerService.java:590)
    at com.sap.netweaver.rtmf.serverimpl.services.UserManagerService.activeActionMethod(UserManagerService.java:100)
    at com.sap.netweaver.rtmf.serverimpl.services.UserManagerService.onMessageArrived(UserManagerService.java:71)
    at com.sap.netweaver.rtmf.serverimpl.services.UserManagerService.onUserMessageArrived(UserManagerService.java:698)
    at com.sap.netweaver.rtmf.messagingimpl.messages.RTMFMessageDispatcher.sendMessageToService(RTMFMessageDispatcher.java:45)
    at com.sap.netweaver.rtmf.serverimpl.core.MessageDispatcher.sendMessageToService(MessageDispatcher.java:46)
    at com.sap.netweaver.rtmf.serverimpl.core.MessageDispatcher.handleRequest(MessageDispatcher.java:72)
    at com.sap.netweaver.rtmf.serverimpl.core.dispatch.dispatchers.SendDispatcher.dispatch(SendDispatcher.java:37)
    at com.sap.netweaver.rtmf.serverimpl.core.RTMFCore.handleSendRequest(RTMFCore.java:190)
    at com.sap.netweaver.rtmf.serverimpl.core.RTMFCore.handleRequest(RTMFCore.java:154)
    at com.sap.netweaver.rtmf.serverimpl.server.RTMFServer.handleRequest(RTMFServer.java:89)
    at com.sap.netweaver.rtmf.servlet.ServletWrapper.doPost(ServletWrapper.java:54)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: com.sap.bc.proj.jstartup.icmadm.IcmAdmException: interface disabled
    at com.sap.bc.proj.jstartup.icmadm.IcmAdm.getInstance(IcmAdm.java:77)
    at com.sap.engine.lib.http.cache.CacheAdmin.getInstance(CacheAdmin.java:53)
    at com.sap.engine.lib.http.cache.CacheAdmin.invalidateCacheEntries(CacheAdmin.java:30)
    at com.sap.engine.services.httpserver.server.CacheManagementInterfaceImpl.clearCacheByEtag(CacheManagementInterfaceImpl.java:29)
    ... 56 more
    LOG OVERVIEW

    After implementing the PCUI_GP , ESS is not empty anoymore but it is giving error like this ;
    Detailed Error ;
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session O8h94DN06FMAxZD*frJ44w--szntRnBBZbpD5Fsc0H8XnA--/pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.roles/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.areagroup_overview/com.sap.pct.erp.ess.overview/sap.com/pcui_gp~xssutils/XssMenu/base/. The causing exception is nested. RID=50ba7f52dc4311e3bf72000000cde33a
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:663)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:349)
      at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:62)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.service(DispatchHandlerForRequestManager.java:39)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.service(DispatchHandlerForRequestManager.java:46)
      at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:270)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToAppContext(ExecutionContextDispatcher.java:68)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:53)
      at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:244)
      at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.callRequestManager(JavaApplicationProxy.java:1244)
      at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.callEmbeddedApplication(JavaApplicationProxy.java:1122)
      at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$StartCommand.doExecute(JavaApplicationProxy.java:1575)
      at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$AbstractCommand.execute(JavaApplicationProxy.java:1488)
      at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.execute(JavaApplicationProxy.java:1028)
      at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy.execute(JavaApplicationProxy.java:859)
      at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy.start1(JavaApplicationProxy.java:637)
      at com.sap.tc.webdynpro.portal.pb.impl.JavaApplicationProxyAdapter.create(JavaApplicationProxyAdapter.java:166)
      at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1661)
      at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:408)
      at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:638)
      at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:1087)
      at com.sap.portal.pb.PageBuilder$PhaseListenerImpl.doPhase(PageBuilder.java:2091)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:251)
      at com.sap.tc.webdynpro.clientserver.phases.PortalDispatchPhase.execute(PortalDispatchPhase.java:50)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
      at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
      at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:894)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
      at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)
      at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
      at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
      at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
      at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
      at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
      at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
      at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
      at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
      at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
      at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
      at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
      at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
      at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: com.sap.tc.webdynpro.services.exceptions.ApplicationFaultException: wdDoInit: exception thrown in this user coding area
      at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:164)
      at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:227)
      at com.sap.tc.webdynpro.progmodel.components.Component.initController(Component.java:258)
      at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:206)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:590)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1457)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:660)
      ... 78 more
    Caused by: com.sap.tc.webdynpro.progmodel.context.DictionaryException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
      at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getScalarType(DictionaryHandler.java:378)
      at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getDataType(DictionaryHandler.java:126)
      at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:438)
      at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:1002)
      at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:294)
      at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:974)
      at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:978)
      at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:67)
      at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:205)
      at com.sap.tc.webdynpro.progmodel.components.Component.getCustomControllerInternal(Component.java:668)
      at com.sap.tc.webdynpro.progmodel.components.Component.getController(Component.java:597)
      at com.sap.tc.webdynpro.progmodel.components.Component.getController(Component.java:552)
      at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:275)
      at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:190)
      at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:204)
      at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:105)
      at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:161)
      ... 84 more
    Caused by: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
      at com.sap.tc.webdynpro.services.datatypes.core.DictionarySetup$1.fillSldConnection(DictionarySetup.java:51)
      at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:437)
      at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:361)
      at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:198)
      at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:161)
      at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:96)
      at com.sap.dictionary.runtime.DdDictionaryPool.makeDictionary(DdDictionaryPool.java:75)
      at com.sap.dictionary.runtime.DdDictionaryPool.makeDictionary(DdDictionaryPool.java:63)
      at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:230)
      at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getScalarType(DictionaryHandler.java:370)
      ... 100 more
    Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
      at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:153)
      at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:161)
      at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:64)
      at com.sap.tc.webdynpro.services.datatypes.core.DictionarySetup$1.fillSldConnection(DictionarySetup.java:32)
      ... 109 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load client to connect to SLD. Please check your SLD connection settings using the Visual Admin.
      at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory$1.run(SystemLandscapeFactory.java:626)
      at java.security.AccessController.doPrivileged(Native Method)
      at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getClient(SystemLandscapeFactory.java:619)
      at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.readJCODestinationFromSLD(JCOClientConnection.java:458)
      at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:396)
      at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:237)
      at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:222)
      at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:84)
      at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:151)
      ... 112 more
    Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Getting CIMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
      at com.sap.sldserv.SldApplicationService.getCimClient(SldApplicationService.java:93)
      at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory$1.run(SystemLandscapeFactory.java:623)
      ... 120 more
    Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
      at com.sap.sldserv.SldApplicationService.getCimClient(SldApplicationService.java:75)
      ... 121 more

  • Portal Runtime Error  in ESS MSS Pages

    Hi All,
    We are getting following run time error from standard ESS transaction page. It is standard ESS iView and data showing correctly but this message is giving in the bottom of the page content area. We are using EP SP12 with 4.6c backend R/3 system.
    Any help or suggestions will be greatly appreciated.
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView
    Cannot assign a java.lang.String object of length 1,342 to host variable 1 which has JDBC type VARCHAR(1,333)..
    Exception id: 10:59_21/08/05_0008_1396450
    See the details for the exception ID in the log file
    Thanks,
    Laxma

    Hi Laxma,
    Change the objectids to something short.
    For now create a new folder structure with Object IDs shorter and move the content in the old folders to the new folders. For each object the name space is too long and is causing the path to exceed the defined limit.
    Regards
    -Venkat Malempati

  • Portal runtime error on creating Travel Request

    I have copied the standard ESS Role and created my own ESS Role. I then assigned this to my portal user.
    Then when I log into the portal as the user and click on "Create Travel Request" or "Create Expense Report" URLs, I get the following error:
    Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 04:53_02/02/10_0021_23623650
    Refer to the log file for details about this exception.
    Is there any portal/IMG setup that is missing? Or any authorization missing?

    Thanks I made changes to Resources node in IMG.
    Before making these changes I was getting the following error:
    Portal Runtime error. An exception occured while processing your request... Exception ID:.... Refer to log for details....
    I just changed the URL of PCD page in the Resources node.
    Note:
    (1) In Portal I have made my own folder structure:
    -> Portant Content
    -->My Travel Setup
    --->Employee Self-Service
    >Roles
    >MyTravelESS (role copy of the original Portal ESS role, Delta link. i.e. ESS role under End User Content-->Employee Self-Service)
    (2) I have not copied the iviews, pages worksets etc. under my new folder structure.
    But Now I am getting another error:
    500 Internal Server Error...
    Root Cause
    The initial exception that caused the request to fail, was:
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name base

  • MSS Portal Runtime error

    Hello Gurus,
    We have deployed the ESS/MSS business package on our portal.
    When we test the MSS business pack we are facing some issues.
    When we click on Budget and Planning we get the Portal runtime error.
    The error is "Portal Runtime error.
    An exception has occured while processing your request
    Exception id: 02:29_08/01/09_0001_324791850
    See the details for the exception ID in the log file.
    When checked the logs the error message we got is:
    Exception ID:04:03_08/01/09_0014_324791850
    [EXCEPTION]
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service/com.sap.pct.erp.mss.manager/overview/com.sap.pct.erp.mss.budget/com.sap.pct.erp.mss.budget_page/com.sap.pct.erp.mss.bw_cost_center
    Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
    User : wfman
                at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
                at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
                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:524)
                at java.security.AccessController.doPrivileged(Native Method)
                at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
                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:102)
                at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &#39;&lt;System.Access.WAS.protocol&gt;://&lt;System.Access.WAS.hostname&gt;/sap/bw/BEx?sap-client=&lt;System.client&gt;&amp;sap-language=&lt;Request.Language&gt;&amp;accessibility=&lt;User.Accessibility[SAP_BOOL]&gt;&amp;style_sheet=&lt;LAF.StylesheetUrl[url_ENCODE]&gt;&amp;&lt;TrayInformation[IF_true PROCESS_RECURSIVE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;Report&gt;&amp;&lt;BusinessParameters&gt;&#39;; the problem occured at position 82. Cannot process expression &lt;System.client&gt; because Invalid System Attribute:
    System:    &amp;#39;SAP_LocalSystem&amp;#39;,
    Attribute: &amp;#39;client&amp;#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)
                ... 29 more
    Can you please suggest what can cause this error.Please reply ASAP.
    Thanks in advance.
    Awaiting reply,
    Regards,
    Ramalakshmi.S
    Edited by: Ramalakshmi Pillay on Jan 8, 2009 8:05 PM
    Edited by: Ramalakshmi Pillay on Jan 8, 2009 9:51 PM

    HI,
    The error shows that you have not maintained the BW system.
    Create a BW system and maintained the connector and the WAS property. The was propert will be
    Protocol: http/https
    Host: <BW system hostname>:<port>
    Path: sap/bw/bex
    Maintain the system alias as SAP_BW.
    Try again
    Regards
    Deb

  • Portal Runtime Error in ESS iview

    Hi All,
    I have implemented ESS 50.4 on EP 6.0 SP9. For SAP IAC iviws i am getting following error.
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/AFDB/Role/ESSRole/Office/SAPInbox/SAPInbox
    Component Name : com.sap.portal.appintegrator.sap.IAC
    Error in executing a process for compilation.
    Exception id: 03:10_06/05/06_0031_4156850
    See the details for the exception ID in the log file.
    In the log file i am getting following error message.
    com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPEPPDB" is stopped or not started, 2) Connector service is stopped or has not been started.
    Please help me to resolve the problem its very urgent.
    Regards,
    Vaishali

    Hi Vaishali,
    Nice to hear from you again.
    Hope you are doing good.
    I am not sure whether the error that you mentioned is the right one for this issue, but if this is the case, just to inform you that a new note has been released in this regard. Please check sap note: 1600085 as well and set the parameters accordingly.
    Usually we need to see what kind of code is using the concerned connection.
    Incase the issue persists, proceed as follows (it wil be better to do this when the value of the number of connections is really high, so that identifying the root cause can be easy.
    1)
    Set the severity of "com.sap.engine.services.connector.jca.ConnectionHashSet" to DEBUG.
    You can change the severity of a location using the guide in the link below:
    http://help.sap.com/saphelp_nwce72/helpdata/en/47/af551efa711503e10000000a42189c/frameset.htm
    2)
    - connect to the AS-JAVA via telnet
    - then execute these commands:
    > add connector
    > switch_debug_mode SAPEPPDB (or the datasource name)
    > jump (to go to the next servernode if you have multiple ones)
    > add connector
    > switch_debug_mode SAPEPPDB
    ... and so on on all the servernodes
    - then wait for a few hours in order to see the connections not being
      released
    - go back to the telnet console and call:
    > list_conn SAPEPPDB -showTrace > server0.txt
    > jump
    > list_conn SAPEPPDB -showTrace > server1.txt
    ... and so on on all the servernodes
    The serverX.txt files will be generated in the ../j2ee/cluster/server directories. Just check them to get more info.
    Thank you!
    Kind Regards,
    Hemanth
    SAP AGS

  • Portal runtime error while trying to run a MSS report

    Hello gurus!!
       I setup the MSS reports launchpad and now I am seeing all the list of reports on the reports launchpad. I am able to click on all the links and each link opens up the relevant page and the selection criteria also comes up. However, on the last screen, I get a portal runtime error after I click on the report result button.
    The trace file shows the following errors:
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[./log/defaultTrace.trc]/>
    <!PATTERN[defaultTrace.trc]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[UTF8]/>
    <!FILESET[17, 20, 10485760]/>
    <!PREVIOUSFILE[defaultTrace.16.trc]/>
    <!NEXTFILE[defaultTrace.18.trc]/>
    <!LOGHEADER[END]/>
    #1.5 #0050568444360067000005D2000005D400049F27DC8DD843#1300893459438#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#sap.com/tcwddispwda#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#SSUBBARAO#113523##n/a##ae3b7a53556011e0cd95000000191d7e#SAPEngine_Application_Thread[impl:3]_23##0#0#Fatal#1#/Applications/Xss#Java###null
    [EXCEPTION]
    #1#com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
         at com.sap.xss.hr.cat.record.blc.RfcManager.rfcExecute(RfcManager.java:453)
         at com.sap.xss.hr.cat.record.blc.RfcManager.init(RfcManager.java:820)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.init(InternalRfcManager.java:280)
         at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onInit(FcCatRecordInterface.java:353)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface.onInit(InternalFcCatRecordInterface.java:268)
         at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface$External.onInit(InternalFcCatRecordInterface.java:542)
         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.xss.hr.cat.record.vac.calendar.VcCatCalendar.onInit(VcCatCalendar.java:251)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendar.onInit(InternalVcCatCalendar.java:194)
         at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendarInterface.onInit(VcCatCalendarInterface.java:162)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface.onInit(InternalVcCatCalendarInterface.java:146)
         at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface$External.onInit(InternalVcCatCalendarInterface.java:222)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1346)
         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.wdDoRefresh(PageBuilder.java:595)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:867)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
         at com.sap.xss.hr.cat.general.model.slim.CatsModelSlim.hrxss_Cat_Wd_Record(CatsModelSlim.java:245)
         at com.sap.xss.hr.cat.general.model.slim.Hrxss_Cat_Wd_Record_Input.doExecute(Hrxss_Cat_Wd_Record_Input.java:137)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
         ... 64 more
    Could anybody please guide me how to fix this error and get the reports working properly?
    Any help with this is much appreciated.
    Thank you!
    ~Maria Kutty~

    Hi,
    Please refer to note 878440.
    Thanks
    Prashant

  • Portal Runtime Error - MSS Implementation

    Hi,
    I am getting the following error in an iView for a MSS implementation (Workset: Employee Review/ Employee Document). The iView does not display correctly and I am showed the following error inside the iView:
    <i><b>Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/com.singaporeair.test/com.singaporeair.MSS/com.singaporeair.MSS_Roles/com.singaporeair.MSS_CRP/com.sap.pct.hcm.mystaff/nf_2/com.sap.pct.hcm.eereview/com.singaporeair.MSS_Employee_Document/com.sap.pct.hcm.employeedocuments
    Component Name : null
    Page could not create the iView.
    See the details for the exception ID in the log file</b></i>
    Any help on the above would be greatly appreciated!
    Thanks,
    Aniruddh

    1st question would be.. does that iview in that path actually exist.  If it does it may be worth delting it from the page and then adding it again.  if it doesn't, well that's your problem.
    If it does exit then try previewing it. Looking at the error (Component Name : null) it could be that the par file has not deployed properly, in which case it is basically pointing at java code that doesn't exist.  If that is the case look for any .err files at OS level, rename then to .par and restart j2ee.
    Paul

  • 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
    <i>
    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
    <i>
    <b>and  the error log file ...</b>
    <i>
    #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]<b>_15##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##</b>
    <i>
    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 &#39;&lt;System.Access.WAS.protocol&gt;://&lt;System.Access.WAS.hostname&gt;/sap/bc/webdynpro/&lt;WebDynproNamespace&gt;/&lt;WebDynproApplication&gt;/;sap-ext-sid=&lt;ESID[url_ENCODE]&gt;?sap-ep-iviewhandle=007&lt;ESID[HASH]&gt;&amp;sap-wd-configId=&lt;WebDynproConfiguration&gt;&amp;sap-ep-iviewid=&lt;IView.ShortID&gt;&amp;sap-ep-pcdunit=&lt;IView.PCDUnit.ShortID&gt;&amp;sap-client=&lt;System.client&gt;&amp;sap-language=&lt;Request.Language&gt;&amp;sap-accessibility=&lt;User.Accessibility[SAP_BOOL]&gt;&amp;sap-rtl=&lt;LAF.RightToLeft[SAP_BOOL]&gt;&amp;sap-ep-version=&lt;Portal.Version[url_ENCODE]&gt;&amp;sap-wd-tstamp=&lt;$TimeStamp&gt;&amp;&lt;FPNInfo[IF_false PROCESS_RECURSIVE]&gt;&amp;sap-explanation=&lt;User.Explanation[SAP_BOOL]&gt;&amp;&lt;StylesheetIntegration[IF_true PROCESS_RECURSIVE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]&gt;&amp;&lt;ForwardParameters[QUERYSTRING]&gt;&amp;&lt;ApplicationParameter[PROCESS_RECURSIVE]&gt;&#39;; the problem occured at position 310. Cannot process expression &lt;System.client&gt; because Invalid System Attribute:
    System:    &amp;#39;SAP_LocalSystem&amp;#39;,
    Attribute: &amp;#39;client&amp;#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

  • Portal runtime error in Purchasing in ESS

    Hello,
    After logging in to the portal, when I go to Employee Self-Services -> Purchasing, which ever option (Shop, Confirm Goods / Services, Check Status) I click, I get a portal runtime error as shown below:
    #1.5 #005056803084006B00000039000000FC0004638903CCAF24#1235340032299#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#smagan#23907##KSCEPD.esr.cri.nz_EPD_3051250#smagan#f667c1b0012b11deb880005056803084#SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#/System/Server#Java###Exception ID:11:00_23/02/09_0004_3051250
    [EXCEPTION]
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.roles/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.area_purchasing/com.sap.pct.erp.ess.purchasing_services/com.sap.pct.erp.ess.purchasing_service
    Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
    User : smagan
    at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
    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:524)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
    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: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)
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;&lt;System.Access.ITS.protocol&gt;://&lt;System.Access.ITS.hostname&gt;/sap&lt;ESID&gt;/bc/gui/sap/its/&lt;IAC[SAP_ITS_NAMESPACE]&gt;?sap-client=&lt;System.client&gt;&amp;sap-language=&lt;Request.Language&gt;&amp;sap-accessibility=&lt;User.Accessibility[SAP_BOOL]&gt;&amp;DisconnectOnClose=0&amp;DesignBaseUrl=&lt;LAF.BaseUrl[url_ENCODE]&gt;&amp;~design=&lt;LAF.Theme[url_ENCODE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;DynamicParameter[PROCESS_RECURSIVE]&gt;&amp;&lt;ForwardParameters[QUERYSTRING]&gt;&amp;&lt;ApplicationParameter[PROCESS_RECURSIVE]&gt;&\#39;; the problem occured at position 121. Cannot process expression &lt;System.client&gt; because Invalid System Attribute:
    System:    &amp;\#39;SAP_LocalSystem&amp;\#39;,
    Attribute: &amp;\#39;client&amp;\#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)
    ... 29 more
    Working Time, Timesheet, Personal Information, Pay Statement works perfectly. The error happens only in the case of Purchasing. I am new to ESS, so any help in this regard would be highly appreciated.
    Thanks,
    Ajay

    Hi Bala,
    It is happening for all users. I checked the authorizations in the backend. The roles assigned to the user has the following authorizations: S_RFC, S_SERVICE, S_TCODE, S_DATASET, S_TABU_DIS, S_WF_WI, P_TRAVL, PLOG, P_ABAP, P_ORGIN, P_ORGINCON, P_ORGXXCON, P_PCLX, P_PERNR, P_TCODE, M_BANF_BSA, M_BANF_EKG, M_BANF_EKO, M_BANF_WRK, M_BEST_BSA, M_BEST_EKG, M_BEST_EKO, M_BEST_WRK.
    In portal the user is assigned the ESS and Standard portal user role.
    The transaction ST22 shows the following:
        The user "TESTUSER9" has no RFC authorization for the function group                         
        "SDIFRUNTIME". Please contact your system administrator to give you                          
        the RFC authorization for the required function groups (such as "SDIFRUNTIME").              
        The RFC authorization object is S_RFC.
    Thanks,
    Ajay

  • Reporting IAC not working in MSS/Time Administrator - Portal Runtime Error

    Hi Experts,
    I am having some problems viewing the Report Results after executing the Reporting IAC in the MSS and TA roles.
    I select a report from the list, click on Define Selection Criteria, select an employee, then the Report Result pops up in a new window.  However, this is where the error occurs as the new window displays a portal runtime error.
    Can anyone help me with this?
    Thanks,
    Oloy.

    What portal version and business package are you using?  What is the backend system release?
    What sort of report is it?
    Is your WEBGUI service activated and tested in the internal ITS?

  • 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 &#39;&lt;System.Access.WAS.protocol&gt;://&lt;System.Access.WAS.hostname&gt;/sap/bw/BEx?sap-client=&lt;System.client&gt;&amp;sap-language=&lt;Request.Language&gt;&amp;accessibility=&lt;User.Accessibility[SAP_BOOL]&gt;&amp;style_sheet=&lt;LAF.StylesheetUrl[url_ENCODE]&gt;&amp;&lt;TrayInformation[IF_true PROCESS_RECURSIVE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;Report&gt;&amp;&lt;BusinessParameters&gt;&#39;; the problem occured at position 82. Cannot process expression &lt;System.client&gt; because Invalid System Attribute:
    System:    &amp;#39;SAP_LocalSystem&amp;#39;,
    Attribute: &amp;#39;client&amp;#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)

  • EP6.0SP2: MSS teamviewer -  portal runtime error

    Hi all,
    could you provide me with information how to solve this problem:
    We implemented the BP MSS 60.1.2 . Now only a few iviews are working fine - he most of them occur this error:
    Portal Runtime Error - ... - tcom/sap/pct/hcm/orgmanagementeventing/CKey.
    The teamviewer is not working neither, here this error appears:
    Portal Runtime Error - ... -
    Component Name : null
    Page could not create the iView
    I have found some similar topics within the sdn forum, but the only solution mentioned there are to reimplement MSS 60.1.1 .
    Is this the only solution for this foreseen ??
    Thanks in advance for your help.
    Sandra

    1st question would be.. does that iview in that path actually exist.  If it does it may be worth delting it from the page and then adding it again.  if it doesn't, well that's your problem.
    If it does exit then try previewing it. Looking at the error (Component Name : null) it could be that the par file has not deployed properly, in which case it is basically pointing at java code that doesn't exist.  If that is the case look for any .err files at OS level, rename then to .par and restart j2ee.
    Paul

Maybe you are looking for