Incoming EDI payment advise - open item not found

Hello,
I introduced the process of incoming EDI payment advise but with manual posting by using transaction F-28. Some positions in the EDI PA could
not be assign to an open item. I have a total amount, cash discount and net amount in the position listed. The system posts AKonto the net amount. What I want to do is to post total amount and to adapt the total cash discount.
For example:
total amount = 100 €
cash discount = 20 €
net amount = 80 €
The posting is actual as a difference to the debitor account with value 80 €. What I would like to have is the possibility to decide that the item is
posted as a difference to the debitor account but with value 100 €. 20 € cash discount should be visible in area "not assigned".
I found User exit EXIT_SAPLIEDP_102 table AVIP parameter "activate cash discount" but it seems that this one has no influence to our needs. Does anybody know if there is any other option to change the system behaviour?
Thanks so much!

check the posting date of the invoice and payment.
You can enter more, go to edit, select more.
Has one of the entries got a special GL entry.
Lastly if all else fails, on the selection screen enter both document numbers.
If only one appears, make sure it has not been cleared already.

Similar Messages

  • Open item not found while doing process open items - F-32

    The customer account shows 2 open items ( 1 Invoice and 1 Payment documents) during account clearing with f-32 t.code, only payment document is appearing. whether reason code maintained in invoice document any way afftects in account clearing process.

    check the posting date of the invoice and payment.
    You can enter more, go to edit, select more.
    Has one of the entries got a special GL entry.
    Lastly if all else fails, on the selection screen enter both document numbers.
    If only one appears, make sure it has not been cleared already.

  • When using program RFDM3000/Automatic creation of dispute cases what is the difference with the option of Automatic incoming payment and Open items?

    We currently have a batch jobs running for each, automatic incoming payment and open items.  This was set up in the past and we are trying to determine what the difference is for each of these functions?  Do you need to have the automatic incoming run prior to the open items for residuals and payments on accounts?

    Hi Chris,
    Program RFDM3000 creates dispute cases for residual items arising during automatic incoming payments (account statement, lockbox), during check presentation, or in postprocessing.
    Alternatively, you can use the program to create dispute cases for open receivables items. You can use the selection criteria to restrict the quantity of open items (for example, using the document type and posting key for residual items from incoming payment postings).
    You will find more information in the link below
    http://help.sap.com/saphelp_erp2004/helpdata/en/0b/e07340b0c6980ae10000000a155106/content.htm
    Regards,
    Jose

  • Open item management_part payment with partial clearing_post outgoing payment process open items

    In this scenario of post outgoing payment process open items , i' m facing a error titled as below
    The difference is too large for clearing
    Message no. F5263
    Diagnosis
    A non-assigned difference exists for the specified clearing amount.
    The difference for an automatic difference posting must not be greater than the difference permitted for the user, nor greater than the difference permitted for the tolerance group that is contained in the customer/vendor master record.
    System Response
    It is not possible to automatically charge off the difference.
    Procedure
    You can charge off the difference manually using the function "Clear differences". You define the upper limits for automatically clearing differences in the tolerance group assigned to the user.
    Change tolerance groups for user
    I gave the specifications in (OBA4 screen) i.e., change tolerance groups for users/employees are as follows
      Amount per document : 9999999999
    Amount per open item account item : 9999999999
    Cash discount per line item : 10%
    Permitted payment differences left blank
      What else do i need to execute ?
    Please aid me in resolving the error....
    Thanks in advance,
    Heamanthkkumar.

    Hi,
    it seems you want to make a partial payment of 15000, select the line item against which you want to make the payment. On the payment amount field put -15000 and then simulate. It will credit the bank account and debit you expense account. Pls refer the screen shot.
    best regds
    Subha

  • Post with clearing: FB05  No open items were found

    Hi,
    I am using FB05 (have selected 'transfer posting with clearing) to clear the vendor open items and post to a GL account, but I encounter the message 'No open items were found' (Msg F5 170) eventhough the vendor has open  items and morever it is not blocked.
    Any reason why this error.
    Tks,
    SS

    There can be any number of reasons why a standard transaction does not pick up open items for your vendor account. Some possible reasons are:
    - outside date range, if you are giving a date range
    - they might be special g/l transactions, not normal line items
    - they migh not be open line items, but noted items
    - the items might not be open anymore when FB05 is being run
    Do a little more investigation into your system - we can only give suggestions from here.
    Regards
    Gulshan

  • No Open Items were found

    Hi
    I am trying to clear open items using F-44
    I am getting an error "No Open Items were found" .
    But when i go and see in FBL1N , I can see the open items there.
    What can be the reason ?
    PS: The posting date of the items is in 2005. Is this causes any problem?
    Thax. for your help.
    -erpMAN-

    The most common reason is that the invoice is in a payment run.
    try to run a f.80 on the invoice in question ( in test mode) to see if you can reverse it.
    If you cant more than likely it will be in a payment run.
    Have a look in the payment run tables to confirm this. REGUH & P
    Are you sure the document is an open item? Is it in BSIK or BSAK?
    Hope this helps.

  • Combine Down Payment Request and Payment of Open Item

    I am paying $ 1000 to a vendor to cover $ 300 down payment request and $ 700 for an open invoice. Is it possible to make one payment transaction to cover “down payment request” and “payment of open item”? I want only one amount to appear in the bank ledger account. Thank you, Pravin

    Hi
    In payment program configuration under the payment method configuration for your company codes, make sure that under grouping of items, the  two radio buttons are not selected. This should combine the two items into one payment document. Screen shot attached
    regards
    Sanil Bhandari

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

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

  • Standard Report for Payment Proposal:Open Items

    Hi all
    Is there any standard report for to display Payment Proposal:Open Items?
    I know we can see them in F110 but I am wondering if there's other related report.
    Thanks in advance.
    az

    Hi,
    Check following report. it may help you
    S_P99_41000099 - Payment List
    Regards,
    Jigar

  • 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

  • Change the default 'Item not found' Page

    Anyone know how to change the standard 'Item not found' in KM? I would like to change it to something a bit less technical. I am assuming that it is stored in the repository somewhere.. but where?

    No,
    it's currently not possible to change that page.
    Best regards, Julian

  • 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

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

Maybe you are looking for

  • [solved] resizing PuTTY window while running nano is messed up

    If I'm using PuTTY (Windows SSH client / terminal emulator) and nano running on Arch Linux, window resizing is completely broken. On Debian it is fine however. I went to see if they used any patches, but they don't, none related to terminal resizing

  • Setting up a local ftp server for wireless photo transfers

    I am a semi-professional photographer who recently purchased a wireless unit that connects to my camera to transfer my images to my Mac. I have turned on the ftp services under Sharing on my Powermac G5 and set up a user account for the camera to log

  • Rolling back the creation of a split partition on a table

    Hi, I had some partitions created on a materialized view . I then split the last partition called FINAL into mulitiple other partitions. Now how can i drop the created split partitions without dropping FINAL. I am using Oracle 10g.

  • Which is better for my needs?

    Hi there. I was wondering which is better for my needs? I'm not very familiar on all of this, so any info will help. I play a lot of games like World of Warcraft, and I do some video editing, + other practical things. I'm debating over to get the 8 G

  • Multiple Hierarchies in Dimension

    Hi All, I have a scenario, where I need to design a dimension with multiple hierarchies, is there a best practice on this ? I have about 6 hierarchy in one dimension. Could any share some idea and thoughts. Thasnks Zan