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

Similar Messages

  • 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

    Hi Vaishnavi,
    Somewhere in your deploy package or in some referenced one, obviously you have a reference to ...enums...  Might be a problem with updating JARs during build or whatever, in any case, just search for it. Use WinRAR for example, with that you also can search within class files.
    The root cause is obvious, so just search and shoot it
    Hope it helps
    Detlev

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

  • 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

  • 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

  • KM iviews, KM Content, Index Administration showed Portal Runtime error

    Hi Experts,
    We recently tried migrating our BI production portal to new hardware. The Portal version was not changed just it was migrated from one server to another. After migration the portal restarted properly but the KM iviews, KM Content and Index Administration showed "Portal Runtime Error".
    We restarted the portal several times but still the same. Also the KM services were running.
    We had migrated the BI development portal in similar manner couple of months back but it did not showed any such error. It was successful in first attempt.
    Can anyone please suggest what must have gone wrong and how can this be corrected? Is there any monitoring or tracing tool we can use to check this. Please suggest.
    Thanks & Regards,
    Seema Rane.

    Hi Ricardo , Lorcan,
    Thank you for the prompt reply. Following is the default trace I found on the server:
    Caused by: com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception while starting: sap.com/com.sap.netweaver.coll.appl.room', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception while starting: sap.com/com.sap.netweaver.coll.appl.room
         at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.prepareStart(PortalRuntimeContainer.java:527)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4367)
         at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:589)
         ... 46 more
    Caused by: com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception while starting: SAPJ2EE::sap.com/xappscprxrpmui~collroomint', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception while starting: SAPJ2EE::sap.com/xappscprxrpmui~collroomint
         at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getAndStartSAPJ2EEApplicationItem(SAPJ2EEPortalRuntime.java:888)
         at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.prepareStart(PortalRuntimeContainer.java:511)
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [ExternalApplicationItem.prepare]: SAPJ2EE::sap.com/xappscprxrpmui~collroomint
         at com.sapportals.portal.prt.core.broker.ExternalApplicationItem.prepare(ExternalApplicationItem.java:188)
         at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:232)
         at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.start(SAPJ2EEApplicationItem.java:192)
         at com.sapportals.portal.prt.service.sapj2ee.Mediator.getAndStartExternalApplication(Mediator.java:132)
         at com.sap.portal.prt.sapj2ee.StartPortalApplication.coreRun(StartPortalApplication.java:59)
         at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getAndStartSAPJ2EEApplicationItem(SAPJ2EEPortalRuntime.java:884)
         ... 49 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.netweaver.coll.appl.room
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
         at com.sapportals.portal.prt.core.broker.ExternalApplicationItem.prepare(ExternalApplicationItem.java:180)
         ... 54 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.netweaver.coll.appl.base
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
         ... 55 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.netweaver.kmc.people
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
         ... 56 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.application
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
         ... 57 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.cm.main
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
         ... 58 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.cm.repository.filter
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
         ... 59 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.cm.service.base
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
         ... 60 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.cm.protocols.ice
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
         ... 61 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.cm.protocols.webdav
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
         ... 62 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.netweaver.bc.rf.service
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
         ... 63 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during start of application: SAPJ2EE::library:signature_lib
         at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:323)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
         ... 64 more
    Caused by: com.sapportals.portal.prt.core.broker.SAPJ2EELibraryNotFoundException: Could not find Library SAPJ2EE::library:signature_lib
         at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:277)
    I guess the KM applications are not being found. How do I correct this? Our KM repository is connected to BI and has got lot of BI content in it.
    Will redeploying the com.sap.km.applications.par file help?
    Please provide some solution so that this error will be resolved without effecting the KM Content.
    Thanks & Regards,
    Seema Rane

  • Portal runtime error while selecting page layout in WPC editor

    Hello,
    in web page composer, editing page, when i click on "select page layout" I have a portal runtime error popup.
    The logfile shows the following :
    #1.5 #005056834112005E0000000C00000FA800048E28A94966CC#1282205196819#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#1016#149##n/a##7ff9c93eab6811dfa9c70000003307de#SAPEngine_Application_Thread[impl:3]_15##0#0#Error##Java###10:06_19/08/10_0010_3344350
    [EXCEPTION]
    #1#com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error in java compiling
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: E:
    usr
    sap
    EPD
    JC00
    j2ee
    cluster
    server0
    apps
    sap.com
    irj
    servlet_jsp
    irj
    root
    WEB-INF
    portal
    portalapps
    com.sap.netweaver.bc.util
    lib
    bc.util.public_api.jar(com/sapportals/wcm/WcmException.java):24: class WcmException is public, should be declared in a file named WcmException.java
    (source unavailable)
    1 error
    I have the same by clicking on "check assignments"
    Any help ?
    Thanks

    Hello Jego.
    We faced the same issue after upgrade to EHP1 SP07 last week and managed to solve it by modification of layout.jsp and com.sap.nw.wpc.layoutmanager.LayoutBean within com.sap.nw.wpc.designtime.par. SAP's code requires an additional catch handler, so it is better to rise an OSS message.
    As a workaround you may change a default layout for wpc main page (good for new pages) or manually edit output.xml for existing pages.
    Best regards,
    Aliaksandr Zhukau

  • 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

  • Portal Runtime Error : An exception occurred while processing a request

    Hello friends,
    After upgradation of my portal to the following patch level, SAP J2EE 6.20:
    <b>Portal Version :</b> EP 6 SP 2 patch 29 hotfix 0
    <b>Content Mgmt and Collaboration  version</b> : 6 SP2 patch 5
    i faced many performance related issues. Portal seems to be <b>very slow</b>. After logging in, most of the time I get 2 errors:
    <b>Either</b>
    <b>1></b> Iview remains blank.
    <b>Or
    2></b> Portal Runtime Error : An exception occurred while processing a request. Portal Runtime exception occured. Please check the System Log.
    But when I refresh that particular iview, it works fine.
    I went through the portal.log file (/usr/sap/PEP6/j2ee/j2ee_00/cluster/server/managers/log/portal/logs). And found <b>the root cause of most of the exceptions as "com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found."</b>Aug 18, 2005 6:07:42 PM # PRT-Async 2          Fatal           Exception ID:06:07_18/08/05_0669
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/ACCContent/ACCContent.Roles/Company/R.Employee/W.MyWork/P.MyWork.DesktopTools/I.Contacts
    Component class : com.sapportals.portal.prt.pom.RootComponentNode
    User : tempuser
            at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:853)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:311)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
            at java.lang.Thread.run(Thread.java:479)
    Caused by: com.sapportals.portal.prt.component.PortalComponentException: PortalComponentException
            at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:153)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
            at java.lang.Thread.run(Thread.java:479)
    Caused by: com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found.
            at com.inqmy.services.servlets_jsp.server.ServletContextFacade.loadServletLocal(ServletContextFacade.java:3660)
            at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:81)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:275)
            at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.include(RequestDispatcherImpl.java:384)
            at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:144)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
            at java.lang.Thread.run(Thread.java:479)
    <b>Help needed.(</b>as i am helpless now.)
    Regards,
    Nilz

    Anthony,
      I had check it. It was correct. But the thing when I saw in the component Inspector of portal, my iview did not appear.
    I created like this
             project-> rightclick->   export-> par ->selecting project-> givint protal password-> and finish.
    The NW didn't give any error, but the par file didn't appear in the portal componet Inspect.
    but the par file is  created in the NW studio Navigation bar.
      Let me know any help regarding this
    thanks
    venkat

  • PPM Portal : Runtime error in KM Navigation Iview

    Hi All,
    We have a PPM(xRPM) 4.5 portal which we recently upgraded to SPS8.
    After upgrading the SAP delivered iview "Attachment and Links" is giving below dump::
    Runtime Error
    An exception occured while processing the request.
    Additional information: com.sap.pct.cprxrpm.XRPMRepositoryFilter$1
    Exception ID = 001dbd54-026e-2e10-7c88-c3c88b7162e7      Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 03:22_31/05/11_0036_501295550
    Refer to the log file for details about this exception.
    The ivew is of type KM Navigation and is mapped to the folder '/documents'
    The exception log is below:
    at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:33)
            at com.sapportals.htmlb.Container.preRender(Container.java:120)
            at com.sapportals.htmlb.Container.preRender(Container.java:120)
            at com.sapportals.htmlb.Container.preRender(Container.java:120)
            at com.sapportals.portal.htmlb.PrtContext.render(PrtContext.java:407)
            at com.sapportals.htmlb.page.DynPage.doOutput(DynPage.java:238)
            at com.sapportals.wcm.portal.component.base.KMControllerDynPage.doOutput(KMControllerDynPage.java:134)
            at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:133)
            at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
            at com.sapportals.wcm.portal.component.base.ControllerComponent.doContent(ControllerComponent.java:80)
            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:235)
            at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)
            at java.security.AccessController.doPrivileged(AccessController.java:246)
            at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
            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
    Please suggeest the possible root cause and soluiton.
    Edited by: Sumit Oberoi on Jun 1, 2011 12:36 AM
    Regards,
    Sumit
    Edited by: Sumit Oberoi on Jun 1, 2011 12:37 AM

    Portal Restart resolved the issue.

Maybe you are looking for

  • Expanding the size of a column in an interactive report?

    Hello, I am wondering if the size of a column in a report can be increased, without reducing the amount of columns displayed in the report? Thank you.

  • Currency in document draft

    Hi, I creating a marketing document and choose the currency to BP Currency. And then i save document as draft. when i open the document draft, the currency is change to local currency. can anyone explain to me why it is happen? i am using SBO version

  • My applications are not responding

    It started with Word, now Pages and iTunes are doing the same thing. I can open the apps but as soon as I start working in them I get the spinning wheel and have to force quit, quite maddening. Help.

  • How can we get debug info without adding IP in CFServer?

    Do we have tag or some code which will give debug information?. <cfdump var="#http#"> on onrequestend.cfm will give me http varible information....any other way?.

  • J1IEX - Screen

    Dear All, In J1IEX screen, my client want SCESS field of Credit Available part as editable field in the Detail Data section (below of Item section). Right now SCESS field is in display mode, then all other fields like BED, AED, NCCD, SED and ECS fiel