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.

Similar Messages

  • 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)

  • Portal Runtime Error when previewing iViews from BP for CRM 4.0 (60.2)

    Hello,
    We have imported Business Package for CRM 4.0 (60.2) into EP 6.0 (Version: 6.0.19.0.0) according to the installation guide(InstGuide_EN_CRM40_502.pdf). We have also defined SAP_CRM and SAP_R3 Systems in  Portal System Landscape Editor. And we have also set the permissions for the user with which we are logged in on the "Portal Content->Migrated Content->EP 5.0" folder with "Read" permission and checked the "End User" option.
    Now when we do a test preview for "Portal Content->Migrated Content->EP 5.0->iViews->SAP CRM 4.0: Sales->Activities" iView in PCD i get Portal Runtime Error in a new window with following information:
    <b>Portal Runtime Error
    An exception occurred while processing a request for :
    iView : com.sap.portal.appintegrator.sap.BSP
    Component Name : com.sap.portal.appintegrator.sap.BSP
    Error occurs during the rendering of jsp component.
    Exception id: 08:40_22/01/07_0001_6052850
    See the details for the exception ID in the log file
    </b>
    We get this similar message for few other iViews as well. Following is the details from the log file for this exception ID:
    <b>###Exception ID:08:40_22/01/07_0001_6052850
    [EXCEPTION]
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
    Component : com.sap.portal.appintegrator.sap.BSP
    Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
    User : <USER_ID>
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
         at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
         at com.sapportals.portal.appintegrator.Utils.includeJSP(Utils.java:199)
         at com.sapportals.portal.appintegrator.layer.HTTPRenderLayer.render(HTTPRenderLayer.java:249)
         at com.sapportals.portal.appintegrator.LayerProcessor.processContentPass(LayerProcessor.java:226)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:100)
         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.sapapplication.bwc.AbstractBWCComponent.doContent(AbstractBWCComponent.java:63)
         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:646)
         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(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         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:160)
         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.component.PortalComponentException: Error occurs during the compilation of java generated from the jsp
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:108)
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:140)
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:291)
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:141)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
         ... 46 more
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2189)
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:81)
         ... 52 more
    </b>
    Why am i getting this error page and how to resolve this? Please help. Thanks.
    Regards,

    I am facing one more problem now. I tried to create a new user in Portal and when i try to login with this new account i get following error message:
    <b>Portal Runtime Error
    An exception occurred while processing a request for :
    iView : com.sap.portal.runtime.logon.default
    Component Name : com.sap.portal.runtime.logon.default
    Error occurs during the rendering of jsp component.
    Exception id: 10:04_22/01/07_0010_6052850
    See the details for the exception ID in the log file</b>
    Following is the error message snippet from the log file for this exception ID:
    <b>
    ###Exception ID:10:04_22/01/07_0010_6052850
    [EXCEPTION]
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
    Component : com.sap.portal.runtime.logon.default
    Component class : com.sapportals.portal.ume.component.logon.SAPMLogonComponent
    User : J2EE_GUEST
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
         at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
         at com.sap.security.core.logonadmin.ComponentAccessToLogic.gotoPage(ComponentAccessToLogic.java:109)
         at com.sap.security.core.sapmimp.logon.SAPMLogonLogic.executeRequest(SAPMLogonLogic.java:251)
         at com.sapportals.portal.ume.component.logon.SAPMLogonComponent.doContent(SAPMLogonComponent.java:37)
         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.ume.component.logon.SAPMLogonCertComponent.doContent(SAPMLogonCertComponent.java:33)
         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:646)
         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(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.sap.portal.navigation.Gateway.service(Gateway.java:101)
         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:160)
         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.component.PortalComponentException: Error occurs during the compilation of java generated from the jsp
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:108)
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:140)
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:291)
         at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:141)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
         at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
         ... 49 more
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2189)
         at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:81)
         ... 55 more</b>
    Though i am still able to login with any of my old accounts, but not with the newly created ones. I thought this might have been because of the new roles that i assigned, but i see the above error message even when i haven't assigned any role. How do i get rid of this one now?
    Thanks and Regards,

  • 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 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

  • Gettin a portal runtime error when adding iviews in web page composer

    we are getting the Following error when we try to add a iview in page builder .we have done the configurations as per the documentation ((http://help.sap.com/saphelp_nw70/helpdata/en/45/3fe7b4f34d4a18e10000000a114a6b/frameset.htm).and will appreciate any help on this issue .
    Portal Runtime Error
    An exception occurred while processing your request
    Exception id: 08:09_31/10/07_0015_15308650
    See the details for the exception ID in the log file.
    #1.5 #00145ECC9C67007E000000190000117800043DC0D68F6E39#1193798349688#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#myadmin#5872##myportalci.keells_JPP_15308650#myadmin#015ef900875a11dc8a3700145ecc9c67#Thread[PRT-Async 2,5,PRT-Async]##0#0#Error##Java###08:09_31/10/07_0015_15308650
    [EXCEPTION]
    #1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Can&\#39;t read the prameter &\#39;siteString&\#39; from the PCD.
         at com.sapportals.portal.httpconnectivity.urliviews.runtime.URLIView.checkPCDVal(URLIView.java:631)
         at com.sapportals.portal.httpconnectivity.urliviews.runtime.URLIView.readFromPCD(URLIView.java:528)
         at com.sapportals.portal.httpconnectivity.urliviews.runtime.URLIView.doContent(URLIView.java:326)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:149)
         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.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:355)
         at com.sapportals.portal.prt.core.async.AsyncPortalComponentResponse.include(AsyncPortalComponentResponse.java:310)
         at com.sap.nw.wpc.runtime.AbstractContainerComponent.doContent(AbstractContainerComponent.java:88)
         at com.sap.nw.wpc.runtime.ContainerComponent.doDesign(ContainerComponent.java:183)
         at sun.reflect.GeneratedMethodAccessor362.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:134)
         at com.sapportals.portal.prt.component.CachablePortalComponent.service(CachablePortalComponent.java:273)
         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.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:375)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:388)
         at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)
         at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
         at java.lang.Thread.run(Thread.java:534)

    Dear Prabash Balsuriya,
    I got similar issue while adding iView to WPC during public, can you elaborate how you solve this issue?
    Thanks.
    Regards,
    Weng

  • Portal Runtime Error in WD iViews during iView personalization

    Hi,
    I am using SAP's MDM iViews with some custom webdynpro application iViews in my netweaver portal 7.0.  When I click on the personalize 'apply' button of any iView, the whole page gets refreshed. The standard SAP MDM iViews gets rendered without any problems.  But the custom webdynpro iViews throw portal runtime error as shown below:
    Portal Runtime Error
    An exception occurred while processing your request
    Exception id: 02:25_17/12/08_0106_18297950
    Can anybody throw some light on this?
    Regards,
    Yuvaraj SG

    Hi Yuvaraj,
    Assign the user super admin role and see if the page opens fine or not.
    If the page opens fine, remove the super admin role and check the permissions for the custom web dynpro applications.....
    and see if enduser check box is marked or not.
    And at the same time check the permissions of the content provided by SAP folder and your custom folder where you have similar roles or not.
    For this navigate to System Administration - Permissions - Portal Content
    For detailed analysis check nwa as suggested by Bala.
    Hope this helps.
    Cheers-
    Pramod

  • Portal Runtime Error for "com.sap.portal.toolAreaiView"

    Hi EP Gurus,
    We are using EP6 SP11 Patch3 installed on UNIX and Windows machine as well.
    We are getting following error message:
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/com.lti.I-1192_fldr_01/
    com.lti.I-1192_fldr_17/I-1192_desktop/
    frameworkPages/frameworkpage/com.sap.portal.toolAreaiView
    Component Name : com.sap.portal.navigation.toolarea.default
    Each time when we got this message we have to restart the j2ee engine and then everything works fine.
    Also we are facing this problem on UNIX machine only(not on windows)
    Can anybody help me out with this?
    With regards,
    Amol

    Hi Dieter,
    Thanks for the reply...........
    But the log files are not getting generated(which did generate earlier), i dont know whats the problem.
    If u can plz help me....
    With regards,
    Amol.

  • Portal Runtime Error for "toolAreaiView"............??

    Hi all,
    We are using EP6 SP11 Patch3 installed on UNIX.
    We are getting following error message after some time:
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/com.lti.I-1192_fldr_01/
    com.lti.I-1192_fldr_17/I-1192_desktop/
    frameworkPages/frameworkpage/com.sap.portal.toolAreaiView
    Component Name : com.sap.portal.navigation.toolarea.default
    Each time when we got this message we had restarted the j2ee engine and then everything works fine.
    Can anybody help me out with this?
    With regards,
    Amol

    Has anybody face this problem earlier?????????

  • Portal Runtime Error for WPC user

    Hi experts,
    I assign wpc_editor_role for my user. But he is getting Portal Runtime error everytime he try to create link list/teaser/paragraph, publish webpage, finish webpage. The error is as follows:
    Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 10:55_27/05/09_0002_21582350
    Refer to the log file for details about this exception.
    For your information, the WPC is working fine for administrator ID. Please help me to solve this problem.
    Rgds,
    Nanie Arianie

    Nanie,
    Please ensure that you have the permissions set as per this help.
    [Defining Permissions in the Portal Content Studio|http://help.sap.com/saphelp_nw70/helpdata/EN/45/f91dd13c7a04aae10000000a114a6b/content.htm]
    [Setting Initial Permissions for Folders|http://help.sap.com/saphelp_nw70/helpdata/EN/a6/78aa5c2ab64c1d83db59a25793e9eb/content.htm]
    This should ensure that your issue is taken care of.
    Good Luck.
    Cheers!
    Sandeep Tudumu

  • Portal runtime error - for Universal Worklist

    Hi All,
    We have upgraded SAP Portal from 7.0 to 7.3 Ehp1, after upgrade we faced some issues and have resolved those.
    Right now some tabs in the portal is working fine whereas Universal Worklist and some tabs are throwing runtime error, where it shows "No logon ticket available" in trace file.
    I have checked login module components in nwa and it shows as
    EvaluateTicketLoginModule SUFFICIENT
    BasicPasswordLoginModule REQUISITE
    CreateTicketLoginModule OPTIONAL
    Please find the below trace details. Kindly suggest your views.
    Thanks in advance !!!!!
    05:24:13:181#0-800#Error#com.sap.portal.prt.runtime#
    #EP-PIN-PRT#tc~epbc~prtc~api#C000A7EEAF6101B000000002000043B0#14599450000000004#sap.com/com.sap.portal.runtime.system.hooks#com.sap.portal.prt.runtime#C933075#83##9C25C9AEA5FB11E38FEB000000DEC51A#be36c9ada5fb11e39ffa000000dec51a#be36c9ada5fb11e39ffa000000dec51a#0#Thread[HTTP Worker [@1426801953],5,Dedicated_Application_Thread]#Plain##
    [EXCEPTION]
    com.sapportals.portal.appintegrator.ApplicationIntegratorException: com.sap.security.api.umap.NoLogonDataAvailableException: No logon ticket available.
    at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
    at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:106)
    at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:53)
    at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:30)
    at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
    at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:175)
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:111)
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:70)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:398)
    at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$1.service(RequestDispatcherFactory.java:168)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:292)
    at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.handleEvent(RequestDispatcherFactory.java:158)
    at com.sap.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:242)
    at com.sap.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:342)
    at com.sap.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:732)
    at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:473)
    at com.sapportals.portal.prt.connection.ServletConnection._handleRequest(ServletConnection.java:224)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:101)
    at com.sap.portal.prt.dispatcher.DispatcherServlet.service(DispatcherServlet.java:132)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
    at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
    at com.sap.portal.prt.dispatcher.CustomHeaderFilter.doFilter(CustomHeaderFilter.java:58)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
    at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:441)
    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:278)
    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.security.api.umap.NoLogonDataAvailableException: No logon ticket available.
    at com.sap.security.core.umap.imp.authndata.LogonTicketAuthnData.<init>(LogonTicketAuthnData.java:57)
    at com.sap.security.core.umap.imp.authndata.AuthnDataFactory.getAuthnData(AuthnDataFactory.java:76)
    at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:257)
    at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:94)
    ... 64 more

    Hi,
    Did you implement SSO in the 7.31?
    BR,
    Saar

  • Alert Mail configuration in Solution Manager 7.1 for Portal Runtime errors

    Dear Friends,
    We have EP7.01 SP5  installed on windows environment with Oracle DB. Also we have  SAP EHP 1 for SAP Solution Manager 7.0.
    Please help to provide steps to configure
    proactive mail alert configuration ,
    GRMG for High availability
    Any portal runtime errors
    for PORTAL services in Solution Manager.
    Regards,
    Venkat.

    Hello Venkat,
    You will have to include the Portal system in the Central System administration of your Solution Manager.
    As the EP system will be monitored by a sapccmsr running with -j2ee option this one can be configured separately. The agent will be started using the monitoring segment of the J2EE instance and therefore can be started more than once.
    Here you should also use the latest sapccmsr agents.
    The following link provides details on the required agents:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ca/118110ff542640b7c86b570cc61ae3/frameset.htm
    Please refer the below notes.
    214247     RZ20: Questions on configuration of monitoring data
    704349     Activating the CCMS monitoring for TREX 6.1 (NW2004
    Note the EP system can only be monitored by using the SAPCCMSR agents. and then by implement a central autoreaction method you can generate e-mails from CCMS.
    Automatic emails will get generated when certain thresholds are met. You must configure the thresholds from the central monitoring system for the nodes that you want email to be generated.
    Please follow the steps in the note to configure central auto reaction.
    429265 CCMS monitor architecture: Central auto-reaction
    In the central monitoring system ( Solution Manager in your case ), Goto RZ20, choose the monitor for the nodes that you are monitoring. Select the node, click properties, & check the threshold values.
    Also refer to the following notes:
    547024 - Transfer the EP 5.0 Monitoring-Data to SAP CCMS
    644783 -P 6.0 Monitoring via CCMS / SolMan
    Also, check the following link that has information on portal monitoring  :
    http://service.sap.com/~sapidb/011000358700002004322004E
    I guess this is a whole lot of information to assimilate and will be helpful to you to setup what you intend to.
    Regards
    Amit

  • Portal Runtime Error in contentCatalogTree after applying SP11

    HI,
    I am getting a POrtal Runtime Error for the contentCatalogTree iView after I applied SP11. It was working fine before I patch the portal. Has anyone got a solution to this?
    Here is the error stack:
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    iView not found: pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.content_administration/com.sap.portal.portal_content/com.sap.portal.contentCatalogTree.
    Exception id: 09:49_11/04/05_0022_6990050
    See the details for the exception ID in the log file
    And the log file says:
    #1.5#001279D06329005D0000000700000F280003F423583156CF#1112857570796#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#178####856f12c0a73311d9b39c001279d06329#SAPEngine_Application_Thread[impl:3]_23##0#0#Error#1#/System/Server#Java###Exception ID:03:06_07/04/05_0005_6990050
    [EXCEPTION]
    #1#com.sapportals.portal.prt.runtime.PortalRuntimeException: iView not found: pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.content_administration/com.sap.portal.portal_content/com.sap.portal.contentCatalogTree
         at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1937)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:230)
         at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
         at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
         at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:435)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Anyone out there can help. Thanks in advance.

    Hi all,
    Apprantly it seems that the sequence to applying the SP Stacks plays a part. I reverted back to SP9 then went on to SP10, SP10 patch2 and then SP11 and it appears fine now.
    Cheers

  • Two iView(out of three) give Portal runtime error when refresh MSS-UWL Page

    Hi All,
    i am getting the Portal runtime exception in the MSS->Work Overview ->2nd and 3rd iView on this page.
    First iView is the UWL-Task 2)Attendance Overview and 3) Work Orders
    When i refresh this page "refresh" from pae level refresh. i am getting the below error on 2nd and 3rd iView. Last 2 iView is not displaying.
    Portal Runtime Error
    An exception occurred while processing your request
    Exception id: 02:02_12/01/09_0039_38688450
    See the details for the exception ID in the log file.
    i have tryed to search the log also in the default trace but can not find any log with this exception ID.
    Please suggest me on this ?
    thanks in advance!
    Narpal S Sihag

    Hello,
    I have also a problem like this (error 09_0006_808022650)
    Can you describe your scenario ?
    My scenario is
    - Portal MDM connection OK and working tasks in MDM
    - new UWL System (connector type : MdmUwlConnector)
    - new config file (XML)
    - dedicated Role and dedicated iView (copy of standard UWL iView)
    - clearing cache
    Test : No working Tasks in UWL
    - restarting portail application com.sap.netweaver.bc.uwl
    Test : No working Tasks in UWL
    - running wizard (System Admin, system config, UWL customize IView)
    - new field "TEST" to iView
    - portail create the com.sap.pct.erp.mss.001
    Test : No working Tasks in UWL
    Test : standard UWL crashes with error 09_0006_808022650
    After what, we try roolback, removing XML config, connection, dedicated iView, ...
    Still crashing with error 09_0006_808022650
    Now our developpemnt system don't work for UWL ... (using UWL with ECC connection and was OK for ECC)
    Questions : is your scenario similar to this one ? Is anyone can help us ?
    My best thanks
    Vincent

Maybe you are looking for

  • Stock as on past dates

    Hi all, I have a requirement to audit stock differences that had happened few months back between SAP and BI. The stock in BI has a cumulative figure of all stock categories viz. unrestricted, in transit, blocked and QI. In SAP, I can get the unrestr

  • I don't want a new row for each line of text

    I have exported a pdf document which is a table full of text in columns (by month). The conversion seems to react randomly so that in some places several lines of text in a column are converted to just one cell (great, just what I want) and then in o

  • Unwanted SMS without number (without using iMessage)

    hi all! A few months back, I began receiving spams (unwanted sms) on my phone, from websites and stuff, and I found out that they were coming through iMessage and that there was nothing to do about it. But it's been a few weeks now that I have been r

  • WEP network does not work

    After upgrade to Snow Leopard, I tried to connect to my home network. It uses plain WEP key (ASCII key, not a "password"). My network at work uses WPA and after upgrade, it just worked, I did not have to set any keys or anything. Home network with WE

  • Oracle Geeks Products Survey

    Dear oracle geeks/gurue We are a startup company that sell apparels and accessories with oracle bugs and error messages on those products. we are currently sizing the oracle market and it will be great if you can take time to fill our 5 min. survey.