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

Similar Messages

  • 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 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 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 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 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 creating users in portal content administrator

    I am getting this error while creating new users in portal.
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.user_administration/com.sap.portal.user_admin_ws/com.sap.portal.user_management/com.sap.portal.createNewUser/com.sap.portal.createNewUser
    Component Name : com.sap.portal.usermanagement.admin.CreateNewUser
    com/sap/security/core/util/imp/Util.patternMatch(Ljava/lang/String;Ljava/lang/String;Z)Z.
    Exception id: 03:51_27/08/08_0028_7431850
    See the details for the exception ID in the log file
    any help is appreciated...

    log file look something like
    this
    2,5,PRT-Async]##0#0#Error#1#/System/Server#Java###Exception in PortalRequestManager.dispatchRequest without timeout
    [EXCEPTION]
    #1#java.lang.NoSuchMethodError: com/sap/security/core/util/imp/Util.patternMatch(Ljava/lang/String;Ljava/lang/String;Z)Z
         at com.sap.security.core.admin.util.checkEmail(util.java:110)
         at com.sap.security.core.admin.UserBean.checkFieldValidity(UserBean.java:695)
         at com.sap.security.core.admin.UserBean.checkUser(UserBean.java:591)
         at com.sap.security.core.admin.UserAdminLogic.performUserModify(UserAdminLogic.java:3226)
         at com.sap.security.core.admin.UserAdminLogic.executeRequest(UserAdminLogic.java:552)
         at com.sapportals.portal.prt.component.usermanagement.admin.UserAdminComponent.doContent(UserAdminComponent.java:71)
         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.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)
         at java.security.AccessController.doPrivileged(AccessController.java:241)
         at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)
         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:758)
    #1.5#001125A6576A008C00000015000550E2000455943BAE9D63#1219995051656#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#197794##irconepd_EPD_7431850#Administrator#f4d062d0759411ddb89b001125a6576a#Thread[PRT-Async 2,5,PRT-Async]##0#0#Error#1#/System/Server#Java###Exception ID:01:00_29/08/08_0043_7431850
    [EXCEPTION]
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.user_administration/com.sap.portal.user_admin_ws/com.sap.portal.user_management/com.sap.portal.userSearch/com.sap.portal.userSearch
    Component class : com.sapportals.portal.prt.component.usermanagement.admin.UserAdminComponent
    User : Administrator
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)
         at java.security.AccessController.doPrivileged(AccessController.java:241)
         at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)
         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:758)
    Caused by: java.lang.NoSuchMethodError: com/sap/security/core/util/imp/Util.patternMatch(Ljava/lang/String;Ljava/lang/String;Z)Z
         at com.sap.security.core.admin.util.checkEmail(util.java:110)
         at com.sap.security.core.admin.UserBean.checkFieldValidity(UserBean.java:695)
         at com.sap.security.core.admin.UserBean.checkUser(UserBean.java:591)
         at com.sap.security.core.admin.UserAdminLogic.performUserModify(UserAdminLogic.java:3226)
         at com.sap.security.core.admin.UserAdminLogic.executeRequest(UserAdminLogic.java:552)
         at com.sapportals.portal.prt.component.usermanagement.admin.UserAdminComponent.doContent(UserAdminComponent.java:71)
         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)
         ... 7 more

  • Portal Runtime error when modifying: com.sap.portal.runtime.logon.par

    Hello,
    We need some help because we get 'Portal Runtime error: iView: N/A Component Name:N/A' error when trying to access portal logon screen.
    This is what we've done:
    We've modified com.sap.portal.runtime.logon.par file and we've uploaded it but it doesn't work. Because of the error, we've overwritten this file with the original one but now it's imposible to access portal.
    The situation it seems to be like before the modification of the .par file but we get the same error and can't access portal.
    Please, do you know what could be the problem?
    Thanks in advance

    Hi Belen,
    Here are the steps you would need to take
    1. import the original par file into the NWDS and name the project as  
        com.sap.portal.runtime.logon
    2. Make sure the project name is com.sap.portal.runtime.logon
    3. use winzip/winrar to extract the com.sap.portal.runtime.logon.par file in
        a local directory
    4.Under the lib you would find two jar files copy them and paste them in your project
       under dist>PORTAL-INF>lib directory
    5.move the files cert....till umResetPass....jsp into the  PORTAL-INF directory
    6. export the par to the server in question
    7. restart your server
    This should solve your problem..
    Thanks,
    Gokul

  • Internet Procurement responsibility error after applying patch

    Hi Guru(s):
    After applying patch 5156915 we get this errro when we select i Procrurment responsibility:
    The POR SSP HOME function is not available under the Internet Procurement responsibility.
    iProcurement is installed.
    Any ideas would be most welcome thank you.
    EBS 11.5.10
    Edited by: Dan A on Dec 16, 2008 9:10 AM

    Thanks yet again to Hussein.
    I am a little worried that I couldnt find that same document.
    I entered in ML "The POR SSP HOME function is not available" ....and that document did not appear.
    Then I entered it with underscores : "The POR_SSP_HOME function is not available" ... and now I can see the doc.
    How did you do your search?! I am guessing you used udnerscores or else something different? ? ?
    Thanks, and still curious,
    DA
    By the way we are told to "clear" the _pages directory. I would do this with
    cat /dev/null > oa_html , etc ?
    Edited by: Dan A on Dec 16, 2008 9:44 AM

  • Error after apply Patch 41 in my EP 6.0 SP2

    Hi! 
    I am migrating my E.P 6.0 SP2 to E.P. 7.0.  
    As you know, the first phase of the process it is migrate source E.P at least to patch 28. I have installed the Patch 41. 
    After that, when I obtain the following error in the start log file ("2007_9_2_at_3_4_29_error.log"): 
    Loading services:
      Loading service: com.sap.km.application|default
      Loading service: com.sap.km.cm.command|default
      Loading service: com.sap.km.cm.main|default
      Loading service: com.sap.km.cm.protocols.ice|default
      Loading service: com.sap.km.cm.protocols.webdav|default
      Loading service: com.sap.km.cm.repository.filter|default
      Loading service: com.sap.km.cm.repository.manager|default
      Loading service: com.sap.km.cm.repository.service|default
      Loading service: com.sap.km.cm.repository.service.base|default
      Loading service: com.sap.km.cm.security|default
      Loading service: com.sap.km.cm.service|default
      Loading service: com.sap.km.cm.service.base|default
      Loading service: com.sap.km.cm.ui|default
      Loading service: com.sap.km.cm.ui.flex|default
      Loading service: com.sap.km.cm.xmlforms|default
      Loading service: com.sap.km.common.resourcebundle|default
      Loading service: com.sap.km.trex.client|default
      Loading service: com.sap.km.trex.ui|default
      Loading service: com.sap.netweaver.bc.crt|default
      Loading service: com.sap.netweaver.bc.protocol|default
      Loading service: com.sap.netweaver.bc.rf|default
      Loading service: com.sap.netweaver.bc.rf.manager|default
      Loading service: com.sap.netweaver.bc.rf.service|default
      Loading service: com.sap.netweaver.bc.sf|default
      Loading service: com.sap.netweaver.bc.sf.service|default
      Loading service: com.sap.netweaver.bc.util|default
      Loading service: com.sap.netweaver.bc.uwl|default
      Loading service: com.sap.netweaver.bc.uwl|UniversalWorklistDeploymentHook
      Loading service: com.sap.netweaver.bc.uwl.aibconnector|default
      Loading service: com.sap.netweaver.bc.wdf.demo|Bootstrap
      Loading service: com.sap.netweaver.bc.wdf.ext|PortalFactory
      Loading service: com.sap.netweaver.bc.wdf.ext|Bootstrap
      Loading service: com.sap.netweaver.coll.appl.async|default
      Loading service: com.sap.netweaver.coll.appl.base|status_engine
      Loading service: com.sap.netweaver.coll.appl.base|ExtensionService
      Loading service: com.sap.netweaver.coll.appl.gw|fwk
      Loading service: com.sap.netweaver.coll.appl.gw|mgr_calendar
      Loading service: com.sap.netweaver.coll.appl.gw|srvc_mail
      Loading service: com.sap.netweaver.coll.appl.room|RoomsService
      Loading service: com.sap.netweaver.coll.appl.room|Concat
      Loading service: com.sap.netweaver.coll.appl.room|ConfigReader
      Loading service: com.sap.netweaver.coll.appl.room|RoomPropertyReader
      Loading service: com.sap.netweaver.coll.appl.room|RoompartPropertyReader
      Loading service: com.sap.netweaver.coll.appl.room|RoomStatusExtension
      Loading service: com.sap.netweaver.coll.appl.room|RoomPartExtension
      Loading service: com.sap.netweaver.coll.appl.room|RoomPartListPropertyProvider
      Loading service: com.sap.netweaver.coll.appl.room|CmRoomExtensionSP2FP
      Loading service: com.sap.netweaver.coll.appl.room|CmDiscussionExtension
      Loading service: com.sap.netweaver.coll.appl.room|CmValueSetProvider
      Loading service: com.sap.netweaver.coll.appl.room|RoomsTestExtension
      Loading service: com.sap.netweaver.coll.appl.room|RoomsTestValueSetProvider
      Loading service: com.sap.netweaver.coll.appl.room|RSL_SERVICE
      Loading service: com.sap.netweaver.coll.appl.room|RSL_NAVIGATION
      Loading service: com.sap.netweaver.coll.appl.room|FilterService
      Loading service: com.sap.netweaver.coll.appl.room|public_area
      Loading service: com.sap.netweaver.coll.appl.room|rpso
      Loading service: com.sap.netweaver.coll.appl.room|RoomPartsService
      Loading service: com.sap.netweaver.coll.appl.room|template_mechanism
      Loading service: com.sap.netweaver.coll.appl.room|PCDTemplateMechanism
      Loading service: com.sap.netweaver.coll.appl.room|PCDTemplateData
      Loading service: com.sap.netweaver.coll.appl.room|CollApplReport
      Loading service: com.sap.netweaver.coll.appl.rtc|rtmf_messaging
      Loading service: com.sap.netweaver.coll.appl.rtc|rtmf_service
      Loading service: com.sap.netweaver.coll.appl.rtc|RTMFServerBridge
      Loading service: com.sap.netweaver.coll.appl.rtc|collaboration_connector_awareness
      Loading service: com.sap.netweaver.coll.appl.rtc|RTCScriptConstants
      Loading service: com.sap.netweaver.coll.appl.rtc|RTCHotDeploymentManagerService
      Loading service: com.sap.netweaver.coll.appl.rtc|RTCClientManagerService
      Loading service: com.sap.netweaver.coll.appl.rtc|RTCClientPollingService
      Loading service: com.sap.netweaver.coll.appl.rtc|RTCClientAwareness
    Sep 2, 2007 3:06:43 AM # System_Thread_12     Fatal           [PortalServiceItem.startServices] service initialisation failed:com.sap.netweaver.coll.appl.rtc|RTCClientAwareness
    com.sapportals.portal.prt.core.broker.PortalServiceInstantiationException: Could not instantiate implementation class com.sap.ip.collaboration.core.api.semantic.services.RTCClientAwareness of Portal Service com.sap.netweaver.coll.appl.rtc|RTCClientAwareness because: could not load the service
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:689)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1491)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1447)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1404)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:371)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: java.lang.IllegalThreadStateException
         at java.lang.Thread.start(Native Method)
         at com.sap.ip.collaboration.core.api.semantic.services.RTCClientAwareness$ClientAwarnessChecker.start(RTCClientAwareness.java:650)
         at com.sap.ip.collaboration.core.api.semantic.services.RTCClientAwareness.initService(RTCClientAwareness.java:176)
         at com.sap.ip.collaboration.core.api.semantic.services.RTCBaseService.init(RTCBaseService.java:127)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstance(PortalServiceItem.java:678)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:519)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:875)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1491)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1447)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1404)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:371)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:160)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:358)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:40)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:113)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:391)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:3340)
         at com.inqmy.services.servlets_jsp.server.ServletContextFacade.init(ServletContextFacade.java:2598)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.createContext(ServletsAndJspImpl.java:766)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.<init>(ServletsAndJspImpl.java:201)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspServerFrame.start(ServletsAndJspServerFrame.java:125)
         at com.inqmy.core.service.application.ApplicationServiceRunner.startFrame(ApplicationServiceRunner.java:55)
         at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java:129)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
      Loading service: com.sap.netweaver.coll.appl.rtc|RTCSessionManagerService
      Loading service: com.sap.netweaver.coll.appl.sync|scf
      Loading service: com.sap.netweaver.coll.appl.sync|sessiondata
      Loading service: com.sap.netweaver.coll.appl.sync|WebExConfig
      Loading service: com.sap.netweaver.coll.appl.sync|RTCConfig
      Loading service: com.sap.netweaver.coll.appl.sync|SCFConnectorSessionsMapService
      Loading service: com.sap.netweaver.coll.appl.ui.async|default
      Loading service: com.sap.netweaver.coll.appl.ui.async.meetingroom|meetingroom
      Loading service: com.sap.netweaver.coll.appl.ui.base|cs_rtc
      Loading service: com.sap.netweaver.coll.appl.ui.base|cs_scf
      Loading service: com.sap.netweaver.coll.appl.ui.base.pcwizard|PostCfgGenericService
      Loading service: com.sap.netweaver.coll.appl.ui.gw|gwuiservice
      Loading service: com.sap.netweaver.coll.appl.ui.room|roomuiservice
      Loading service: com.sap.netweaver.coll.appl.ui.sync|sessiondata
      Loading service: com.sap.netweaver.coll.pc.homer|homer
      Loading service: com.sap.netweaver.coll.shared|default2
      Loading service: com.sap.netweaver.coll.shared|collaboration_base
      Loading service: com.sap.netweaver.coll.shared.ui|people
      Loading service: com.sap.netweaver.kmc.attachment.shared|attachment
      Loading service: com.sap.netweaver.kmc.people|umeservice
      Loading service: com.sap.netweaver.kmc.people|trustedattributechecker
      Loading service: com.sap.netweaver.kmc.util|default
      Loading service: com.sap.netweaver.kmc.util|logginginitializer
      Loading service: com.sap.portal.admin.propertyeditor|property_editor
      Loading service: com.sap.portal.admin.propertyeditor|PEService
      Loading service: com.sap.portal.appdesigner.contentcatalog|contentcatalog
      Loading service: com.sap.portal.appdesigner.framework|menu
      Loading service: com.sap.portal.appintegrator|template_processor
      Loading service: com.sap.portal.appintegrator|application_integrator
      Loading service: com.sap.portal.appintegrator|psid
      Loading service: com.sap.portal.appintegrator|Common_Configuration
      Loading service: com.sap.portal.appintegrator.sap|Transaction_Configuration
      Loading service: com.sap.portal.appintegrator.sap.bwc|urlgenerator_bwc
      Loading service: com.sap.portal.appintegrator.sap.bwc|psid
      Loading service: com.sap.portal.compatibility50.cache|cache
      Loading service: com.sap.portal.compatibility50.systemlandscape|landscape
      Loading service: com.sap.portal.contentfetching|contentFetchingService
      Loading service: com.sap.portal.contentmigration.contentmigrationservice|contentmigration
      Loading service: com.sap.portal.contentmigration.contentmigrationservice|mapping
      Loading service: com.sap.portal.contentmigration.pagemigrationhandlerservice|default
      Loading service: com.sap.portal.contentmigration.parmigrationhandlerservice|parhandler
      Loading service: com.sap.portal.contentmigration.pcdmigrationhandlerservice|pcdhandler
      Loading service: com.sap.portal.contentmigration.pcdobjectservice|pcdobjects
      Loading service: com.sap.portal.desktop.desktopservice|desktopservice
      Loading service: com.sap.portal.dsm|dsmservice
      Loading service: com.sap.portal.epcf.loader|epcfloader
      Loading service: com.sap.portal.epcf.toolbox|epcftoolbox
      Loading service: com.sap.portal.heartbeats|ClusterTest
      Loading service: com.sap.portal.htmlb|htmlb
      Loading service: com.sap.portal.ivs.connectorservice|connector
      Loading service: com.sap.portal.ivs.global|producer
      Loading service: com.sap.portal.ivs.httpservice|http
      Loading service: com.sap.portal.ivs.httpservice|proxy
      Loading service: com.sap.portal.ivs.init|genericcreator
      Loading service: com.sap.portal.ivs.iviewservice|iviews_dt
      Loading service: com.sap.portal.ivs.iviewservice|iviews
      Loading service: com.sap.portal.ivs.iviewservice|SLUtilsSrv
      Loading service: com.sap.portal.ivs.iviewservice|SLObjectsManagerSrv
      Loading service: com.sap.portal.ivs.iviewservice|iViewsSrv
      Loading service: com.sap.portal.ivs.iviewservice|pagesSrv
      Loading service: com.sap.portal.ivs.iviewservice|layoutsSrv
      Loading service: com.sap.portal.ivs.iviewservice|templates_cache
      Loading service: com.sap.portal.ivs.iviewservice|PersonalizationSyncService
      Loading service: com.sap.portal.ivs.personalizationsync|ContentMarshallerService
      Loading service: com.sap.portal.ivs.systemlandscapeservice|systemlandscape
      Loading service: com.sap.portal.ivs.systemlandscapeservice|producerSrv
      Loading service: com.sap.portal.ivs.systemlandscapeservice|oldPcmMockup
      Loading service: com.sap.portal.navigation.helperservice|navigation_events_helper
      Loading service: com.sap.portal.navigation.service|navigation
      Loading service: com.sap.portal.objectlocator.objectlocatorservice|ObjectLocatorService
      Loading service: com.sap.portal.pagebuilder|pageUtilHook
      Loading service: com.sap.portal.pcd.admintoolsservice|admintools
      Loading service: com.sap.portal.pcd.pcm.roles.rolecontainer|rolecontainerservice
      Loading service: com.sap.portal.pcd.plainfolderservice|plainfolders
      Loading service: com.sap.portal.pcd.rolenavigationservice|rolenavigation
      Loading service: com.sap.portal.pcd.roleservice|roles
      Loading service: com.sap.portal.pcd.samplesemanticservice|sample
      Loading service: com.sap.portal.pcd.transportapplication|transportapplication
      Loading service: com.sap.portal.pcm.admin.plainfolder_converter|default
      Loading service: com.sap.portal.processlogger.processloggerservice|processlogger
      Loading service: com.sap.portal.productivity.desktop|DesktopManager
      Loading service: com.sap.portal.productivity.desktop|RuntimeDesktopManager
      Loading service: com.sap.portal.productivity.dom|dom
      Loading service: com.sap.portal.productivity.resolverservice|ruleManager
      Loading service: com.sap.portal.productivity.resolverservice|resolver
      Loading service: com.sap.portal.productivity.util.dyntree|DynamicTreeService
      Loading service: com.sap.portal.productivity.utils|sap_utilities
      Loading service: com.sap.portal.prt.cache|dbcacheservice
      Loading service: com.sap.portal.runtime.admin.logadmin|adminlogger
      Loading service: com.sap.portal.runtime.application.contentconversion|contentconversion
      Loading service: com.sap.portal.runtime.application.contentconverter|contentconverter
      Loading service: com.sap.portal.runtime.application.document|document
      Loading service: com.sap.portal.runtime.application.document|documentnew
      Loading service: com.sap.portal.runtime.application.monitor|Monitoring
      Loading service: com.sap.portal.runtime.application.monitor|SATController
      Loading service: com.sap.portal.runtime.application.monitor|MonitorAdministration
      Loading service: com.sap.portal.runtime.application.monitor|PortalMonitor
      Loading service: com.sap.portal.runtime.application.monitor|StateMonitor
      Loading service: com.sap.portal.runtime.application.soap|soap
      Loading service: com.sap.portal.runtime.system.console|portalanywhere
      Loading service: com.sap.portal.runtime.system.hooks|modehook
      Loading service: com.sap.portal.runtime.system.prtconnection|default
      Loading service: com.sap.portal.runtime.system.prtconnection|prtrwconnection
      Loading service: com.sap.portal.strucfilterservice|structure_filter
      Loading service: com.sap.portal.supportability.reporting|Reporter
      Loading service: com.sap.portal.themes.designservice|design
      Loading service: com.sap.portal.themes.integrity|ServerTestService
      Loading service: com.sap.portal.ui.uiservice|ui
      Loading service: com.sap.portal.um_webservice|um_web
      Loading service: com.sap.portal.unification.dragandrelate|DragAndRelateService
      Loading service: com.sap.portal.unification.dragandrelate|DragAndRelateComponentHook
      Loading service: com.sap.portal.unification.parsers|default_hrnp_link_parser
      Loading service: com.sap.portal.unification.parsers|default_sap_link_parser
      Loading service: com.sap.portal.unification.parsers|link_parser_strategy
      Loading service: com.sap.portal.unification.uslservice|uslservice
      Loading service: com.sap.portal.unification.utils|utils
      Loading service: com.sap.portal.unification.utils|HRNPNodeFactoryService
      Loading service: com.sap.portal.unification.utils|HRNPParser
      Loading service: com.sap.portal.unification50.sync|component_sync
      Loading service: com.sap.portal.upgrader.channels|ChannelsUpgraderService
      Loading service: com.sap.portal.upgrader.iviews|IViewsUpgraderService
      Loading service: com.sap.portal.upgrader.landscapeupgrader|landscapeupgrader
      Loading service: com.sap.portal.upgrader.pages|PagesUpgraderService
      Loading service: com.sap.portal.upgrader.parupgraderservice|ParUpgraderService
      Loading service: com.sap.portal.upgrader.pcdaccess|PcdAccessService
      Loading service: com.sap.portal.upgrader.pcdpersupgrader|PcdPersUpgraderService
      Loading service: com.sap.portal.upgrader.pcdupgrader|PcdUpgraderService
      Loading service: com.sap.portal.upgrader.personalization.iviews|PersonalizedIViewsUpgraderService
      Loading service: com.sap.portal.upgrader.rolestochannels|RolesToChannelsUpgraderService
      Loading service: com.sap.portal.upgrader.style|service
      Loading service: com.sap.portal.upgrader.um|default
      Loading service: com.sap.portal.upgrader.upgraderservice|UpgraderService
      Loading service: com.sap.portal.useragent|useragent
      Loading service: com.sap.portal.util.threadreporting|reportingservice
      Loading service: com.sap.portal.yahoo|yahoo
      Loading service: com.sap.workflow.apps|WFPortalService
      Loading service: com.sap.workflow.service|KMNotification
      Loading service: com.sap.workflow.service|WFAttachmentService
      Loading service: com.sap.workflow.service.uwl|WFEWorkitemProvider
    Portal initialization done.
    How can I solve the error? 
    Thanks a lot in advance.

    Hi Ramon,
    There is some problem with the RealTimeCollaboration, which should not harm the system integrity at all, so that from that point of view there should be no problem going on with the migration.
    Anyhow, you can still try to fix this on SP2 P41 level, maybe the hint given in /message/3603152#3603152 [original link is broken] also works for you.
    Hope it helps
    Detlev
    PS: Please consider rewarding points for helpful answers on SDN. Thanks in advance!

  • Dump error after applying patches

    Dear all;
    after applying SAP_BASIS Packs (SAPKB62019 and SAPKB62020) the transaction was canceled before finched implementing the patches and We are receiving ABAP dump errors while executing any transaction ( syntax_error)
    could you help me to resolve this proble?
    thanks and regards.
    Issam CHIBOUNI

    Hi
    SAPKB62020
               Symptom: After you import Basis Support Package SAPKB62020, you may experience a change in the system response at different points in an R/3 Enterprise system. This problem can be seen in the sudden appearance of screen elements, for example, or in changes in the process flow of transactions. In extreme cases, it can also cause data corruption.
               Reason: Support Package SAPKB62020 included an incomplete correction to BAdI processing that caused the execution of BAdI implementation of deactivated Enterprise Extensions.
               Solution: You must refer to SAP Note 601742. Import Basis Support Package SAPKB62023 as soon as possible (planned release date is May 06, 2003) or implement the additional correction instructions as described in Note 601742.
    thanks and regard
    Khurshid

  • Error after applying patch set 10.1.3.4.0

    Hi everyone,
    I downloaded the patch set 10.1.3.4.0 from [http://www.oracle.com/technology/software/products/ias/htdocs/101310.html] and intalled it on my machine but after the installation finished, I found problem in runing Oracle Process Manaer Console. When I try to login, it redirects to DomainPickup.jsp and after entering oc4jadmin id and password below message appears: No domains accessible to the user logged in.
    When I click on Goto BPEL Admin and try to create a new domain, it does not accept "default" as domain id: it says "Domain already exists." when I give different name, it shows this error:
    Exception
    Operation failed because:
    Domain creation error.
    An exception occurred while attempting to create the domain "sample" at path "c:\oracle10gR1\product\10.1.3.1\OracleAS_1\bpel\domains\sample". The exception reported is:
    I was using SOA suite 10.1.3.0 and it was working properly before upgrade.
    I will appeciate if someone can help me to fix this problem. I could not found any note for applying this patch on download page too.
    Thanks
    Esfand

    Hi Adina,
    I tried to perform all the steps explained there but I might have missed some parts which I'm not getting it down. I could figure out the cause of problem after I searched the oracle forums for several times. It seems that this error is because of data-source settings and database server. The bpel engine can not connect to database anymore. This means that during the pachset the database settings has been altered somehow but when I check the XML files, I can't find any mistake there.
    I have not worked with Oracle Lit database and do not know how to manage the database it creates therefore, I decided to install the Oracle 10g Database XE, when I go through advanced installation of SOA suite 10.3.0.1 after running IRCA, the installation is finished successfully but the same problem exists. When I checked the Connection pool in Oracle AS, it shows error from NLS data and now I'm in infinite loop how to fix this problem. After many installation / deinstallation I could not fix it so I decided to install the SOA Suite in typical mode and then connect the BPEL to oracle Database later. After the installation, I changed 3 data sources defined in Oracle AS along with its connection pool to connect to my Oracle 10g XE database having BPEL schema but it still raises some more exception and now, I have no idea what to do?!!!!
    It's about 10 days that I'm struggling to get this installation done but I have not succeeded yet. I believe It should not be so hard and complex to have Oracle Suite 11g TP4 configured as it appears to happen for me. Oracle products all have straightforward installation process but this once is killing me.!!
    I will appreciate any further help for windows installation.
    Regards
    Esfand
    Edited by: user3788199 on Sep 4, 2008 3:59 AM
    Edited by: user3788199 on Sep 4, 2008 4:02 AM

  • ERROR after applying patch CSCtj01051: solaris9 CS 3.3 - LMS 3.2

    I installed a couple of LMS 3.2 point patches on a solaris 9 box. Afterwards the LMS did not started any more. DCRServer hang in "Waiting to initialize" and Apache failed to run. Also a couple of other processes failed (attached pdshow).
    Troublshooting this I found a line in dmgtd.log which says web_server misses libm.so.2;
    I have installed cwcs33-sol-CSCtj01051.tar which updates Apache to 2.2.16 (and already had the patch for CSCtg46847 installed - which is a prerequisite).
    As I could not find  libm.so.2 in /usr/lib I did ldd on web_server, which gave me:
    bash-2.05# ldd /opt/CSCOpx/MDC/Apache/bin/web_server
            libm.so.2 =>     (file not found)
            libaprutil-1.so.0 =>     (file not found)
            libexpat.so.0 =>         (file not found)
            libiconv.so.2 =>         (file not found)
            libapr-1.so.0 =>         (file not found)
            libuuid.so.1 =>  /usr/lib/libuuid.so.1
            libsendfile.so.1 =>      /usr/lib/libsendfile.so.1
            librt.so.1 =>    /usr/lib/librt.so.1
            libsocket.so.1 =>        /usr/lib/libsocket.so.1
            libnsl.so.1 =>   /usr/lib/libnsl.so.1
            libpthread.so.1 =>       /usr/lib/libpthread.so.1
            libc.so.1 =>     /usr/lib/libc.so.1
            libdl.so.1 =>    /usr/lib/libdl.so.1
            libaio.so.1 =>   /usr/lib/libaio.so.1
            libmd5.so.1 =>   /usr/lib/libmd5.so.1
            libmp.so.2 =>    /usr/lib/libmp.so.2
            libthread.so.1 =>        /usr/lib/libthread.so.1
            /usr/platform/SUNW,Sun-Fire-V440/lib/libc_psr.so.1
            /usr/platform/SUNW,Sun-Fire-V440/lib/libmd5_psr.so.1
    bash-2.05#
    Content of /opt/CSCOpx/MDC/Apache/lib/ is:
    bash-2.05# ls -al /opt/CSCOpx/MDC/Apache/lib/
    total 2384
    drwxr-x---   2 casuser  casusers     512 May  6  2010 .
    drwxrwxr-x   8 casuser  casusers     512 Feb 16 18:22 ..
    lrwxrwxrwx   1 casuser  casusers      44 May  6  2010 libapr-1.so -> /opt/CSCOpx/MDC/Apache/lib/libapr-1.so.0.3.3
    lrwxrwxrwx   1 casuser  casusers      44 May  6  2010 libapr-1.so.0 -> /opt/CSCOpx/MDC/Apache/lib/libapr-1.so.0.3.3
    -rwxr-x---   1 casuser  casusers  541816 Nov  3  2008 libapr-1.so.0.3.3
    lrwxrwxrwx   1 casuser  casusers      48 May  6  2010 libaprutil-1.so -> /opt/CSCOpx/MDC/Apache/lib/libaprutil-1.so.0.3.4
    lrwxrwxrwx   1 casuser  casusers      48 May  6  2010 libaprutil-1.so.0 -> /opt/CSCOpx/MDC/Apache/lib/libaprutil-1.so.0.3.4
    -rwxr-x---   1 casuser  casusers  368476 Nov  3  2008 libaprutil-1.so.0.3.4
    lrwxrwxrwx   1 casuser  casusers      44 May  6  2010 libexpat.so -> /opt/CSCOpx/MDC/Apache/lib/libexpat.so.0.1.0
    lrwxrwxrwx   1 casuser  casusers      44 May  6  2010 libexpat.so.0 -> /opt/CSCOpx/MDC/Apache/lib/libexpat.so.0.1.0
    -rwxr-x---   1 casuser  casusers  267276 Nov  3  2008 libexpat.so.0.1.0
    bash-2.05#
    so beside libm.so.2 everything seems to be in place - but it seems not to be recognized by /opt/CSCOpx/MDC/Apache/bin/web_server
    Also libm.so.2 seems to be for solaris 10 (according to some threads on the web) and thus I ask myself if cwcs33-sol-CSCtj01051.tar is really intended for solaris 9...
    And also, I ask myself how I can get LMS running again ...

    thank you Joe for filing the Bug.
    When I observed the issue I was quite at a loss and it took me a while to find the reason.
    I created a softlink on libm.so.2 but this didn' t solved the issue. ldd /opt/CSCOpx/MDC/Apache/bin/web-server showed that this library was now found but some other still not.
    The reason was a bit strange and I am not sure if my troubleshooting steps caused it (e.g. re-applying the patch) or if I was just unconcentrated as "it was late in the evening ...."
    Finally I found that the other library files which comes with LMS (libaprutil-1.so.0, libexpat.so.0, libiconv.so.2, libapr-1.so.0) and are stored in NMSROOT/MDC/Apache/lib have had a byte size of 0;
    Happily, I had still another server running and could copy those files to the local server, restarted dmgtd and got it back running
    So I am not sure if the patch just introduces libm.so.2 or if it also has some impact on somee other libraries in  NMSROOT/MDC/Apache/lib.
    I will update the other server in the next 2 or 3 weeks, then I can tell....

  • 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

Maybe you are looking for

  • I click on a website, it loads, and then immediately goes to a blank page

    This problem just started about 2 weeks ago. I will click on a site, and for a second i am there, then the page goes blank. sometimes I get the word "Done" in the lower left-hand corner of the page. This appears to be random w/pages. Some, never have

  • Connecting my playstation 3 to my Macbook Pro

    Is it possible? I'd love to take advantage of the 15" screen I have here and just play my ps3 through the mac. Any tips would be great.

  • BPM Process with offline adobe forms - NW CE 7.2 SP3

    Hi experts, I have to develop the following scenario and I still don´t know the correct way that I should follow, I have already created the Process Development DC, the XSD and the XDP files, I have also put the XSD and XDP files into portal drive. S

  • Game animation...

    I'm kinda new to java, but not new to programming... I want to get a particular character to walk or do anything, meaning i want to use several images for a characters actions, im thinking of gif files, as they are the closest to small image files. A

  • DropdownByKey UI element is giving Classcast exception

    Hi In my webdynpro view if i add "DropdownbyKey" UI element and the run the application,it is giving Classcast Exception.i am getting following error The initial exception that caused the request to fail, was:    java.lang.ClassCastException     at c