Portal Runtime Error after System Refresh

Did a system refresh and now when I select a BI workbook that executed before the refresh I receive the error
"portal runtime error
an exception occurred while processing your request
exception id:09:27_07/02/11_0018_2780350
see the details for the exceptio id in the log file". 
Queries run without erroring only the workbooks give this error... apprecitate any help - thanks

Hi Annette,
Did you clear all the cache, closed the browser and try again?
If the error still appears, check the error log.
Where are you checking the BI workbook? Is it through portal is it through an iview? If yes then check if the
application runs when the iview is previewed directly.

Similar Messages

  • Portal runtime error after modifying masthead par file

    Hi experts,
    i tried to upload com.sap.portal.navigation.masthead.par in the portal (productive system) after modifying tooltip text of u201CHelpu201D link. i used Archive uploader.
    After upload, status messages are correct.
    But now in the masthead area, i have red message :
    "Portal runtime error"
    "An exception occurred while processing your request"
    I cannot also access the Browse Deploymentu2026
    So now i cannot log off from the portal (except by restart computer)
    In development system where I used the same procedure, everything is OK.
    Please help!

    Dev,
    Please ensure that the changes are correct by to upload the orignial par.
    The other way of modifying the par is as below,
    *Upload the PAR into NWDS and add the jars htmlb.jar, com.sap.portal.htmlb_api.jar and servlet.jar through java build path of your par project and add the jar com.sap.portal.navigation.masthead_core.jar (you can get this by extracting your par and navigate to the folder PORTAL-INF -> lib) in PORTAL-INF -> lib folder of your project.
    Make changes
    Build project
    Export into portal
    Ram

  • Portal Runtime error after applying patch 12 to portal

    hi experts,
    i m getting following error
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.content_administration/com.sap.portal.content_admin_ws/com.sap.portal.webdynpro_ws/com.sap.portal.content_administrator/com.sap.portal.wd_content_administrator
    Component Name : com.sap.portal.appintegrator.sap.WebDynpro
    Exception in SAP Application Integrator occured: ApplicationIntegratorException.
    Exception id: 09:30_22/01/08_0005_16892850
    See the details for the exception ID in the log file
    after applying patch 12 in portal
    i m getting this error in guided procedures,Universal worklist ,webdynpro workset undfer content administration
    Please suggest me the solution
    regards,
    vani

    Hi Vani,
    Just go to the System Configuration and UME configuration.
    Now go to user mapping tab, and remove the entry for a reference system. Then check for the issue if persists, restart system.
    Hope this helps!
    regards
    Atul Shrivastava

  • Portal Runtime Error after Upgrade 7.01 to 7.3

    Hi,
    i have a Problem after Upgrade a BW 7.01 to 7.3 SP5 the,
    abap works fine but the Java Portal bring up Error on many time by choosing any funktion
    for example:
    try to use Portalcontent -> Systemlandscape -> SAP_BW
    this error is shown.
    Portal Runtime Error
    Tracefile:
    2011 11 24 13:05:51:546#+0100#Error#com.sap.portal.prt.connection#
    #EP-PIN-PRT#tcepbcprtc~api#C0000A11295500740000000000E900F2#9281050000000004#sap.com/irj#com.sap.portal.prt.connection#FREYAD#3##8D780B5716941                             1E1C8790000008D9E1A#a6e61adf169411e1cab50000008d9e1a#a6e61adf169411e1cab50000008d9e1a#0#Thread[HTTP Worker [@904797166],5,Dedicated_Application_                             Thread]#Plain##
    Exception ID:01:05_24/11/11_0004_9281050
    [EXCEPTION]
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Application name : com.sap.portal.appdesigner.framework
    Component : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.pcmEditor
    Component class : com.sap.portal.admin.propertyeditor.core_functionality.PCMEditor
    -all Funktions in NWA are working
    -Diagnose an Supporttool is Green !
    Thanks Steven

    Hi Raj,
    You need to redeploy the patches in the message from Alexandra.
    How to redeploy same component with JSPM?
    JSPM does not allow to deploy an SCA with the same version (release, SP-level, patch-level) as an already deployed component. However, in some special cases you may need to redeploy an SCA with the same version. Use command line:
    go "-config=/jspm/forceMode=true" "-config=/jspm/deployVersionRule=updateAll" to redeploy all SDAs. See note #1123333 for more options.
    regards
    Steven

  • Portal Runtime Error after Portal SP21 Patch Update

    Dear GURU's,
    Greetings!
    We have installed and configured SAP Netweaver 2004 WAS Java and have EP 6.0 SR1 - SP9 system on Windows Server 2003, Enterprise Edition Service Pack 2 and MS SQL Server 2005 Service Pack 2.
    We had connected the server to the backend R3 system and completed all the configurations for an HCM implementation with KMC. We had updated the SP level from SP9 to SP21.
    When we were trying to access the portal system today we found a Portal Runtime Error when we launched the Portal URL. The error is mentioned below.
    Portal Runtime Error
    An exception occurred while processing your request
    Exception id: 07:02_06/11/08_4102050
    See the details for the exception ID in the log file.
    We had not changed any of the configurations in the system, we also had experienced the same error in the UWL Administration link in the portal system and our portal consultant was working on the same.
    Please help us in solving the error. We would be glad to know the reason of the error and also the measures to avoid the same in the future.
    Expecting your reply at the earliest.
    Thank you
    Regards,
    Vineeth

    Dear Ravi & Vamshi,
    Thank you very much for the reply.
    I solved this error.
    This is caused due to insufficient permissions that is configured in the security zones of the portal system.
    The below mentioned document specifies further details and inital permission settings,
    https://www.sdn.sap.com/irj/sdn/nw-portalandcollaboration?rid=/library/uuid/00bfbf7c-7aa1-2910-6b9e-94f4b1d320e1
    Thank you
    Regards,
    Vineeth

  • Portal runtime error after migrating to 7.3

    Hi,
    We have an enterprise portal --> portal application standalone type DC. We have been able to migrate the DCs to 7.3. The problem we are facing currently is that one of the applications does not load in the portal giving a portal runtime error. Looking at the log files, the errors being shown are to do with one specific type of class.
    setClientEvent(com.sapportals.htmlb.enum.EventTrigger,java.lang.String) in com.sapportals.htmlb.EventValidationComponent cannot be applied to (com.sapportals.htmlb.enums.EventTrigger,java.lang.String)
                         CustomerInput.setClientEvent(com.sapportals.htmlb.enums.EventTrigger.ON_KEYDOWN, "onCustomerEnter()");
    The above error shows that at runtime, it is trying to resolve 'com.sapportals.htmlb.enum.EventTrigger' but this class is deprecated in 7.3. The code which we have written has the right package which is com.sapportals.htmlb.enums.EventTrigger.
    I am not sure why it is still trying to resolve with an older version. If I try to change the code and use the 'enum' package instead of 'enums', then the application fails again with the runtime error.
    Thanks & Regards,
    Vaishnavi

    Closing this thread as it was solved. Apparently, there is a java method setClientEventExt() which takes an eventtrigger and an event as inputs.
    Regards,
    Vaishnavi

  • Portal Runtime Error after Login into EP

    Hi all,
            when i login into SAP Enterprise Portal,It is throwing Portal Runtime Error.
    Error as follows :
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    com.sapportals.portal.navigation.INavigationNode.getHashedName()Ljava/lang/String;.
    Exception id: 04:59_17/06/06_0022_1660050
    See the details for the exception ID in the log file
    How to Rectify this Error,Plz help me Out.
    I will reward with the Points.
    Thanks and Regards
    Santosh Saraf

    Hi Santosh,
    This is related to memory issue...delete all the cookies and restart ur server..
    regards
    Amit

  • DTP transport error after system refresh

    Hi Experts,
        The scenario is that Dsystem has already refreshed data from Psystem,and then error occured when transport DTP from D to Q system.
        As per the threads before, i know that we can trace  DTP technical name in table RSBKDTP.
        That i show the detail as the field from RSBKDTP in the below,
    Before refresh,
    System        DTP technical name     DTP original technical name  
    P                  DTP2                            DTP0
    Q                  DTP1                           DTP0
    D                  DTP0                            DTP0           
    After refresh P to D,
    System        DTP technical name     DTP original technical name  
    P                  DTP2                            DTP0
    Q                  DTP1                           DTP0
    D                  DTP2                         DTP0   
    Then the transport error from D to Q caused by that the two name underlined is not corresponding.
    Could anybody give me advice to solve the problem, if not ,i could only creat a new DTP in D.
    I am currently trying to find an solution and I will share if I find. Thanks.
    Edited by: rurupolo on Jul 15, 2010 5:20 PM

    Hi Friend,
    Just activate the DTP2 in D again and transport to Q.  It should work.
    Regards
    Hemant Khemani

  • Getting RFC error After system Refresh

    HI Gurus,
    Recently our SRM  QA client was refreshed from Prod and all the RFC connections are pointing to R/3 Production client instead of R/3 QA Client. Because of this reason we are unable to replicate the Product ID's from R/3 to SRM. Also all the attribute values are showing the source sustem as Producion instead of QA R/3.
    We have verified the following and everything looks good.
    1. Table CRMMLSGUID - R/3 logical system as QA R/3.
    2.We ran the report RHOMATTRIBUTES_REPLACE  for the attribute SYS but.no update.
    3.SPRO u2192 Supplier Relationship Management u2192 SRM Server u2192 Technical Basic Settings u2192 ALE Settings (Logical System) u2192 Distribution (ALE) u2192 Basic Settings u2192 Logical Systems u2192 Define Logical System.
    4.SPRO -->Supplier Relationship Management -->SRM Server ->Technical Basic Settings ->Technical Basic Settings.
    5. SPRO ->Supplier Relationship Management -->SRM Server ->Technical Basic Settings ->Define Backend System for Product Category.
    Your response is highly appreciated.
    Thanks,
    Sada.

    Hi,
    After refresh to QA, there may be refresh fpr RFC users.
    Please check
    a)RFC Users with Pwd are exists , if not create new.
    b) Maintain those users /pwd/client in SM59.
    Hope this will work for it.
    Rahul Mandale

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

  • Portal Runtime Error while creating  new system in portal content

    Hi
      Can anyone  solve my problem, i am geting error while creating new system in p ortal content
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.templateSelection
    Component Name : com.sap.portal.admin.templateselectionwizard.default
    com/sap/portal/iviewserver/cache/OClass.
    Exception id: 11:29_26/12/06_0014_5891950
    See the details for the exception ID in the log file

    Hi,
    Check this link for creating system object
    http://help.sap.com/bp_epv260/EP_EN/documentation/EP/N03_BB_InstallGuide_EN_US.doc
    Regards
    Arun

  • Portal runtime error: where can I find the system log?

    I got a portal runtime error. Like this:
    Portal Runtime Error
    An exception occurred while processing your request
    Exception id: 10:22_16/05/08_0007_13424550
    Where can I find the log file / more details?
    Thanks
    René

    Hello rene,
    2 ways for accessing log: 
    1) browse portal filesystem : \usr\sap\J2E\JC00\j2ee\cluster\<server instance>\log\
    2) use sap log applications
    I suggest you to use logviewer or visual admin(it contains logviewer) applications. It will display formated logfile and you will be able to filter on severity / User Name / date / .......
    if you are using visual admin, just connect with Visual Admin then browse to  <server name> / services / log viewer then  again <server name> \usr\sap\J2E\JC00
    j2ee\cluster\server0\log and then click on defaultTrace.trc
    it is pretty the same navigation when using logviewer
    Kind Regards
    Cedric Meyer

  • Portal Runtime Error while accessing BW reports through portal

    Hi,
    We are facing portal runtime error(An exception occurred while processing your request. Please send the exception id to your portal administrator) while accessing BI reports through portal frequently.
    We are unable to trace the error in the 'default trace' log file and although refreshing the cache solves this issue, it is difficult to explain this to every user individually.
    After many such errors, We found one log entry, which we are now not yet sure if it is relevant. The error states:
    1.
    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;&lt;BWLauncherComponent[PORTAL_URL]&gt;;jsessionid=&lt;Request.JSessionID&gt;?sap-ext-sid=&lt;ID[url_ENCODE]&gt;&amp;Language=&lt;Request.Language&gt;&amp;theme=&lt;LAF.Theme[url_ENCODE]&gt;&amp;sap-lafversions=&lt;LAF.AllVersions[url_ENCODE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;Report&gt;&amp;&lt;BusinessParameters&gt;&#39;; the problem occured at position 230. Cannot process expression &lt;LAF.AllVersions&gt;
    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:540)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:423)
    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)
    Content pass of Application Integrator failed.
    Component Name:       'com.sap.portal.appintegrator.sap.BWReport',
    Context Name (iView):  <iview name location>
    Top Layer:            'BWReport/TopLayer',
    Producer ID (FPN):    'null',
    System Alias:         'Sap_bw',
    2.
    The cluster server element 111111 is not added in the EP cluster context,
       because prtbridge on 111111 is stopped  or not yet started (maybe the server is starting or shuting down).
    Please suggest us if the above logs are related to the issue or not
    Kindly provide us any inputs or solutions.

    Hi All,
    We are also having similiar type of error in our portal. 
    com.sap.engine.services.prtbridge##com.sap.engine.services.prtbridge
    #######SAPEngine_System_Thread[impl:5]_13##0#0#Error#1#/System/Server#Plain###
    The cluster server element 125898350 is not added in the EP cluster context,
       because prtbridge on 125898350 is stopped  or not yet started
    (maybe the server is starting or shuting down).
    We have implemented the FPN using RRA.
    This error comes only for few users when they navigate in Portal. After clearing the cache, it works for all. Kindly help us to resolve this issue.
    Regards,
    Venkatesh

Maybe you are looking for

  • Re: How to restore data after HDD format?

    hi, folks I need your help to restore some important data that gone after hdd formatting. I didn't make any backup that was my mistake. Everyone's help is appreciated. Thanks to all.

  • Im running 10.6.7 but cant play call of duty 4

    It says to redownload from the mac app store and I did and it still doesnt work!Im running 10.6.7 Is There a sulotion?my mac book air runs call of duty a bit slow so i wanna play it here Hardware Overview:   Model Name:          iMac   Model Identifi

  • ERROR OGG-00685  begin time : extract process abending

    Hi Gurus, I have installed Oracle Golden Gate in the below environment.But unable to start extract process I am newer to OGG and its production setup. Primary site (source): This is production DB and up and running. RAC 2 nodes Oracle RAC 11.2.0.1.0

  • Restrict Output to PDF Only

    Hi All, I am using XML Publisher on Oracle eBS 11.5.10.2. The requirement that I have specifies that while running the concurrent program the user should only be able to select the output format as PDF. ie after supplying the parameters for the repor

  • The system administrator has set policies to prevent this installation

    when installing itunes on mums sony vaio with vista home edition. a message saying "the system administrator has set policies to prevent this installation" pops up not allowing the installation to continue. had a quick look on other forums and the ge