Validation error 'Item not found' in Middleware

Hi,
In the middleware monitor, I have some bdocs failed with the validation error ' Item was not found. Validation error occured. module CRM_DOWNLOAD_BEA_VAL, BDoc Type BEABILLDOCCRMB'.
When i look at the document numbers associated , they do exist.
It is in this state for a long time.
Can anyone help.
Regards,
Pratima

Hi Venkat,
There are no messages in the outbound or inbound queue releated to these bdocs.
These bdocs exist only in the monitor with validation error.
Regards,
Pratima

Similar Messages

  • BAPI_SALESORDER_CHANGE: Error-Item not found

    Hi,
    I am calling BAPI_SLESORDER_CHANGE from an enhancement in the include MV45AF0B_BELEG_SICHERN. This will be called after the commit work of sales order. Im using this BAPI for the purpose of changing/updating the Inquiry line item from which the SO is created.
    When I execute the BAPI in SE37 by passing the Inquiry no. & item to be updated, it is not giving any error. In my enhancement, I am passing the same values but getting the error: ITEM NOT FOUND.
    When I debugged the BAPI, the error is raised in the Fm SD_SALES_ITEM_READ.
    In the below code in FM, VBAP is getting filled inside the PERFORM VBAP_BEARBEITEN_VORBEREITEN but when it comes out of this subroutine, the VBAP is initial.
    But when executing with SE37, this VBAP value is not getting cleared after the subroutine.
      PERFORM XVBAP_LESEN_DIREKT_SVBAP(SAPFV45P) USING ITEM_NUMBER.
      PERFORM VBAP_BEARBEITEN_VORBEREITEN(SAPFV45P).
      EVBAP = VBAP.
    Please help me out to resolve this issue.

    Yes,
    but in sales order creation you are going thru a different code:
    * Anlegen <= Here from sales order creation
      IF SVBAP-TABIX = 0.
        CLEAR:  MAEPV,
                MAAPV,
                MTCOM,
                XVBUP,
                XVBAPF,
                KONDD,
                XVBAP.
         *VBAP = XVBAP.                    " Getuntes clear
        HVBAP = XVBAP.                     " Getuntes clear
         *HVBAP = XVBAP.                   " Getuntes clear
        VBAP = XVBAP.                      " Getuntes clear
         *MTCOM = MTCOM.                   " Getuntes clear
        MOVE-CORRESPONDING XVBAP TO VBAPD. " Getuntes clear
         *VBAPD = VBAPD.                   " Getuntes clear
        CLEAR: HVBKD, *HVBKD.
    * Steuerflag für Textverarbeitung initialisieren
        CLEAR NO_TEXT_COPY-ITEM.
        clear no_text_copy-check.
      ELSE.
    * Ändern <= Here from SE37
        VBAP = XVBAP.
    It's a completely different behaviour!
    Regards,
    Klaus

  • Error: "Item Not Found"  in SR1 KMSP9 installation

    Hi all,
         We have installed SR1 KM SP9.But, we are getting the following error in <i>Content Administration > KM Content</i>::
    <b>Item not found
    The item you are attempting to access is not available. Check that the name or link is correct. You might also check whether the associated repository is currently accessible. </b>
    We get the following error in the News iView (in <i>Home > Company</i>)::
    <b>Item not found
    /documents/News
    The item you are attempting to access is not available. Check that the name or link is correct. You might also check whether the associated repository is currently accessible. </b>
    I have seen the thread <b>EP60 SR1 + KM problems - Content management not working> and i have searched the note <b>813144</b>.
    The note says that::
    The page and iviews have been moved to the following place accordingly:
    portal_content/com.sap.pct/every_user/general/pages/com.sap.km.pages/ com.sap.netweaver.bc.uwl.uwl_page
    portal_content/com.sap.pct/every_user/general/iViews/ com.sap.netweaver.bc.uwl.iviews/com.sap.netweaver.bc.uwl.uwl_iview
    portal_content/com.sap.pct/every_user/general/iViews/com.sap.km.iviews/ com.sap.km.NewsBrowser
    portal_content/com.sap.pct/every_user/general/iViews/com.sap.km.iviews/ com.sap.km.Favorites
    portal_content/com.sap.pct/every_user/general/iViews/com.sap.km.iviews/ com.sap.km.LinkList
    Please modify the link to the shared page and iviews.
    I have checked the pcd Location of News iView. it is "pcd:portal_content/com.sap.pct/every_user/general/iViews/com.sap.km.iviews/com.sap.km.NewsBrowser" only. How come the News iView has the error mentioned above then??
    All other pages and iViews mentioned above have the respective pcd Locations.
    Can anyone please help me???
    Waiting for your reply.
    <b>
    Regards,
    Ranjith.</b>

    Hi Dimitry,
    Thanks for the reply.
    I checked the log file you had mentioned. It shows that the following services are being loaded :
    <b>com.sap.km.application
    com.sap.km.cm.command
    com.sap.km.cm.main
    com.sap.km.cm.protocols.ice
    com.sap.km.cm.protocols.webdav
    com.sap.km.cm.repository.filter
    com.sap.km.cm.repository.manager
    com.sap.km.cm.repository.service
    com.sap.km.cm.repository.service.base
    com.sap.km.cm.repository.security
    com.sap.km.cm.repository.service
    com.sap.km.cm.repository.service.base
    com.sap.km.cm.repository.ui
    com.sap.km.cm.repository.ui.flex
    com.sap.km.xmlfoms
    com.sap.km.common.resourcebundle
    com.sap.km.trex.ui</b>
    I think the required services are loaded, right. So what could be the problem?
    The following is the log::
    #1.5#000F1FB3D5CE0041000001AD00000C7C0003FCDC5D2E355F#1122448316447#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading services:#
    #1.5#000F1FB3D5CE0041000001AE00000C7C0003FCDC5D2E361B#1122448316447#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.ip.bi.broadcasting|broadcasting#
    #1.5#000F1FB3D5CE0041000001AF00000C7C0003FCDC5D3ED01D#1122448317538#/System/Server#sap.com/irj#com.sap.ip.bi.webapplications#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.ip.bi.webapplications#Plain###Service com.sap.ip.bi.portallogger.loggerservice has been initialized successfully#
    #1.5#000F1FB3D5CE0041000001B100000C7C0003FCDC5D4443F0#1122448317899#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.ip.bi.broadcasting|broadcasting_users#
    #1.5#000F1FB3D5CE0041000001B200000C7C0003FCDC5D45295F#1122448317949#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.ip.bi.broadcasting|online_link#
    #1.5#000F1FB3D5CE0041000001B300000C7C0003FCDC5D45E2B0#1122448317999#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.ip.bi.portallogger|loggerservice#
    #1.5#000F1FB3D5CE0041000001B400000C7C0003FCDC5D45E379#1122448317999#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.ip.bi.portalnavigation|binavigationservice#
    #1.5#000F1FB3D5CE0041000001B500000C7C0003FCDC5D4EED1B#1122448318590#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.ip.bi.portalnavigation|binavigationrfcservice#
    #1.5#000F1FB3D5CE0041000001B600000C7C0003FCDC5D4F26D4#1122448318610#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.ip.bi.portalrfctest|biportalrfctest#
    #1.5#000F1FB3D5CE0041000001B700000C7C0003FCDC5D58D772#1122448319241#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.ip.bi.portalrfctest|filebrowserrfcservice#
    #1.5#000F1FB3D5CE0041000001B800000C7C0003FCDC5D591CEB#1122448319261#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.ip.bi.repositorymanager|default#
    #1.5#000F1FB3D5CE0041000001BA00000C7C0003FCDC5D5E3CA4#1122448319601#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.application|default#
    #1.5#000F1FB3D5CE0041000001BC00000C7C0003FCDC5DCADBF9#1122448326712#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.cm.command|default#
    #1.5#000F1FB3D5CE0041000001BE00000C7C0003FCDC5DCC4586#1122448326812#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.cm.main|default#
    #1.5#000F1FB3D5CE0041000001C000000C7C0003FCDC5DCE5833#1122448326942#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.cm.protocols.ice|default#
    #1.5#000F1FB3D5CE0041000001C200000C7C0003FCDC5DCF5AF2#1122448327012#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.cm.protocols.webdav|default#
    #1.5#000F1FB3D5CE0041000001C400000C7C0003FCDC5DCFC6F1#1122448327042#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.cm.repository.filter|default#
    #1.5#000F1FB3D5CE0041000001C600000C7C0003FCDC5DD1E661#1122448327172#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.cm.repository.manager|default#
    #1.5#000F1FB3D5CE0041000001C800000C7C0003FCDC5DD2EE60#1122448327242#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.cm.repository.service|default#
    #1.5#000F1FB3D5CE0041000001CA00000C7C0003FCDC5DD3EEDB#1122448327312#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.cm.repository.service.base|default#
    #1.5#000F1FB3D5CE0041000001CC00000C7C0003FCDC5DD51D96#1122448327382#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.cm.security|default#
    #1.5#000F1FB3D5CE0041000001CE00000C7C0003FCDC5DD5C24E#1122448327433#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.cm.service|default#
    #1.5#000F1FB3D5CE0041000001D000000C7C0003FCDC5DD6A90B#1122448327493#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.cm.service.base|default#
    #1.5#000F1FB3D5CE0041000001D200000C7C0003FCDC5DD8547E#1122448327603#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.cm.ui|default#
    #1.5#000F1FB3D5CE0041000001D400000C7C0003FCDC5DD9C1FA#1122448327693#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.cm.ui.flex|default#
    #1.5#000F1FB3D5CE0041000001D600000C7C0003FCDC5DDD08C6#1122448327903#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.cm.xmlforms|default#
    #1.5#000F1FB3D5CE0041000001D800000C7C0003FCDC5DDE31FF#1122448327983#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.common.resourcebundle|default#
    #1.5#000F1FB3D5CE0041000001DA00000C7C0003FCDC5DDF971B#1122448328073#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.km.trex.ui|default#
    #1.5#000F1FB3D5CE0041000001DC00000C7C0003FCDC5DE03AB5#1122448328114#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.bc.crt|default#
    #1.5#000F1FB3D5CE0041000001DD00000C7C0003FCDC5DE11DF6#1122448328174#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.bc.protocol|default#
    #1.5#000F1FB3D5CE0041000001DF00000C7C0003FCDC5DE2D15C#1122448328284#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.bc.rf|default#
    #1.5#000F1FB3D5CE0041000001E100000C7C0003FCDC5DE445BA#1122448328384#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.bc.rf.manager|default#
    #1.5#000F1FB3D5CE0041000001E300000C7C0003FCDC5DE504A0#1122448328434#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.bc.rf.service|default#
    #1.5#000F1FB3D5CE0041000001E500000C7C0003FCDC5DE70349#1122448328564#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.bc.sf|default#
    #1.5#000F1FB3D5CE0041000001E700000C7C0003FCDC5DEA5D3D#1122448328784#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.bc.sf.service|default#
    #1.5#000F1FB3D5CE0041000001E900000C7C0003FCDC5DED1AB0#1122448328955#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.bc.util|default#
    #1.5#000F1FB3D5CE0041000001EB00000C7C0003FCDC5DEFE01C#1122448329145#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.bc.uwl|default#
    #1.5#000F1FB3D5CE0041000001EC00000C7C0003FCDC5E9C42B4#1122448340441#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.bc.uwl|UniversalWorklistDeploymentHook#
    #1.5#000F1FB3D5CE0041000001ED00000C7C0003FCDC5E9CFBC1#1122448340481#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.bc.wdf.ext|PortalFactory#
    #1.5#000F1FB3D5CE0041000001EE00000C7C0003FCDC5E9F2561#1122448340632#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.bc.wdf.ext|Bootstrap#
    #1.5#000F1FB3D5CE0041000001F000000C7C0003FCDC5E9F5DF4#1122448340642#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.async|default#
    #1.5#000F1FB3D5CE0041000001F200000C7C0003FCDC5EA2561F#1122448340832#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.base|ExtensionService#
    #1.5#000F1FB3D5CE0041000001F400000C7C0003FCDC5EA5B7A7#1122448341062#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.base.support|GenericService#
    #1.5#000F1FB3D5CE0041000001F600000C7C0003FCDC5EA7E082#1122448341202#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.gw|fwk#
    #1.5#000F1FB3D5CE0041000001F800000C7C0003FCDC5EAADA8C#1122448341393#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.gw|mgr_calendar#
    #1.5#000F1FB3D5CE0041000001F900000C7C0003FCDC5EAB34A8#1122448341423#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.gw|srvc_mail#
    #1.5#000F1FB3D5CE0041000001FA00000C7C0003FCDC5EAB9DAF#1122448341443#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|RoomsService#
    #1.5#000F1FB3D5CE0041000001FB00000C7C0003FCDC5EB66882#1122448342154#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|Concat#
    #1.5#000F1FB3D5CE0041000001FD00000C7C0003FCDC5EB766AE#1122448342214#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|ConfigReader#
    #1.5#000F1FB3D5CE0041000001FE00000C7C0003FCDC5EB7AD5F#1122448342234#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|RoomPropertyReader#
    #1.5#000F1FB3D5CE0041000001FF00000C7C0003FCDC5EB7F3AA#1122448342254#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|RoompartPropertyReader#
    #1.5#000F1FB3D5CE00410000020000000C7C0003FCDC5EB8211E#1122448342264#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|RoomStatusExtension#
    #1.5#000F1FB3D5CE00410000020100000C7C0003FCDC5EB9F733#1122448342384#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|RoomPartExtension#
    #1.5#000F1FB3D5CE00410000020200000C7C0003FCDC5EBA9809#1122448342424#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|RoomPartListPropertyProvider#
    #1.5#000F1FB3D5CE00410000020300000C7C0003FCDC5EBAF74D#1122448342454#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|CmRoomExtensionSP2FP#
    #1.5#000F1FB3D5CE00410000020400000C7C0003FCDC5EBFDA2E#1122448342775#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|CmDiscussionExtension#
    #1.5#000F1FB3D5CE00410000020500000C7C0003FCDC5EC0A76F#1122448342825#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|CmValueSetProvider#
    #1.5#000F1FB3D5CE00410000020600000C7C0003FCDC5EC0F082#1122448342845#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|RoomsTestExtension#
    #1.5#000F1FB3D5CE00410000020700000C7C0003FCDC5EC12276#1122448342855#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|RoomsTestValueSetProvider#
    #1.5#000F1FB3D5CE00410000020800000C7C0003FCDC5EC150B4#1122448342865#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|RSL_SERVICE#
    #1.5#000F1FB3D5CE00410000020900000C7C0003FCDC5EC1D870#1122448342905#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|RSL_NAVIGATION#
    #1.5#000F1FB3D5CE00410000020A00000C7C0003FCDC5EC59F89#1122448343145#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|FilterService#
    #1.5#000F1FB3D5CE00410000020B00000C7C0003FCDC5EC7DD75#1122448343295#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|public_area#
    #1.5#000F1FB3D5CE00410000020C00000C7C0003FCDC5EC97097#1122448343396#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|rpso#
    #1.5#000F1FB3D5CE00410000020D00000C7C0003FCDC5ECF700C#1122448343796#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|RoomPartsService#
    #1.5#000F1FB3D5CE00410000020E00000C7C0003FCDC5ECFE841#1122448343826#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|template_mechanism#
    #1.5#000F1FB3D5CE00410000020F00000C7C0003FCDC5ED16987#1122448343926#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|PCDTemplateMechanism#
    #1.5#000F1FB3D5CE00410000021000000C7C0003FCDC5ED19EF0#1122448343936#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room|PCDTemplateData#
    #1.5#000F1FB3D5CE00410000021100000C7C0003FCDC5EDFB98C#1122448344858#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.room.rfcadapter|RFCService#
    #1.5#000F1FB3D5CE00410000021200000C7C0003FCDC5EE0BF5F#1122448344928#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.rtc|rtmf_messaging#
    #1.5#000F1FB3D5CE00410000021300000C7C0003FCDC5EE9139E#1122448345468#/System/Server#sap.com/irj#com.sap.engine.services.jndi#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.engine.services.jndi#Plain###Path to object does not exist at jmsfactory, the whole lookup name is webContainer/applications/sap.com/irj/irj/jmsfactory/default/queueconnectionfactory.#
    #1.5#000F1FB3D5CE00410000021400000C7C0003FCDC5EEB5D6A#1122448345619#/System/Server#sap.com/irj#com.sap.engine.services.jndi#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.engine.services.jndi#Plain###Path to object does not exist at jmsfactory, the whole lookup name is webContainer/applications/sap.com/irj/irj/jmsfactory/default/topicconnectionfactory.#
    #1.5#000F1FB3D5CE00410000021500000C7C0003FCDC5EEC5A4F#1122448345689#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.rtc|rtmf_service#
    #1.5#000F1FB3D5CE00410000021600000C7C0003FCDC5EEC9822#1122448345699#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.rtc|RTMFServerBridge#
    #1.5#000F1FB3D5CE00410000021700000C7C0003FCDC5EEFEF01#1122448345919#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.rtc|collaboration_connector_awareness#
    #1.5#000F1FB3D5CE00410000021800000C7C0003FCDC5EF75204#1122448346410#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.rtc|RTCScriptConstants#
    #1.5#000F1FB3D5CE00410000021900000C7C0003FCDC5EF77D10#1122448346420#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.rtc|RTCHotDeploymentManagerService#
    #1.5#000F1FB3D5CE00410000021A00000C7C0003FCDC5EF8A53A#1122448346490#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.rtc|RTCClientManagerService#
    #1.5#000F1FB3D5CE00410000021B00000C7C0003FCDC5EFA0AE1#1122448346580#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.rtc|RTCClientPollingService#
    #1.5#000F1FB3D5CE00410000021C00000C7C0003FCDC5EFAE7D5#1122448346640#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.rtc|RTCClientAwareness#
    #1.5#000F1FB3D5CE00410000021D00000C7C0003FCDC5EFBEC68#1122448346710#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.rtc|RTCSessionManagerService#
    #1.5#000F1FB3D5CE00410000021E00000C7C0003FCDC5EFC3469#1122448346730#/System/Server#sap.com/irj#com.sap.engine.services.jndi#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.engine.services.jndi#Plain###Path to object does not exist at jmsfactory, the whole lookup name is webContainer/applications/sap.com/irj/irj/jmsfactory/default/queueconnectionfactory.#
    #1.5#000F1FB3D5CE00410000021F00000C7C0003FCDC5EFDA454#1122448346820#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.sync|scf#
    #1.5#000F1FB3D5CE00410000022100000C7C0003FCDC5F200A39#1122448349074#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.sync|sessiondata#
    #1.5#000F1FB3D5CE00410000022200000C7C0003FCDC5F203C1C#1122448349084#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.sync|WebExConfig#
    #1.5#000F1FB3D5CE00410000022300000C7C0003FCDC5F22916A#1122448349244#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.sync|RTCConfig#
    #1.5#000F1FB3D5CE00410000022400000C7C0003FCDC5F22D3A3#1122448349254#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.sync|SCFConnectorSessionsMapService#
    #1.5#000F1FB3D5CE00410000022500000C7C0003FCDC5F231A62#1122448349274#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.ui.async|default#
    #1.5#000F1FB3D5CE00410000022700000C7C0003FCDC5F3DD2AF#1122448351026#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.ui.async.meetingroom|meetingroom#
    #1.5#000F1FB3D5CE00410000022900000C7C0003FCDC5F482C99#1122448351707#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.ui.base|cs_rtc#
    #1.5#000F1FB3D5CE00410000022B00000C7C0003FCDC5F53E838#1122448352479#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.ui.base|cs_scf#
    #1.5#000F1FB3D5CE00410000022C00000C7C0003FCDC5F5418D2#1122448352489#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.ui.gw|gwuiservice#
    #1.5#000F1FB3D5CE00410000022E00000C7C0003FCDC5F5989C4#1122448352839#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.ui.room|roomuiservice#
    #1.5#000F1FB3D5CE00410000023000000C7C0003FCDC5F83BE6D#1122448355613#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.appl.ui.sync|sessiondata#
    #1.5#000F1FB3D5CE00410000023200000C7C0003FCDC5F8D0B3B#1122448356214#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.pc.homer|homer#
    #1.5#000F1FB3D5CE00410000023400000C7C0003FCDC5F925607#1122448356564#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.shared|default2#
    #1.5#000F1FB3D5CE00410000023600000C7C0003FCDC5F9631EF#1122448356815#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.shared|collaboration_base#
    #1.5#000F1FB3D5CE00410000023700000C7C0003FCDC5F963273#1122448356815#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.shared.ui|people#
    #1.5#000F1FB3D5CE00410000023900000C7C0003FCDC5F9773F2#1122448356905#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.coll.statusengine|status_engine#
    #1.5#000F1FB3D5CE00410000023B00000C7C0003FCDC5F99B26B#1122448357045#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.kmc.attachment.shared|attachment#
    #1.5#000F1FB3D5CE00410000023D00000C7C0003FCDC5F9C8494#1122448357235#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.kmc.people|default#
    #1.5#000F1FB3D5CE00410000023F00000C7C0003FCDC5F9E7FE8#1122448357366#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.kmc.people|umeservice#
    #1.5#000F1FB3D5CE00410000024000000C7C0003FCDC5FA79946#1122448357956#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.netweaver.kmc.util|default#
    #1.5#000F1FB3D5CE00410000024200000C7C0003FCDC5FCF773C#1122448360570#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.abstracturleditor|URLEditorService#
    #1.5#000F1FB3D5CE00410000024300000C7C0003FCDC5FDEE0C9#1122448361582#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.addlangattr|AddLangAttrService#
    #1.5#000F1FB3D5CE00410000024400000C7C0003FCDC5FE1C774#1122448361772#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.admin.propertyeditor|StandardPcmAdminPropertyObjectProvider#
    #1.5#000F1FB3D5CE00410000024500000C7C0003FCDC5FE6FB23#1122448362112#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.admin.propertyeditor|StandardPcmRuntimePropertyObjectProvider#
    #1.5#000F1FB3D5CE00410000024600000C7C0003FCDC5FE74481#1122448362132#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.admin.propertyeditor|StandardAdministrationPropertyEditingRuleService#
    #1.5#000F1FB3D5CE00410000024700000C7C0003FCDC5FE85483#1122448362203#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.admin.propertyeditor|StandardPersonalizationPropertyEditingRuleService#
    #1.5#000F1FB3D5CE00410000024800000C7C0003FCDC5FE87EB1#1122448362213#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.admin.propertyeditor|StandardPEControlFactory#
    #1.5#000F1FB3D5CE00410000024900000C7C0003FCDC5FEA951C#1122448362353#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.admin.util|aclutil#
    #1.5#000F1FB3D5CE00410000024A00000C7C0003FCDC5FEC52C4#1122448362463#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.appdesigner.contentcatalog|contentcatalog#
    #1.5#000F1FB3D5CE00410000024B00000C7C0003FCDC600697DF#1122448364185#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.appdesigner.framework|menu#
    #1.5#000F1FB3D5CE00410000024C00000C7C0003FCDC600F6219#1122448364756#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.appintegrator|template_processor#
    #1.5#000F1FB3D5CE00410000024D00000C7C0003FCDC6010EBD2#1122448364856#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.appintegrator|application_integrator#
    #1.5#000F1FB3D5CE00410000024E00000C7C0003FCDC60112A25#1122448364876#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.appintegrator|psid#
    #1.5#000F1FB3D5CE00410000024F00000C7C0003FCDC60119A43#1122448364906#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.appintegrator|Common_Configuration#
    #1.5#000F1FB3D5CE00410000025000000C7C0003FCDC6011D71C#1122448364916#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.appintegrator.sap|Transaction_Configuration#
    #1.5#000F1FB3D5CE00410000025100000C7C0003FCDC601252A0#1122448364957#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.appintegrator.sap.bwc|urlgenerator_bwc#
    #1.5#000F1FB3D5CE00410000025200000C7C0003FCDC60148BE7#1122448365097#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.appintegrator.sap.bwc|psid#
    #1.5#000F1FB3D5CE00410000025300000C7C0003FCDC6014FE18#1122448365127#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.bidi.utils|_RTLUtils#
    #1.5#000F1FB3D5CE00410000025400000C7C0003FCDC6016331F#1122448365207#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.common.commonservices|CommonService#
    #1.5#000F1FB3D5CE00410000025500000C7C0003FCDC601750E5#1122448365277#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.compatibility50.cache|cache#
    #1.5#000F1FB3D5CE00410000025600000C7C0003FCDC6019B839#1122448365437#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.compatibility50.systemlandscape|landscape#
    #1.5#000F1FB3D5CE00410000025700000C7C0003FCDC601E35D9#1122448365728#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.contentfetching|contentFetchingService#
    #1.5#000F1FB3D5CE00410000025800000C7C0003FCDC60250E06#1122448366178#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.contentmigration.contentmigrationservice|contentmigration#
    #1.5#000F1FB3D5CE00410000025900000C7C0003FCDC60284A4F#1122448366389#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.contentmigration.contentmigrationservice|mapping#
    #1.5#000F1FB3D5CE00410000025A00000C7C0003FCDC60295B2F#1122448366459#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.contentmigration.pagemigrationhandlerservice|default#
    #1.5#000F1FB3D5CE00410000025B00000C7C0003FCDC60331EAD#1122448367100#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.contentmigration.parmigrationhandlerservice|parhandler#
    #1.5#000F1FB3D5CE00410000025C00000C7C0003FCDC6035010C#1122448367230#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.contentmigration.pcdmigrationhandlerservice|pcdhandler#
    #1.5#000F1FB3D5CE00410000025D00000C7C0003FCDC604873F4#1122448368502#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.desktop.desktopservice|desktopservice#
    #1.5#000F1FB3D5CE00410000025E00000C7C0003FCDC604D0EA3#1122448368802#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.drservices.targetmainobjects|targetmainobjects#
    #1.5#000F1FB3D5CE00410000025F00000C7C0003FCDC604FDD20#1122448368982#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.drservices.targetmainobjects|sapunifierutils#
    #1.5#000F1FB3D5CE00410000026000000C7C0003FCDC60501548#1122448369002#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.dsm|dsmservice#
    #1.5#000F1FB3D5CE00410000026100000C7C0003FCDC60520CCF#1122448369133#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.epcf.loader|epcfloader#
    #1.5#000F1FB3D5CE00410000026200000C7C0003FCDC60566717#1122448369413#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.epcf.toolbox|epcftoolbox#
    #1.5#000F1FB3D5CE00410000026300000C7C0003FCDC6056DD2F#1122448369443#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.heartbeats|NotificationTest#
    #1.5#000F1FB3D5CE00410000026400000C7C0003FCDC6057BAA9#1122448369503#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.htmlb|htmlb#
    #1.5#000F1FB3D5CE00410000026500000C7C0003FCDC605C3363#1122448369793#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.httpconnectivity.httpauthentication|ClientAuthHookService#
    #1.5#000F1FB3D5CE00410000026600000C7C0003FCDC605E5A6B#1122448369934#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.httpconnectivity.httpauthentication|ClientGetMethodAuthService#
    #1.5#000F1FB3D5CE00410000026700000C7C0003FCDC60601E3D#1122448370054#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.httpconnectivity.httpauthentication|ClientPostMethodAuthService#
    #1.5#000F1FB3D5CE00410000026800000C7C0003FCDC606058ED#1122448370064#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.httpconnectivity.httpauthentication|ClientBasicMethodAuthService#
    #1.5#000F1FB3D5CE00410000026900000C7C0003FCDC606092D1#1122448370084#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.httpconnectivity.httpauthentication|ServerGetMethodAuthService#
    #1.5#000F1FB3D5CE00410000026A00000C7C0003FCDC6060E533#1122448370104#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.httpconnectivity.httpauthentication|ServerPostMethodAuthService#
    #1.5#000F1FB3D5CE00410000026B00000C7C0003FCDC60611FB7#1122448370114#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.httpconnectivity.httpauthentication|ServerBasicMethodAuthService#
    #1.5#000F1FB3D5CE00410000026C00000C7C0003FCDC60615B4E#1122448370134#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.httpconnectivity.httpauthentication|ClientAuthManagerService#
    #1.5#000F1FB3D5CE00410000026D00000C7C0003FCDC6061B839#1122448370154#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.httpconnectivity.iviewcatcher.runtime|IWebSiteContentFetcherService#
    #1.5#000F1FB3D5CE00410000026E00000C7C0003FCDC60621561#1122448370184#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.ivs.connectorservice|connector#
    #1.5#000F1FB3D5CE00410000026F00000C7C0003FCDC60649FC4#1122448370344#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.ivs.httpservice|http#
    #1.5#000F1FB3D5CE00410000027000000C7C0003FCDC60666F13#1122448370464#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.ivs.httpservice|proxy#
    #1.5#000F1FB3D5CE00410000027100000C7C0003FCDC6067BB30#1122448370555#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.ivs.init|genericcreator#
    #1.5#000F1FB3D5CE00410000027200000C7C0003FCDC606AE35A#1122448370755#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.ivs.iviewservice|SLUtilsSrv#
    #1.5#000F1FB3D5CE00410000027300000C7C0003FCDC606AE418#1122448370755#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.ivs.iviewservice|SLObjectsManagerSrv#
    #1.5#000F1FB3D5CE00410000027400000C7C0003FCDC606AE485#1122448370755#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.ivs.iviewservice|iViewsSrv#
    #1.5#000F1FB3D5CE00410000027500000C7C0003FCDC606AE4EE#1122448370755#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.ivs.iviewservice|pagesSrv#
    #1.5#000F1FB3D5CE00410000027600000C7C0003FCDC606CCDD1#1122448370885#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.ivs.iviewservice|layoutsSrv#
    #1.5#000F1FB3D5CE00410000027700000C7C0003FCDC606D1B8E#1122448370905#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.ivs.iviewservice|templates_cache_srv#
    #1.5#000F1FB3D5CE00410000027800000C7C0003FCDC606DCA46#1122448370945#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.ivs.iviewservice.oldpcm|iviews_dt#
    #1.5#000F1FB3D5CE00410000027900000C7C0003FCDC606DCB1D#1122448370945#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.ivs.iviewservice.oldpcm|iviews#
    #1.5#000F1FB3D5CE00410000027A00000C7C0003FCDC606DFFD8#1122448370965#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.ivs.iviewservice.oldpcm|templates_cache#
    #1.5#000F1FB3D5CE00410000027B00000C7C0003FCDC606E8216#1122448370995#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.ivs.systemlandscapeservice|producerSrv#
    #1.5#000F1FB3D5CE00410000027C00000C7C0003FCDC6073B7D4#1122448371336#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.ivs.systemlandscapeservice.oldpcm|systemlandscape#
    #1.5#000F1FB3D5CE00410000027D00000C7C0003FCDC60750222#1122448371416#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.langattrprop|LangAttrPropService#
    #1.5#000F1FB3D5CE00410000027E00000C7C0003FCDC60765D13#1122448371506#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.mdc|mdc#
    #1.5#000F1FB3D5CE00410000027F00000C7C0003FCDC60785851#1122448371636#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.navigation.AliasService|AliasService#
    #1.5#000F1FB3D5CE00410000028000000C7C0003FCDC607B2A95#1122448371826#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.navigation.helperservice|navigation_events_helper#
    #1.5#000F1FB3D5CE00410000028100000C7C0003FCDC607C5AB6#1122448371907#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.navigation.mimeservice|navigation_mime_repository#
    #1.5#000F1FB3D5CE00410000028200000C7C0003FCDC607C5B7C#1122448371907#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.navigation.service|navigation#
    #1.5#000F1FB3D5CE00410000028300000C7C0003FCDC607C5C18#1122448371907#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.pagebuilder.utils|FPM#
    #1.5#000F1FB3D5CE00410000028400000C7C0003FCDC607D8FB0#1122448371977#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.pcd.pcm.roles.rolecontainer|rolecontainerservice#
    #1.5#000F1FB3D5CE00410000028500000C7C0003FCDC607F41D2#1122448372097#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.pcd.rolenavigationservice|rolenavigation#
    #1.5#000F1FB3D5CE00410000028600000C7C0003FCDC60808C35#1122448372177#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.pcd.roleservice|roles#
    #1.5#000F1FB3D5CE00410000028700000C7C0003FCDC60808CFE#1122448372177#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.pcd.transportapplication|transportapplication#
    #1.5#000F1FB3D5CE00410000028800000C7C0003FCDC608C1312#1122448372928#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.pcd.transportapplication|deploy#
    #1.5#000F1FB3D5CE00410000028900000C7C0003FCDC608C5CED#1122448372948#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.pcm.admin.apiservice|default#
    #1.5#000F1FB3D5CE00410000028A00000C7C0003FCDC608CBC84#1122448372978#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.pcm.admin.plainfolder_converter|default#
    #1.5#000F1FB3D5CE00410000028B00000C7C0003FCDC608EA224#1122448373098#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.processlogger.processloggerservice|processlogger#
    #1.5#000F1FB3D5CE00410000028C00000C7C0003FCDC608EFC88#1122448373118#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.productivity.desktop|DesktopManager#
    #1.5#000F1FB3D5CE00410000028D00000C7C0003FCDC608FF685#1122448373188#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.productivity.desktop|DesktopUpgrader#
    #1.5#000F1FB3D5CE00410000028E00000C7C0003FCDC6091650B#1122448373278#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.productivity.dom|dom#
    #1.5#000F1FB3D5CE00410000028F00000C7C0003FCDC609199FD#1122448373299#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.productivity.resolverservice|ruleManager#
    #1.5#000F1FB3D5CE00410000029000000C7C0003FCDC6095A715#1122448373559#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.productivity.resolverservice|resolver#
    #1.5#000F1FB3D5CE00410000029100000C7C0003FCDC6096D8EC#1122448373639#/System/Server#sap.com/irj#com.sap.portal.desktop#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.desktop#Java###PcmRuleStorage$RuleCache: Rule Cache created##
    #1.5#000F1FB3D5CE00410000029200000C7C0003FCDC60975C81#1122448373669#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.productivity.utils|sap_utilities#
    #1.5#000F1FB3D5CE00410000029300000C7C0003FCDC60975D41#1122448373669#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.prt.cache|dbcacheservice#
    #1.5#000F1FB3D5CE00410000029400000C7C0003FCDC609883B4#1122448373749#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.rtlcomphook|RightToLeftComponentHook#
    #1.5#000F1FB3D5CE00410000029500000C7C0003FCDC6099C13E#1122448373829#/System/Server#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#18####2f853650fe6d11d99481000f1fb3d5ce#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.portal.prt.runtime.broker#Plain###Loading service: com.sap.portal.runtime.application.contentconversion|contentconversion#
    #1.5#000F1FB3D5CE00410000029600000C7C0003FCDC609C367B#1122448373989#/System/Server#sap.com/i

  • Validation error message not found in PI 7.1 :

    I've enabled Validation at adapter engine level.When a message is failed at validation level,i got an alert email with message id.
    But i can't see the message in Message monitorring and Communication chennel monitorring as well.
    Any idea/.??????
    Thanks
    Prabhakar

    I've enabled Validation at adapter engine level.When a message is failed at validation level,i got an alert email with
    message id.
    But i can't see the message in Message monitorring and Communication chennel monitorring as well.
    XML Validation in Adapter Engine = backward Error handling
    backward Error handling = Message Not Persisted ....hence there would be no message that you can see.
    For more info refer page 14, 17
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b04bc560-e4e7-2a10-92ab-92dbf097aae1?quicklink=events&overridelayout=true
    Regards,
    Abhishek.

  • Component Monitor - Item not found /runtime

    Dear all,
    When i try to open the component monitor via System Administration -> System configuration -> Knowledge management, i get the following error:
    Item not found
    /runtime
    The item you are trying to access is not available. Try to check....
    This error came up the first time after deployment of some custom scheduler tasks. The same tasks were deployed on DVL and QA systems, and everything worked fine there.
    There is a thread on sdn forum (https://www.sdn.sap.com/irj/scn/thread?messageID=902388) that mentions the same error, but the explanation there is not really clear to me.
    I deleted my custom tasks via the configUninstaller and removed the archives via Support and did a restart of the portal, but the error stays the same.
    I hope someone can help.
    Kind regards,
    J.

    Closed. Not solved.

  • 'Item Not Found 'error in Middleware Monitor

    Hi,
    Monitoring the MW Monitor..
    There is a BDoc Validation error. BDoc type is 'BEABILLDOCCRMB'.
    The message on the error segment says ' Item was Not found',  Module CRM_DOWNLOAD_BEA_VAL.
    Can anyone help me.
    Pratima

    Hi Animesh,
    There is an Accounting document and it is transferred to finance.
    But it is still in the 'Item Not found' state in the MW monitor with a validation error.
    Regards,
    Pratima

  • Windows 7 error: Location is not available or Item not found

    I'm using windows 7 ultimate. I have a directory on a 1TB external usb drive called "1976 T.N.T". I am neither able to access this directory nor am I able to delete it. When I double click to access it windows says -
    Message Title: "Location is not available"
    Message Text: J:\Music\Library\Rock-Metal\ACDC\1976 T.N.T refers to a location that is unavailable. It could be on a hard drive on this computer.or on a network. Check to make sure that the disk is properly inserted, or that you are connected to the Internet
    or your network and then try again. If it still cannot be located the information might have been moved to a different location.
    When I try to delete it windows says -
    Message Title: Item Not Found
    Message Text: Could not find this item.
    This item is no longer located in J:\Music\Library\Rock-Metal\ACDC. Verify the item's location and try again.
    I have tried the following -
    1. Deleting file using command prompt but that doesn't work
    2. Check disk with both options "File system errors" and "Bad sector recovery" selected - it does not report any errors and the problem persists
    3. Rebooting the computer
    4. Disconnecting the drive and connecting it to my xp pro laptop (messages on xp are slightly different but to the same effect)
    Any suggestions short of formatting the drive will be appreciated.

    The cause of this is as follows:
    The directories in question were created or last modified by a process other than Windows Explorer. This process created a directory name with a space at the end. When you created a duplicate directory, the exact directory name you created was therefore
    not exactly the same; it had no space on the end. That is why both directories with the apparent same name could coexist.
    Note: if you attempt to create a directory from within Windows Explorer with a space on the end, the process explorer.exe is designed to prevent this from happening. That's why it's never usually an issue.
    To reproduce this problem, you could do the following:
    1) Create C:\foo
    2) Create C:\bar
    3) Use Robocopy to create the erroneous directory using the following command:
    robocopy "C:\foo" C:\bar" /E
    Notice that I missed the first double-quote on the target location. Robocopy should have responded with an error, but due to the way it interpreted my input, it didn't.
    Now you will see a directory called C:\foo\bar
    Except this directory is actually: "bar " - the word "bar" with a space on the end.
    Now try deleting C:\foo altogether. It won't because there is a directory underneath it that has an invalid name.
    Now try entering C:\foo, and creating a second directory called "bar". This will work, and there will appear to be two directories named "bar".
    But this time you can go up a level and delete "C:\foo".
    Put it down to a bug in Windows, a bug in Robocopy, whatever you like! That's the reason though...

  • "Error: Document not found (WWC-46000)" with a form based on a table with blob item

    Hi all,
    I have to manage a table-based form. One of the fields of the table is BLOB and the corrisponding field of the form is HIDDEN.
    When I push the INSERT button all works well but when I try to UPDATE I get "Error: Document not found. (WWC-46000)".
    Have you some suggestions ?
    Thanks,
    Antonino
    p.s. Oracle Portal 3.0.7.6.2 / NT
    null

    Sorry, I think I did not explain well my problem.
    Imagine this simple table:
    key number;
    description varchar2(50);
    image blob;
    I need to make a form that contains the corresponding "key" field and the "description" field but not the "image" one. I don't want to allow the end user to upload images!
    When I insert a row the form works well and in the "image" field of the table an empty blob or null (now I don't remember) is stored: that's ok.
    Now imagine I want to change the value of the "description" field. I submit a query for the right key, I type a new value for the description and finally I push UPDATE button but....an error occours.
    I think this error is related with the Blob item of the table but I'm not sure.
    Thanks again,
    Antonino
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Dmitry Nonkin([email protected]):
    Antonino,
    If I understood the problem correctly:
    The form's item type for BLOB column used to upload content cannot be hidden, that's why we have a special item type FileUpload(binary).
    Thanks,
    Dmitry<HR></BLOCKQUOTE>
    null

  • IHC errors valid clearing partner not found and no header details found while idoc creation after f110

    IHC errors :valid clearing partner not found and no header details found while idoc creation after f110
    Please let me know where the config is missing for ihc automatic payment program.in we02 status is not 53.
    Please help

    Hi
    Please share the error message in the IDOC.
    If the error message is IHC204 "No valid clearing partner was found", it may be due to the missing correct configuration in Set Up Creation of Payment Requests for Inbound IDoc in FI, which links the clearing partner, ALE logical system partner type and IHC account number.
    Cheers
    taro

  • Error when accessing /bw_document/MasterData/... (Item not found)

    Hello,
    I'm trying to index the BI documents (Master Data) repository with TREX. As fas as I know the BI documents are now stored in KM (=portal). I found /bw_document/MasterData in KM but when I trigger the indexing of this repository he stops after 2 seconds with status=error (type: crawler -> are there anymore details on this?!)
    When I browse to this rep. using "Content Administration" -> "KM Content" I see the following error message:
    Item not found
    /bw_document/MasterData/0D_PH2
    The item you are attempting to access is not available. Check that the name or link is correct. You might also check whether the associated repository is currently accessible.
    What's wrong here?
    BR,
    Markus

    Problem solved. The InfoObject "0D_PH2" was not yet activated from BI Content in RSA1. Don't know why he has it in his KM Repository, but after activating it the error message is gone.

  • Regarding Template updates, what does this error " not updated, item not found" mean?

    This is the second time I've posted this question so hopefully somebody will respond. At some point in the last few weeks I found that I could no longer apply a template in a group operation (returns the error shown above). If I modify the template and save it it shows all the related files to be updated but does not actually update them and again returns the error "not updated, item not found". As a test I created a duplicate of a particular .html file and applied the associated template successfully. When I apply a template change it does properly update the newly created file but not the others. I also did a mechanical file compare (using windiff.exe) between the original and duplicate file and there are NO differences in the two .html files. I have also deleted and recreated my site maps several times.
    As an aside, Library items do update successfully.
    I am running Dreamweaver CS6 on Windows 7.

    I have an extensive home network and I consider myself to be very proficient with personal computers (had one since 1981) so let's start at that level.
    I have you beat by 2 years. Bought an Apple II+ in 1979!
    When this problem first started, I went to another PC (home built desktop Win 7 64 bit) I have and created a new Dreamweaver site copy using an instance of the site that was on a network share running on a NAS box (Netgear RAID5) that I use for central file storage. Just for a test I did the same thing on my main working PC (see below) and created a new site with the data that was on the network share. Well, lo and behold the template problem went away with both of the two sites I am having trouble with. Now I have no idea why sites housed on my PC are having a problem but that seems to be the issue.
    Your setup is very similar to mine - NAS (I'm using an Intel NAS) housing all my working files.
    Just for a test I did the same thing on my main working PC (see below) and created a new site with the data that was on the network share. Well, lo and behold the template problem went away with both of the two sites I am having trouble with.
    So it's working in the duplicate site, but not the current site. And in the current site, you have some files that update as desired and some that do not? Why not just make the duplicate site be the main working site?
    Anyhow, I cannot think of any wrinkle that would cause DW to update some legitimate child files in a site but not others, except for a corrupted file cache.

  • Error: Document not found. (WWC-46000) while updating a form whit blob items

    Hi all,
    I have to manage a table-based form. The table has a BLOB field that allows NULL.
    The blob field of the form is hidden.
    When I try to INSERT all works well but when I attempt to UPDATE I get "Error: Document not found. (WWC-46000)".
    Have you some suggestions ?
    Thanks,
    Antonino
    p.s. Oracle Portal 3.0.7.6.2 / NT

    I have the same problem. I have one form to insert file (works fine), and another form to update that record, but not the file. The fields of the file (blob and mime type) are not on the form at all, and getting the message WWC-46000.

  • DADs on WLS 11g (version 10.3.6.0) do not work (Error 404--Not Found)

    Actually we use Application Server 10g (version 10.1.2.3.0) for different Forms 10g Applications (roundabout 1000 Forms) and want to change to Forms 11g and Weblogic Server 11g (version 10.3.6.0). A Test-Application on the Weblogic Server works fine, but DAD’s do not work at all.
    In Enterprise Manager 10g i can configure DADs within the GUI of the Enterprise Manager, where i can see, if a connection could be established or not.
    In Enterprise Manager 11g Fusion Middleware Control this doesn't seem to exist anymore, so i tried to configure the DADs manually, but something has to be wrong or missing, because there is no connection to the database and the following error appears:
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
    If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
    I added several DAD’s to /opt/oracle/product/Middleware/asinst_1/config/OHS/ohs1/mod_plsql/dads.conf like this:
    <Location /pls/jd-download-dev>
    SetHandler pls_handler
    Order allow,deny
    Allow from All
    AllowOverride None
    PlsqlDatabaseUsername w_web_user_download
    PlsqlDatabasePassword @BWKChfgPacV6yQL40lIKZqXUUA9wC4cmAw==
    PlsqlDatabaseConnectString jddev TNSFormat
    PlsqlNLSLanguage German_Germany.WE8ISO8859P1
    PlsqlAuthenticationMode Basic
    PlsqlDefaultPage w_anwendung.p_web_show_document
    PlsqlAlwaysDescribeProcedure Off
    PlsqlErrorStyle DebugStyle
    </Location>
    The passwords were obfuscated with dadTool.pl and the http-Server restarted with /opt/oracle/product/Middleware/asinst_1/bin/opmnctl restartproc process-type=OHS
    The files /opt/oracle/product/Middleware/asinst_1/config/OHS/ohs1/mod_plsql.cache.conf and /opt/oracle/product/Middleware/asinst_1/config/OHS/ohs1/moduleconf.plsql.conf were left unchanged.
    Our Test-Application generates the following link
    'http://172.106.2.7:9001/pls/jddevdev/B_ARCHIVE.P_ARCHIVE_VIEW?docfid=200'
    that seems to be ok, because when i replace IP and port with our old IAS it works fine, but the WebLogic Server generates the above mentioned error.
    To get some more information i searched an error_log in /opt/oracle/product/Middleware/asinst_1/diagnostics/logs/OHS/ohs1 but there isn’t any.
    I used the following Documentation for configuring the DADs which is for HTTP Server 11g Release 1 (version 11.1.1), because I could not find one for version 10.3.6.0:
    http://docs.oracle.com/cd/E23943_01/web.1111/e10144/under_mods.htm#i1055269
    So probably there are differences between configuring version 10.3.6.0 and version 11.1.1 and so something is wrong configured or missing...
    Thank you in advance for your help
    Udo

    Hi Raj,
    it is a Sparc Solaris 10
    and yes that's my enviorment.
    After some more tests it's seems it's not a real bug but no realy nice working solution.
    Eclipse uses for all instances the same secure storage, where OEPE also saves the password.
    And if I look right the pasword was saved without the user context, so if you use an other user he takes the same password from the old user.
    and I doesn't know how do OEPE check the connection in reality or only reply the last failed login message.
    After deleting the complete secure storage and test it again with the juno version it works well.

  • [SOLVED] == ERROR: file not found: `/sbin/dmsetup'

    [EDIT] A much simpler way to deal with this is to explicitly ignore the kernel update during a full system update:
    pacman -Syu --ignore linux
    Then explicitly update the kernel alone:
    pacman -S linux
    [EDIT] First, after a full system update I had to move the STUB kernel image from the UEFI directory back to /boot, them recreate the images a second time. The systemd service moved it back to the UEFI directory.
    [EDIT] The use of 'mdadm_udev' in HOOKS= also seems to be no longer just 'preferred' to the 'mdadm' hook but instead is now mandatory.
    I've read the news item...
    Changes to LVM
    2013-02-12 - Thomas Bächler
    With lvm2 2.02.98-3, we now utilize lvmetad to activate LVM volumes automatically. This implies the following changes:
        The lvm2 initramfs hook now requires the udev hook.
        The use_lvmetad = 1 must be set in /etc/lvm/lvm.conf. This is the default now - if you have a lvm.conf.pacnew file, you must merge this change.
        You can restrict the volumes that are activated automatically by setting the auto_activation_volume_list in /etc/lvm/lvm.conf. If in doubt, leave this option commented out.
        If you need monitoring (needed for snapshots), run systemctl enable lvm-monitoring.service.
        The lvmwait kernel command line option is no longer needed and has no effect.
    If you run pacman -Syu and update device-mapper, linux and lvm2 at the same time, you will get an error message that /sbin/dmsetup is missing. Run mkinitcpio -p linux again after the update to avoid any problems.
    ...and I do get the message...
    ==> ERROR: file not found: `/sbin/dmsetup'
    ...but after a full system update with...
    pacman -Syu
    ...when I execute...
    mkinitcpio -p linux
    ...this is what I get...
    Building image from preset: 'default'
    /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    ERROR:specified kernel image does not exist: `/boot/vmlinuz-linux'
    Building image from preset: 'fallback'
    /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    ERROR:specified kernel image does not exist: `/boot/vmlinuz-linux'
    So of course if I reboot I get the dreaded 'No volume groups found' message.
    I should mention that I use the systemd path and service to move the kennel after it has been updated.
    Last edited by KairiTech (2013-04-07 02:45:12)

    With lvm2 2.02.98-3, we now utilize lvmetad to activate LVM volumes automatically. This implies the following changes:
        The lvm2 initramfs hook now requires the udev hook.
        The use_lvmetad = 1 must be set in /etc/lvm/lvm.conf. This is the default now - if you have a lvm.conf.pacnew file, you must merge this change.
        You can restrict the volumes that are activated automatically by setting the auto_activation_volume_list in /etc/lvm/lvm.conf. If in doubt, leave this option commented out.
        If you need monitoring (needed for snapshots), run systemctl enable lvm-monitoring.service.
        The lvmwait kernel command line option is no longer needed and has no effect.
    Just to confirm. You did all these steps, right?
    EDIT: I just noticed something:
    KairiTech wrote:HOOKS="base udev autodetect sata mdadm usbinput keymap encrypt lvm2 filesystems timestamp shutdown"
    Replace
    mdadm
    with
    mdadm_udev
    . Maybe this is nothing, but it is recommended to use this one instead of the other.
    NEW EDIT: Expecially this one
    The use_lvmetad = 1 must be set in /etc/lvm/lvm.conf. This is the default now - if you have a lvm.conf.pacnew file, you must merge this change.
    Last edited by s1ln7m4s7r (2013-03-24 20:42:55)

  • EPM 11.1.2.3 ,Error 404 - Not Found

    Hi All,
    I am getting the following error after my installation and configuration of EPM 11.1.2.3 and when I try to access the Workspace URL.
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol --
    HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the
    Request-URI. No indication is given of whether the condition is temporary or
    permanent.
    If the server does not wish to make this information available to the client,
    the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code
    SHOULD be used if the server knows, through some internally configurable
    mechanism, that an old resource is permanently unavailable and has no forwarding
    address.
    I installed 11.1.2.3 in windows 7 ultimate OS and 64 bit and using sql server 2005 Database and configured Essbase,planning, hfm, arm, fcm,fdm ,hpcm, , everything was configured successfully but when I open the workspace URL it is throwing "Error 404 not found"
    I tried accessing http://machinename:7001/console (I replaced machinename with my machinename)
    even here I am getting the same error, but I checked the database and it has the table hss_component_types and it is populated with the various products.
    could you guide me
    Regards,
    SG
    The following is the error I am getting in C:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services
    <Jul 9, 2013 7:30:18 PM CDT> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Jul 9, 2013 7:30:18 PM CDT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <Jul 9, 2013 7:30:18 PM CDT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
    C:\Oracle\Middleware\user_projects\domains\EPMSystem\lib\audit-client.jar;C:\Oracle\Middleware\user_projects\domains\EPMSystem\lib\css.jar;C:\Oracle\Middleware\user_projects\domains\EPMSystem\lib\ctg_custom.jar;C:\Oracle\Middleware\user_projects\domains\EPMSystem\lib\ldapbp.jar;C:\Oracle\Middleware\user_projects\domains\EPMSystem\lib\opencsv-1.8.jar;C:\Oracle\Middleware\user_projects\domains\EPMSystem\lib\registry-api.jar;C:\Oracle\Middleware\user_projects\domains\EPMSystem\lib\wlpool.jar>
    <Jul 9, 2013 7:30:18 PM CDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.2.5-50-153520-1.6.0_37-20121220-0844-windows-x86_64 from Oracle Corporation>
    <Jul 9, 2013 7:30:47 PM CDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 >
    <Jul 9, 2013 7:30:57 PM CDT> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://SUBHASUBBU:7001.>
    <Jul 9, 2013 7:30:57 PM CDT> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
    <Jul 9, 2013 7:30:57 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Jul 9, 2013 7:30:57 PM CDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Jul 9, 2013 7:30:58 PM CDT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\logs\EPMServer0.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Jul 9, 2013 7:30:58 PM CDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\logs\EPMServer0.log00002. Log messages will continue to be logged in C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\logs\EPMServer0.log.>
    <Jul 9, 2013 7:30:58 PM CDT> <Notice> <Log Management> <BEA-170019> <The server log file C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\logs\EPMServer0.log is opened. All server side log events will be written to this file.>
    OracleFileSSOWalletImpl.getWalletData: enter...
    OracleFileSSOWalletImpl.getWalletData: System.getProperty(user.name)=SUBHASUBBU$
    OracleFileSSOWalletImpl.getWalletData: locking (shared) dummy sso file..
    OracleFileSSOWalletImpl.getWalletData: locking (shared) sso file..
    Oracle Wallet: wallet size 8349
    OracleWallet: getSecretStore
    OracleSecretStore: loading wallet from stream
    OracleSSOKeyStoreImpl: engineLoad
    OracleKeyStoreSpi: Loading wallet from stream
    OracleKeyStoreSpi: Opening safe 0
    OracleKeyStoreSpi: Opening safe 0
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: Opening safe 0
    OracleKeyStoreSpi: found secret store bag
    OracleKeyStoreSpi: found secret store bag
    OracleKeyStoreSpi: found secret store bag
    OracleKeyStoreSpi: found secret store bag
    OracleKeyStoreSpi: Opening safe 0
    OracleKeyStoreSpi: Opening safe 0
    Processing TP 0
    Storing TP 0 as CN=Entrust.net Secure Server Certification Authority
    Processing TP 1
    Storing TP 1 as CN=Entrust.net Secure Server Certification Authority 1
    Processing TP 2
    Storing TP 2 as CN=Entrust.net Certification Authority (2048)
    Processing TP 3
    Storing TP 3 as CN=GTE CyberTrust Global Root
    Processing TP 4
    Storing TP 4 as OU=Secure Server Certification Authority
    Processing TP 5
    Storing TP 5 as OU=Class 1 Public Primary Certification Authority
    Processing TP 6
    Storing TP 6 as OU=Class 2 Public Primary Certification Authority
    Processing TP 7
    Storing TP 7 as OU=Class 3 Public Primary Certification Authority
    OracleKeyStoreSpi: Storing Secret0
    Getting sequence from bag
    Getting alias from sequence
    Getting secret from sequence
    OracleKeyStoreSpi: Storing Secret1
    Getting sequence from bag
    Getting alias from sequence
    Getting secret from sequence
    OracleKeyStoreSpi: Storing Secret2
    Getting sequence from bag
    Getting alias from sequence
    Getting secret from sequence
    OracleKeyStoreSpi: Storing Secret3
    Getting sequence from bag
    Getting alias from sequence
    Getting secret from sequence
    OracleKeyStoreSpi: Keystore Loaded
    OracleWallet: getSecretStore
    OracleFileSSOWalletImpl.getWalletData: enter...
    OracleFileSSOWalletImpl.getWalletData: System.getProperty(user.name)=SUBHASUBBU$
    OracleFileSSOWalletImpl.getWalletData: locking (shared) dummy sso file..
    OracleFileSSOWalletImpl.getWalletData: locking (shared) sso file..
    Oracle Wallet: wallet size 3941
    OracleWallet: getSecretStore
    OracleSecretStore: loading wallet from stream
    OracleSSOKeyStoreImpl: engineLoad
    OracleKeyStoreSpi: Loading wallet from stream
    OracleKeyStoreSpi: Opening safe 0
    OracleKeyStoreSpi: Opening safe 0
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: found cert bag
    OracleKeyStoreSpi: Opening safe 0
    OracleKeyStoreSpi: found secret store bag
    OracleKeyStoreSpi: found secret store bag
    OracleKeyStoreSpi: found secret store bag
    OracleKeyStoreSpi: found secret store bag
    OracleKeyStoreSpi: Opening safe 0
    OracleKeyStoreSpi: Opening safe 0
    Processing TP 0
    Storing TP 0 as OU=Class 1 Public Primary Certification Authority
    Processing TP 1
    Storing TP 1 as CN=GTE CyberTrust Global Root
    Processing TP 2
    Storing TP 2 as OU=Class 2 Public Primary Certification Authority
    Processing TP 3
    Storing TP 3 as OU=Class 3 Public Primary Certification Authority
    OracleKeyStoreSpi: Storing Secret0
    Getting sequence from bag
    Getting alias from sequence
    Getting secret from sequence
    OracleKeyStoreSpi: Storing Secret1
    Getting sequence from bag
    Getting alias from sequence
    Getting secret from sequence
    OracleKeyStoreSpi: Storing Secret2
    Getting sequence from bag
    Getting alias from sequence
    Getting secret from sequence
    OracleKeyStoreSpi: Storing Secret3
    Getting sequence from bag
    Getting alias from sequence
    Getting secret from sequence
    OracleKeyStoreSpi: Keystore Loaded
    OracleWallet: getSecretStore
    <Jul 9, 2013 7:31:19 PM CDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Jul 9, 2013 7:31:19 PM CDT> <Notice> <Security> <BEA-090083> <Storing boot identity in the file: C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\security\boot.properties>
    <Jul 9, 2013 7:31:41 PM CDT> <Warning> <JTA> <BEA-110503> <The migrator(the AdminServer for manual JTA migration policy, or the Singleton Master for automatic JTA migration policy) is not available. Will skip JTA TRS failback because isStrictOwnershipCheck is [false]. This may lead to potencial TLOG corruption if TRS of EPMServer0 has been migrated to backup server and the backup server is accessing the TLOG of EPMServer0. More safety can be achieved by setting isStrictOwnershipCheck to [true].>
    <Jul 9, 2013 7:31:42 PM CDT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\logs\access.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Jul 9, 2013 7:31:42 PM CDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\logs\access.log00002. Log messages will continue to be logged in C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\logs\access.log.>
    <Jul 9, 2013 7:32:18 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Jul 9, 2013 7:32:18 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    Using OraclePKI Provider
    javax.net.ssl.TrustManagerFactory supported
    javax.net.ssl.KeyManagerFactory supported
    Using OracleJSSE103 Provider
    <Jul 9, 2013 7:32:21 PM CDT> <Warning> <JDBC> <BEA-001552> <The logging last resource (LLR) data source accountreconciliation_datasource will not function when it is a participant in a global transaction that spans multiple WebLogic Server instances because remote JDBC support is disabled. LLR will function in single-server configurations.>
    <Jul 9, 2013 7:32:21 PM CDT> <Warning> <JDBC> <BEA-001552> <The logging last resource (LLR) data source financialclose_datasource will not function when it is a participant in a global transaction that spans multiple WebLogic Server instances because remote JDBC support is disabled. LLR will function in single-server configurations.>
    <Jul 9, 2013 7:33:42 PM CDT> <Warning> <Security> <BEA-090668> <Ignored deployment of role "Admin" for resource "type=<url>, application=DMS Application#11.1.1.1.0, contextPath=/dms, uri=/">
    <Jul 9, 2013 7:33:47 PM CDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ACCOUNTRECONCILIATION [Version=11.1.2.0]' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.soa.workflow.wc, exact-match: false]..
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.soa.workflow.wc, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
    Truncated. see log file for complete stacktrace
    >
    <Jul 9, 2013 7:34:12 PM CDT> <Warning> <EJB> <BEA-010001> <While deploying EJB 'RuleService_AsyncRequestProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncRequestProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
    <Jul 9, 2013 7:34:12 PM CDT> <Warning> <EJB> <BEA-010001> <While deploying EJB 'RuleService_AsyncResponseProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncResponseProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
    <Jul 9, 2013 7:34:13 PM CDT> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\Oracle\Middleware\EPMSystem11R1\products\Essbase\aps\AppServer\InstallableApps\Common\aps.ear/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Jul 9, 2013 7:34:13 PM CDT> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\tmp\servers\EPMServer0\tmp\_WL_user\APS_11.1.2.0\mizf54/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Jul 9, 2013 7:35:15 PM CDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'FINANCIALCLOSE [Version=11.1.2.0]' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.soa.workflow.wc, exact-match: false]..
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: oracle.soa.workflow.wc, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
    Truncated. see log file for complete stacktrace
    >
    <Jul 9, 2013 7:35:44 PM CDT> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: com/oracle/adfm, Specification-Version: 1, referenced from: C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\tmp\servers\EPMServer0\tmp\_WL_user\FMADFWEB_11.1.2.0\nw1g9o]. Make sure the referenced optional package has been deployed as a library.>
    <Jul 9, 2013 7:35:49 PM CDT> <Warning> <EJB> <BEA-010001> <While deploying EJB 'ActionsService_AsyncRequestProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncRequestProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
    <Jul 9, 2013 7:35:49 PM CDT> <Warning> <EJB> <BEA-010001> <While deploying EJB 'ActionsService_AsyncResponseProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncResponseProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
    <Jul 9, 2013 7:36:57 PM CDT> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element web-app in the deployment descriptor in C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\tmp\servers\EPMServer0\tmp\_WL_user\SHAREDSERVICES_11.1.2.0\dt7o9d\interop.war/WEB-INF/web.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Jul 9, 2013 7:38:12 PM CDT> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\Oracle\Middleware\odi\setup\manual\oracledi-agent\oraclediagent.ear/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Jul 9, 2013 7:38:12 PM CDT> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\tmp\servers\EPMServer0\tmp\_WL_user\oraclediagent\cn250y/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
    <Jul 9, 2013 7:38:12 PM CDT> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.bam.odi.library, Specification-Version: 11.1.1, referenced from: C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EPMServer0\tmp\servers\EPMServer0\tmp\_WL_user\oraclediagent\cn250y]. Make sure the referenced optional package has been deployed as a library.>
    <Jul 9, 2013 7:38:13 PM CDT> <Emergency> <Deployer> <BEA-149259> <Server 'EPMServer0' in cluster 'EPMServer' is being brought up in administration state due to failed deployments.>
    Hyperion Provider Services - Release 11.1.2.3.4408
    Copyright (c) 1991, 2013 Oracle and / or its affiliates. All rights reserved.
    connection mode : HTTP
    essbase.properties: C:\Oracle\Middleware\EPMSystem11R1/common/EssbaseJavaAPI/11.1.2.0/bin/essbase.properties
    java System properties -DESS_ES_HOME: C:\Oracle\Middleware\EPMSystem11R1/common/EssbaseJavaAPI/11.1.2.0
    Mode: Non Fusion read from Registry
    registry.isRegistryDatabaseCreated()true
    Registry was initialized sucessfully
    Component was found from component type DISC_MAN_PRODUCT
    Updating version Disclosure_dbVersion with DISC_MAN_PRODUCT
    Warning: Starting ADF Library jar post-deployment on WebLogic Server. Is "provider-lazy-inited" init-param missing from LibraryFilter? Ignore this warning if the ADFJspResourceProvider is not being used.
    Started: ADF Library non-ADFJspResourceProvider post-deployment
    Finished: ADF Library non-ADFJspResourceProvider post-deployment (millis): 46
    Essbase® Administration Services - Version  11.1.2.3.000.4415
    Copyright © 1991, 2013 Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. No portion hereof may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the recipient's personal use, without the express written permission of Oracle.
    US Patent Number 5,359,724
    US Patent Number 6,317,750
    Current time stamp: Tue Jul 09 19:38:54 CDT 2013
    Server started successfully
    Waiting for client requests
    HRContextListener::contextInitialized
    Warning: Starting ADF Library jar post-deployment on WebLogic Server. Is "provider-lazy-inited" init-param missing from LibraryFilter? Ignore this warning if the ADFJspResourceProvider is not being used.
    Started: ADF Library non-ADFJspResourceProvider post-deployment
    Finished: ADF Library non-ADFJspResourceProvider post-deployment (millis): 203
    - WEBLOGIC
    null
    - The AMHM configuration file path is..nullconf
    -  getting attributes for bsp.jsr: [Migration, Ant-Version, Manifest-Version, Created-By, Version]
    -  going to get value for Migration attribute
    -  Encryption Type : AES
    - Invocation of generateSecurityFile Successful
    - userName :
    - ServiceID :
    - applicationName :
    - Configuration File (config.xml) does not exist under C:\Oracle\Middleware\user_projects\epmsystem1\Planning\planning1\config.xml Process aborted.
    - Migration Failed
    Utf8Filter: forceRequestCharacterEncoding set to true (init-param=true)
    Utf8Filter: repairRequestParameters set to false (init-param=false)
    Utf8Filter: rebuildPathInfo set to false (init-param=false)
    Utf8Filter: revertRequestURI set to true (init-param=true)
    Utf8Filter: settings are true/false/false/true
    Initializing CORBA ORB.
    CORBA ORB initialization complete.
    Loading configuration from registry
    WSBaseServlet.setDefaultGSMContext(): Servlet GSM context. host=192.168.204.1:6800
    Log configuration: file:/C:/Oracle/Middleware/user_projects/epmsystem1/ReportingAnalysis/RAFrameworkWebapp/WEB-INF/logging.properties
    <Jul 9, 2013 7:39:39 PM CDT> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
    <Jul 9, 2013 7:39:39 PM CDT> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of EPMServer.>
    <Jul 9, 2013 7:39:44 PM CDT> <Warning> <Log Management> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[7]" is now listening on fe80:0:0:0:0:5efe:c0a8:ed01:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[9]" is now listening on fe80:0:0:0:0:100:7f:fffe:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[13]" is now listening on 0:0:0:0:0:0:0:1:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on fe80:0:0:0:0:5efe:c0a8:cc01:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[5]" is now listening on fe80:0:0:0:0:5efe:c0a8:7:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[12]" is now listening on 127.0.0.1:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[8]" is now listening on fe80:0:0:0:3415:3499:e650:c29e:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[10]" is now listening on fe80:0:0:0:2d02:d309:55d5:a150:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[11]" is now listening on fe80:0:0:0:5894:d88c:c022:f32b:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 192.168.204.1:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 192.168.0.7:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[6]" is now listening on fe80:0:0:0:c885:cffb:be7a:3e0b:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on fe80:0:0:0:1d4d:5292:d06b:f62b:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.237.1:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jul 9, 2013 7:40:09 PM CDT> <Notice> <WebLogicServer> <BEA-000358> <Started WebLogic Independent Managed Server "EPMServer0" for domain "EPMSystem" running in Production Mode>
    <Jul 9, 2013 7:40:09 PM CDT> <Warning> <Server> <BEA-002611> <Hostname "SUBHASUBBU", maps to multiple IP addresses: 192.168.204.1, 192.168.237.1, 192.168.0.7, fe80:0:0:0:c885:cffb:be7a:3e0b%18, fe80:0:0:0:1d4d:5292:d06b:f62b%20, fe80:0:0:0:3415:3499:e650:c29e%15>
    <Jul 9, 2013 7:40:09 PM CDT> <Warning> <JMX> <BEA-149510> <Unable to establish JMX Connectivity with the Adminstration Server AdminServer at <JMXServiceURL:null>.>
    <Jul 9, 2013 7:40:11 PM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Jul 9, 2013 7:40:11 PM CDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in ADMIN mode>
    <Jul 9, 2013 8:11:16 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM HSS_COMPONENT_TYPES WHERE 1 = 0" set up for pool "EPMSystemRegistry" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:11:16 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM V8_VERSION WHERE 1 = 0" set up for pool "raframework_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:11:54 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on fe80:0:0:0:c885:cffb:be7a:3e0b:54,190 during the configured idle timeout of 5 secs>
    <Jul 9, 2013 8:12:04 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on fe80:0:0:0:c885:cffb:be7a:3e0b:54,198 during the configured idle timeout of 5 secs>
    <Jul 9, 2013 8:12:19 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 0:0:0:0:0:0:0:1:54,216 during the configured idle timeout of 5 secs>
    <Jul 9, 2013 8:12:41 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM HSS_COMPONENT_TYPES WHERE 1 = 0" set up for pool "EPMSystemRegistry" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:41 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM ARM_ATTRIBUTES WHERE 1 = 0" set up for pool "accountreconciliation_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:41 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM AIF_LOOKUP_MAPPINGS WHERE 1 = 0" set up for pool "aif_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:41 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM CALCMGRCONFIG WHERE 1 = 0" set up for pool "calc_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:41 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM DISCMAN_COUNTER WHERE 1 = 0" set up for pool "discman_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:46 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM SERVERLOGID WHERE 1 = 0" set up for pool "eas_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:46 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM FCC_USER_ATTRIBUTES WHERE 1 = 0" set up for pool "financialclose_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:46 PM CDT> <Error> <JDBC> <BEA-001112> <Test "select count(*) from SNP_LOC_REP" set up for pool "odiMasterRepository" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:46 PM CDT> <Error> <JDBC> <BEA-001112> <Test "select count(*) from SNP_LOC_REP" set up for pool "odiMasterRepository" failed with exception: "java.sql.SQLException: [FMWGEN][SQLServer JDBC Driver]Object has been closed.".>
    <Jul 9, 2013 8:12:46 PM CDT> <Error> <JDBC> <BEA-001112> <Test "select count(*) from SNP_LOC_REPW" set up for pool "odiWorkRepository" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:46 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM HSPSYS_CLUSTER WHERE 1 = 0" set up for pool "planning_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:12:46 PM CDT> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM HPM_APPLICATION WHERE 1 = 0" set up for pool "profitability_datasource" failed with exception: "java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]socket write error: Connection reset by peer.".>
    <Jul 9, 2013 8:18:49 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on fe80:0:0:0:c885:cffb:be7a:3e0b:54,579 during the configured idle timeout of 5 secs>
    <Jul 9, 2013 8:22:29 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on fe80:0:0:0:c885:cffb:be7a:3e0b:54,820 during the configured idle timeout of 5 secs>
    <Jul 9, 2013 8:29:44 PM CDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on fe80:0:0:0:c885:cffb:be7a:3e0b:55,178 during the configured idle timeout of 5 secs>

    First of all "I installed 11.1.2.3 in windows 7 ultimate OS", it is not a supported OS so if you want assistance problem solving you should stick with a supported OS.
    It also looks like you have installed a whole range of products some requiring additional configuration and the requirement of SOA.
    I recommend starting with a support OS and only install products that are required.
    Cheers
    John
    http://john-goodwin.blogspot.com/

Maybe you are looking for