Problem when Generating a PDF , from a SPOOL

Hi,
I'm using the Standard report RSTXPDFT4 to generate data from a spool to a .pdf file.
When the program runs online the data is generated correctly, but, when the data has more then 99 pages, it runs in background, give me the return that the PDF was produced correctly but i can't find where.
I used the path C:\file.pdf but since the server is UNIX, it has got none "C:" Directory.
Then i tried to use /usr/sap/trans/tmp , but the program don't find this path.
Does anyone know how to solve this problem?
Thanks and regards.

see ...
go to your desktop   <b>create  one  pdf  file   empty    see  rightclick the file  and see  the properties of the file  ... there the path of the  file</b>  will be there  ..  copy and paste it in the   RSTXPDFT4   file path .
just  give the file   path as your desktop   and   do  background   ... so that the spool will be downloaded into your   desktop with  the file  name
i think  problem is  the file  path  ..... see the  properties of the files in your  desktop
Girish

Similar Messages

  • Have problem when generate Web Service from bapi function

    Dear all,
    Please kindly help me about generating Web Service from BAPI function, It does not success only this attached function.
    I have done so many function without any problems.
    I found 1 case that I use specific variable to be an import/ export then, it can't create as well.
    As for this one, I try so many changes but I can't success it as well.
    This is my function on R/3 4.6C, Dot net connector 2.0, Dot net Frame Work 1.1.
    FUNCTION Z_BAPI_ATTACHMENT_CREATE.
    ""Local interface: Type: Remote-enabled module
    *"  IMPORTING
    *"     VALUE(P_BOTYPE) LIKE  BORIDENT-OBJTYPE
    *"     VALUE(P_BO_ID) LIKE  BORIDENT-OBJKEY
    *"     VALUE(P_MSGTYP) LIKE  SOFM-DOCTP
    *"     VALUE(P_DOCTY) LIKE  BORIDENT-OBJTYPE
    *"     VALUE(P_RELTYP) LIKE  BRELTYP-RELTYPE
    *"     VALUE(P_FNAME) LIKE  RLGRAP-FILENAME
    *"     VALUE(P_OBJDES) TYPE  SO_OBJ_DES
    *"  EXPORTING
    *"     VALUE(RETURNMESSAGE) TYPE  CHAR50
    INCLUDE : <cntn01>.
    P_BOTYPE  TYPE  BORIDENT-OBJTYPE DEFAULT 'BUS2105'
    P_BO_ID   TYPE  BORIDENT-OBJKEY
    P_MSGTYPE TYPE  SOFM-DOCTP DEFAULT 'URL'
    P_DOCTY   TYPE  BORIDENT-OBJTYPE DEFAULT 'MESSAGE'
    P_RELTYP  TYPE  BRELTYP-RELTYPE DEFAULT 'ATTA'
    P_FNAME   TYPE  RLGRAP-FILENAME
    P_OBJDES  TYPE  SO_OBJ_DES
    TYPES: BEGIN OF ty_message_key,
    foltp TYPE so_fol_tp,
    folyr TYPE so_fol_yr,
    folno TYPE so_fol_no,
    doctp TYPE so_doc_tp,
    docyr TYPE so_doc_yr,
    docno TYPE so_doc_no,
    fortp TYPE so_for_tp,
    foryr TYPE so_for_yr,
    forno TYPE so_for_no,
    END OF ty_message_key.
    DATA : lv_message_key TYPE ty_message_key.
    DATA : lo_message TYPE swc_object.
    DATA : lt_doc_content TYPE STANDARD TABLE OF soli-line
    WITH HEADER LINE.
    First derive the Attachment's ( MESSAGE )document type.
    p_docty = 'MESSAGE'.
    CASE p_reltyp.
    In case of URls
      WHEN 'URL'.
        p_msgtyp = 'URL'.
    In case of Notes / Private Notes
      WHEN 'NOTE' OR 'PNOT'.
        p_msgtyp = 'RAW'.
      WHEN 'ATTA'.
    Take given parameter e.g. 'DOC', 'PDF' etc.
    P_MSGTYP = 'EXT'.
      WHEN OTHERS.
    ....exit
        EXIT.
    ENDCASE.
    Create an initial instance of BO 'MESSAGE' - to call the
    instance-independent method 'Create'.
    swc_create_object lo_message 'MESSAGE' lv_message_key.
    define container to pass the parameter values to the method call
    in next step.
    swc_container lt_message_container.
    Populate container with parameters for method
    swc_set_element lt_message_container 'DOCUMENTTITLE' p_objdes.
    swc_set_element lt_message_container 'DOCUMENTLANGU' 'E'.
    swc_set_element lt_message_container 'NO_DIALOG' 'X'.
    swc_set_element lt_message_container 'DOCUMENTNAME' p_docty.
    swc_set_element lt_message_container 'DOCUMENTTYPE' p_msgtyp.
    In case of URLs..it should be concatenated with &KEY& in the begining.
    CASE p_msgtyp.
      WHEN 'URL'.
      lt_doc_content = '&KEY&http://www.rmtiwari.com' .
        CONCATENATE '&KEY&' p_fname INTO lt_doc_content.
        APPEND lt_doc_content.
    In case of Notes or Private Notes, get the data from files on appl
    server or from wherever(? - remember background).
      WHEN 'RAW'.
        lt_doc_content = p_fname.
        APPEND lt_doc_content.
    In case of PC File attachments
      WHEN OTHERS.
        OPEN DATASET p_fname FOR INPUT IN BINARY MODE.
        IF sy-subrc EQ 0.
          DO.
            READ DATASET p_fname INTO lt_doc_content.           "2 of 27
            IF sy-subrc EQ 0.
              APPEND lt_doc_content.
            ELSE.
              EXIT.
            ENDIF.
          ENDDO.
          CLOSE DATASET p_fname.
        ENDIF.
    ENDCASE.
    'DocumentContent' is a multi-line element ( itab ).
    swc_set_table lt_message_container 'DocumentContent' lt_doc_content.
    Size is required in case of File attachments
    DATA : lv_doc_size TYPE i.
    DATA : l_file_lines TYPE i.
    DESCRIBE TABLE lt_doc_content LINES l_file_lines.
    READ TABLE lt_doc_content INDEX l_file_lines.
    lv_doc_size = ( 255 * ( l_file_lines - 1 ) ) +
    STRLEN( lt_doc_content ).
    swc_set_element lt_message_container 'DOCUMENTSIZE' lv_doc_size .
    Refresh to get the reference of create 'MESSAGE' object for attachment
    swc_refresh_object lo_message.
    swc_call_method lo_message 'CREATE' lt_message_container.
    Get Key of new object
    swc_get_object_key lo_message lv_message_key.
    Now we have attachment as a business object instance. We can now
    attach it to our main business object instance.
    Create main BO object_a
    data: LO_IS_OBJECT_A type SIBFLPORB. "type SIBFLPORB is unknown, so I
    DATA: lo_is_object_a TYPE borident.
    lo_is_object_a-objkey = p_bo_id.
    lo_is_object_a-objtype = p_botype.
    LO_IS_OBJECT_A-CATID = 'BO'.
    Create attachment BO object_b
    data: LO_IS_OBJECT_B type SIBFLPORB. "type SIBFLPORB is unknown
    DATA: lo_is_object_b TYPE borident.
    lo_is_object_b-objkey = lv_message_key.
    lo_is_object_b-objtype = p_docty.
    LO_IS_OBJECT_B-CATID = 'BO'.
    *TRY.
    *CALL METHOD CL_BINARY_RELATION=&gtCREATE_LINK
    EXPORTING
    IS_OBJECT_A = LO_IS_OBJECT_A
    IS_OBJECT_B = LO_IS_OBJECT_B
    IP_RELTYPE = P_RELTYP.
    CALL FUNCTION 'BINARY_RELATION_CREATE'
      EXPORTING
        obj_rolea    = lo_is_object_a
        obj_roleb    = lo_is_object_b
        relationtype = p_reltyp
      EXCEPTIONS
        OTHERS       = 1.
    Check if everything OK...who cares!!
    COMMIT WORK.
    if sy-subrc = 0.
      RETURNMESSAGE = 'S-Success'.
    else.
      RETURNMESSAGE = 'E-Error'.
    endif.
    ENDFUNCTION.
    Thanks in advance,
    Benjawan
    Edited by: Nitipat Chadchavalpanichaya on Oct 20, 2008 9:02 AM

    There is no any error message show up. It just the class
    Z_BAPI_ATTACHMENT_CREATE  doesn't create autometically as normal. I showed you as below.
    That means I can't call class z_bapi_attachment_create.
    ' <autogenerated>
    '     This code was generated by a SAP. NET Connector Proxy Generator Version 2.0
    '     Created at 21/10/2551
    '     Created from Windows
    '     Changes to this file may cause incorrect behavior and will be lost if
    '     the code is regenerated.
    ' </autogenerated>
    Imports System
    Imports System.Text
    Imports System.Collections
    Imports System.ComponentModel
    Imports System.Runtime.InteropServices
    Imports System.Xml.Serialization
    Imports System.Web.Services
    Imports System.Web.Services.Description
    Imports System.Web.Services.Protocols
    Imports SAP.Connector
      '@ <summary>
      '@ Client SAP proxy class
      '@ </summary>
      <WebServiceBinding(Name:="dummy.Binding", Namespace:="urn:sap-com:document:sap:rfc:functions")> _
      Public Class PRAttachment
        Inherits SAPClient
        '@ <summary>
        '@ Initializes a new PRAttachment.
        '@ </summary>
        Public Sub New()
        End Sub
        '@ <summary>
        '@ Initializes a new PRAttachment with a new connection based on the specified connection string.
        '@ </summary>
        '@ <param name="connectionString">A connection string (e.g. RFC or URL) specifying the system where the proxy should connect to.</param>
        Public Sub New(ByVal ConnectionString As String)
          MyBase.New(ConnectionString)
        End Sub
        '@ <summary>
        '@ Initializes a new PRAttachment and adds it to the given container.
        '@ This allows automated connection mananged by VS component designer:
        '@ If container is disposed, it will also dispose this SAPClient instance,
        '@ which will dispose a contained connection if needed.
        '@ </summary>
        '@ <param name="Cont">The container where the new SAPClient instance is to be added.</param>
        Public Sub New(ByVal Cont As Container)
          MyBase.New(Cont)
        End Sub
      End Class

  • How do I prevent Acrobat from encoding # in hyperlinks to %23 when generating a PDF from Word 2010?

    Existing posts seem to indicate that the only solution is to manually modify each hyperlink in the generated PDF. This is a tedious and time-consuming process that I would like to avoid at any cost. Is there an alternative?
    Joe

    It is relative, but I don't want it to be. The problem is that I don't see any way in either Acrobat or InDesign to specify that it must be absolute.
    It sounds like if I were to keep my working file on a local drive and export from there, it would automatically create an absolute link to the network path, but another designer is also working on the project and needs to be able to access the file. I could also copy the entire working folder to a local drive before exporting each time, or manually update the links in Acrobat from a local copy of the PDF after each export... but these both seem like ridiculous extra steps that shouldn't be necessary.
    Is it really possible that neither program allows the user to control whether a link is relative or absolute? Should I post this in the InDesign forums, though the issue seems to be in Acrobat?

  • JDev 10g: Problem when generating database objects from UML diagram

    Hi,
    I have noticed following problem.
    I made some business components through UML diagrammer in 9.0.3. From the diagram I generated database objects. It worked fine.
    When I doing the same thing in 10g, the generation fails on several tables with the message that the "identifier is too long".
    Looking at the SQL produced in one of the failing tables. In 9.0.3 following is produced:
    create table sfs_document_def (
    id number constraint document_definition_id_check not null,
    caption varchar2(100) constraint document_definition_caption_ch not null,
    index1 number,
    owner_type number constraint document_definition_owner_type not null
    alter table sfs_document_def add (constraint documentdefinition_primary_key primary key (id));
    And in 10g following is produced:
    create table sfs_document_def (
    id number,
    caption varchar2(100) constraint sfs_document_def_caption_check not null,
    index1 number,
    owner_type number constraint sfs_document_def_owner_type_ch not null
    alter table sfs_document_def add ( constraint documentdefinition_primary_key primary key (id));
    alter table sfs_document_def add ( constraint document_definition_id_check check ("id" is not null));
    alter table sfs_document_def add ( constraint sfs_document_def_caption_check_10 check ("caption" is not null));
    alter table sfs_document_def add ( constraint sfs_document_def_owner_type_ch_10 check ("owner_type" is not null));
    It seems that column that are set not to be null in 10 g first get a constraint creating the table and then when altering the table. Furthermore, notice that the name of the second constraint is longer than 30 chars, which is reason to the error when creating the tables.

    Thanks for reporting the issue. I have managed to reproduce your problem and logged a bug to get the problem fixed.
    Thanks,
    Lisa Sherriff
    JDev QA

  • Problem in generating a PDF From XSTRING From RFC

    Hi All,
    I have done the ADS Configuration successfully.
    When I try to create empty interactive using one text field, and deployed it, the application displays the PDF form. Now I want to display a PDF report, for this I am calling a RFC which returns a file in the format of XSTRING. How can I convert the XSTRING into PDF form in webdynpro.
    If anyone have done this scenario, can guide me what are all the steps to be followed and can give me some sample codings to convert the XSTRING to the Form supported by PDF.
    Thanks
    Ponnusamy P

    Hi sumit,
        Here is my server log:
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[./log/defaultTrace.trc]/>
    <!PATTERN[defaultTrace.trc]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[ASCII]/>
    <!FILESET[11, 20, 10485760]/>
    <!PREVIOUSFILE[defaultTrace.10.trc]/>
    <!NEXTFILE[defaultTrace.12.trc]/>
    <!LOGHEADER[END]/>
    #1.5#00144F3E9F4B005A000000030000124100043F954B6C0EBB#1195810354891#com.sap.engine.services.prtbridge#sap.com/irj#com.sap.engine.services.prtbridge#Guest#0####05b79de099a711dcaaad00144f3e9f4b#Thread[com.sap.pcd.gl.xfs.LocalNotificationThread,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server#Java###An Error has been occured during PRTBridge operation
    [EXCEPTION]
    #1#com.sap.engine.frame.cluster.message.NoListenerOnDestinationException: There is no listener registered on the destination 12,751,750 for service "prtbridge".
         at com.sap.engine.core.cluster.impl6.ms.MSEventListener.isServiceRunning(MSEventListener.java:392)
         at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.sendMessage(MSConnectionImpl.java:146)
         at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendMessage(ClusterManagerImpl.java:2382)
         at com.sap.engine.core.service630.context.cluster.message.MessageContextImpl.send(MessageContextImpl.java:85)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:138)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:169)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.broadCastMessage(PRTBridgeCommunicationManager.java:305)
         at com.sap.portal.prt.sapj2ee.core.clustercommunication.MessageContextWrapper.broadCastMessage(MessageContextWrapper.java:252)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.publish(NotificationSAPJ2EE630.java:683)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.publish(NotificationServiceDispatcher.java:160)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.handleMsgContainer(SynchronousNotificationCommunication.java:134)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.createNotification(SynchronousNotificationCommunication.java:183)
         at com.sapportals.portal.softcache.SoftCaches.createNotification(SoftCaches.java:310)
         at com.sapportals.portal.softcache.SoftCache.createNotification(SoftCache.java:579)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.notifyCrossServer(XfsNotificationEngine.java:789)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.sendNotifications(XfsNotificationEngine.java:813)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.updateAllCachedObjects(XfsNotificationEngine.java:723)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.run(XfsNotificationEngine.java:220)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#00144F3E9F4B0058000003710000124100043F954BD445BC#1195810361722#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003720000124100043F954BD4465A#1195810361722#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = UWL_PUSH_ITEMS; name application = UniversalWorklistService#
    #1.5#00144F3E9F4B005A000000050000124100043F954C6F7792#1195810371891#com.sap.engine.services.prtbridge#sap.com/irj#com.sap.engine.services.prtbridge#Guest#0####05b79de099a711dcaaad00144f3e9f4b#Thread[com.sap.pcd.gl.xfs.LocalNotificationThread,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server#Java###An Error has been occured during PRTBridge operation
    [EXCEPTION]
    #1#com.sap.engine.frame.cluster.message.NoListenerOnDestinationException: There is no listener registered on the destination 12,751,750 for service "prtbridge".
         at com.sap.engine.core.cluster.impl6.ms.MSEventListener.isServiceRunning(MSEventListener.java:392)
         at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.sendMessage(MSConnectionImpl.java:146)
         at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendMessage(ClusterManagerImpl.java:2382)
         at com.sap.engine.core.service630.context.cluster.message.MessageContextImpl.send(MessageContextImpl.java:85)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:138)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:169)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.broadCastMessage(PRTBridgeCommunicationManager.java:305)
         at com.sap.portal.prt.sapj2ee.core.clustercommunication.MessageContextWrapper.broadCastMessage(MessageContextWrapper.java:252)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.publish(NotificationSAPJ2EE630.java:683)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.publish(NotificationServiceDispatcher.java:160)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.handleMsgContainer(SynchronousNotificationCommunication.java:134)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.createNotification(SynchronousNotificationCommunication.java:183)
         at com.sapportals.portal.softcache.SoftCaches.createNotification(SoftCaches.java:310)
         at com.sapportals.portal.softcache.SoftCache.createNotification(SoftCache.java:579)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.notifyCrossServer(XfsNotificationEngine.java:789)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.sendNotifications(XfsNotificationEngine.java:813)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.updateAllCachedObjects(XfsNotificationEngine.java:723)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.run(XfsNotificationEngine.java:220)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#00144F3E9F4B005A000000070000124100043F954C9D6556#1195810374901#com.sap.engine.services.prtbridge#sap.com/irj#com.sap.engine.services.prtbridge#Guest#0####05b79de099a711dcaaad00144f3e9f4b#Thread[com.sap.pcd.gl.xfs.LocalNotificationThread,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server#Java###An Error has been occured during PRTBridge operation
    [EXCEPTION]
    #1#com.sap.engine.frame.cluster.message.NoListenerOnDestinationException: There is no listener registered on the destination 12,751,750 for service "prtbridge".
         at com.sap.engine.core.cluster.impl6.ms.MSEventListener.isServiceRunning(MSEventListener.java:392)
         at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.sendMessage(MSConnectionImpl.java:146)
         at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendMessage(ClusterManagerImpl.java:2382)
         at com.sap.engine.core.service630.context.cluster.message.MessageContextImpl.send(MessageContextImpl.java:85)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:138)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:169)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.broadCastMessage(PRTBridgeCommunicationManager.java:305)
         at com.sap.portal.prt.sapj2ee.core.clustercommunication.MessageContextWrapper.broadCastMessage(MessageContextWrapper.java:252)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.publish(NotificationSAPJ2EE630.java:683)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.publish(NotificationServiceDispatcher.java:160)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.handleMsgContainer(SynchronousNotificationCommunication.java:134)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.createNotification(SynchronousNotificationCommunication.java:183)
         at com.sapportals.portal.softcache.SoftCaches.createNotification(SoftCaches.java:310)
         at com.sapportals.portal.softcache.SoftCache.createNotification(SoftCache.java:579)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.notifyCrossServer(XfsNotificationEngine.java:789)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.sendNotifications(XfsNotificationEngine.java:813)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.updateAllCachedObjects(XfsNotificationEngine.java:723)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.run(XfsNotificationEngine.java:220)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#00144F3E9F4B005A000000090000124100043F954D75ED62#1195810389092#com.sap.engine.services.prtbridge#sap.com/irj#com.sap.engine.services.prtbridge#Guest#0####05b79de099a711dcaaad00144f3e9f4b#Thread[com.sap.pcd.gl.xfs.LocalNotificationThread,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server#Java###An Error has been occured during PRTBridge operation
    [EXCEPTION]
    #1#com.sap.engine.frame.cluster.message.NoListenerOnDestinationException: There is no listener registered on the destination 12,751,750 for service "prtbridge".
         at com.sap.engine.core.cluster.impl6.ms.MSEventListener.isServiceRunning(MSEventListener.java:392)
         at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.sendMessage(MSConnectionImpl.java:146)
         at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendMessage(ClusterManagerImpl.java:2382)
         at com.sap.engine.core.service630.context.cluster.message.MessageContextImpl.send(MessageContextImpl.java:85)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:138)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:169)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.broadCastMessage(PRTBridgeCommunicationManager.java:305)
         at com.sap.portal.prt.sapj2ee.core.clustercommunication.MessageContextWrapper.broadCastMessage(MessageContextWrapper.java:252)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.publish(NotificationSAPJ2EE630.java:683)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.publish(NotificationServiceDispatcher.java:160)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.handleMsgContainer(SynchronousNotificationCommunication.java:134)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.createNotification(SynchronousNotificationCommunication.java:183)
         at com.sapportals.portal.softcache.SoftCaches.createNotification(SoftCaches.java:310)
         at com.sapportals.portal.softcache.SoftCache.createNotification(SoftCache.java:579)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.notifyCrossServer(XfsNotificationEngine.java:789)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.sendNotifications(XfsNotificationEngine.java:813)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.updateAllCachedObjects(XfsNotificationEngine.java:723)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.run(XfsNotificationEngine.java:220)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#00144F3E9F4B00580000039A0000124100043F954DFE9318#1195810398049#com.sap.workflow#sap.com/irj#com.sap.workflow.#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Object not found in lookup of WF_DBPOOL.#
    #1.5#00144F3E9F4B00580000039C0000124100043F954DFE97B5#1195810398050#com.sap.workflow#sap.com/irj#com.sap.workflow.#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Object not found in lookup of SAPF11DB.#
    #1.5#00144F3E9F4B00580000039E0000124100043F954DFEA154#1195810398052#com.sap.workflow#sap.com/irj#com.sap.workflow.#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Error##Plain###Path to object does not exist at java:comp, the whole lookup name is java:comp/env/jdbc/SAP/EP_PRT.#
    #1.5#00144F3E9F4B0058000003AD0000124100043F954E27CA25#1195810400750#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003AE0000124100043F954E27CACB#1195810400750#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSRD_BROADCASTING_KM_RFC; name application = com.sap.ip.bi.broadcasting.broadcasting#
    #1.5#00144F3E9F4B005A0000000B0000124100043F954E3B1289#1195810402012#com.sap.engine.services.prtbridge#sap.com/irj#com.sap.engine.services.prtbridge#Guest#0####05b79de099a711dcaaad00144f3e9f4b#Thread[com.sap.pcd.gl.xfs.LocalNotificationThread,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server#Java###An Error has been occured during PRTBridge operation
    [EXCEPTION]
    #1#com.sap.engine.frame.cluster.message.NoListenerOnDestinationException: There is no listener registered on the destination 12,751,750 for service "prtbridge".
         at com.sap.engine.core.cluster.impl6.ms.MSEventListener.isServiceRunning(MSEventListener.java:392)
         at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.sendMessage(MSConnectionImpl.java:146)
         at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendMessage(ClusterManagerImpl.java:2382)
         at com.sap.engine.core.service630.context.cluster.message.MessageContextImpl.send(MessageContextImpl.java:85)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:138)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:169)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.broadCastMessage(PRTBridgeCommunicationManager.java:305)
         at com.sap.portal.prt.sapj2ee.core.clustercommunication.MessageContextWrapper.broadCastMessage(MessageContextWrapper.java:252)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.publish(NotificationSAPJ2EE630.java:683)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.publish(NotificationServiceDispatcher.java:160)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.handleMsgContainer(SynchronousNotificationCommunication.java:134)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.createNotification(SynchronousNotificationCommunication.java:183)
         at com.sapportals.portal.softcache.SoftCaches.createNotification(SoftCaches.java:310)
         at com.sapportals.portal.softcache.SoftCache.createNotification(SoftCache.java:579)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.notifyCrossServer(XfsNotificationEngine.java:789)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.sendNotifications(XfsNotificationEngine.java:813)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.updateAllCachedObjects(XfsNotificationEngine.java:723)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.run(XfsNotificationEngine.java:220)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#00144F3E9F4B005A0000000D0000124100043F954E6900A2#1195810405022#com.sap.engine.services.prtbridge#sap.com/irj#com.sap.engine.services.prtbridge#Guest#0####05b79de099a711dcaaad00144f3e9f4b#Thread[com.sap.pcd.gl.xfs.LocalNotificationThread,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server#Java###An Error has been occured during PRTBridge operation
    [EXCEPTION]
    #1#com.sap.engine.frame.cluster.message.NoListenerOnDestinationException: There is no listener registered on the destination 12,751,750 for service "prtbridge".
         at com.sap.engine.core.cluster.impl6.ms.MSEventListener.isServiceRunning(MSEventListener.java:392)
         at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.sendMessage(MSConnectionImpl.java:146)
         at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendMessage(ClusterManagerImpl.java:2382)
         at com.sap.engine.core.service630.context.cluster.message.MessageContextImpl.send(MessageContextImpl.java:85)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:138)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:169)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.broadCastMessage(PRTBridgeCommunicationManager.java:305)
         at com.sap.portal.prt.sapj2ee.core.clustercommunication.MessageContextWrapper.broadCastMessage(MessageContextWrapper.java:252)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.publish(NotificationSAPJ2EE630.java:683)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.publish(NotificationServiceDispatcher.java:160)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.handleMsgContainer(SynchronousNotificationCommunication.java:134)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.createNotification(SynchronousNotificationCommunication.java:183)
         at com.sapportals.portal.softcache.SoftCaches.createNotification(SoftCaches.java:310)
         at com.sapportals.portal.softcache.SoftCache.createNotification(SoftCache.java:579)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.notifyCrossServer(XfsNotificationEngine.java:789)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.sendNotifications(XfsNotificationEngine.java:813)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.updateAllCachedObjects(XfsNotificationEngine.java:723)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.run(XfsNotificationEngine.java:220)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#00144F3E9F4B005A0000000F0000124100043F954E6909E6#1195810405025#com.sap.engine.services.prtbridge#sap.com/irj#com.sap.engine.services.prtbridge#Guest#0####05b79de099a711dcaaad00144f3e9f4b#Thread[com.sap.pcd.gl.xfs.LocalNotificationThread,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server#Java###An Error has been occured during PRTBridge operation
    [EXCEPTION]
    #1#com.sap.engine.frame.cluster.message.NoListenerOnDestinationException: There is no listener registered on the destination 12,751,750 for service "prtbridge".
         at com.sap.engine.core.cluster.impl6.ms.MSEventListener.isServiceRunning(MSEventListener.java:392)
         at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.sendMessage(MSConnectionImpl.java:146)
         at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendMessage(ClusterManagerImpl.java:2382)
         at com.sap.engine.core.service630.context.cluster.message.MessageContextImpl.send(MessageContextImpl.java:85)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:138)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:169)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.broadCastMessage(PRTBridgeCommunicationManager.java:305)
         at com.sap.portal.prt.sapj2ee.core.clustercommunication.MessageContextWrapper.broadCastMessage(MessageContextWrapper.java:252)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.publish(NotificationSAPJ2EE630.java:683)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.publish(NotificationServiceDispatcher.java:160)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.handleMsgContainer(SynchronousNotificationCommunication.java:134)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.createNotification(SynchronousNotificationCommunication.java:183)
         at com.sapportals.portal.softcache.SoftCaches.createNotification(SoftCaches.java:310)
         at com.sapportals.portal.softcache.SoftCache.createNotification(SoftCache.java:579)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.notifyCrossServer(XfsNotificationEngine.java:789)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.sendNotifications(XfsNotificationEngine.java:813)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.updateAllCachedObjects(XfsNotificationEngine.java:723)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.run(XfsNotificationEngine.java:220)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#00144F3E9F4B005A000000110000124100043F954E691286#1195810405027#com.sap.engine.services.prtbridge#sap.com/irj#com.sap.engine.services.prtbridge#Guest#0####05b79de099a711dcaaad00144f3e9f4b#Thread[com.sap.pcd.gl.xfs.LocalNotificationThread,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server#Java###An Error has been occured during PRTBridge operation
    [EXCEPTION]
    #1#com.sap.engine.frame.cluster.message.NoListenerOnDestinationException: There is no listener registered on the destination 12,751,750 for service "prtbridge".
         at com.sap.engine.core.cluster.impl6.ms.MSEventListener.isServiceRunning(MSEventListener.java:392)
         at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.sendMessage(MSConnectionImpl.java:146)
         at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendMessage(ClusterManagerImpl.java:2382)
         at com.sap.engine.core.service630.context.cluster.message.MessageContextImpl.send(MessageContextImpl.java:85)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:138)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:169)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.broadCastMessage(PRTBridgeCommunicationManager.java:305)
         at com.sap.portal.prt.sapj2ee.core.clustercommunication.MessageContextWrapper.broadCastMessage(MessageContextWrapper.java:252)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.publish(NotificationSAPJ2EE630.java:683)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.publish(NotificationServiceDispatcher.java:160)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.handleMsgContainer(SynchronousNotificationCommunication.java:134)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.createNotification(SynchronousNotificationCommunication.java:183)
         at com.sapportals.portal.softcache.SoftCaches.createNotification(SoftCaches.java:310)
         at com.sapportals.portal.softcache.SoftCache.createNotification(SoftCache.java:579)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.notifyCrossServer(XfsNotificationEngine.java:789)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.sendNotifications(XfsNotificationEngine.java:813)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.updateAllCachedObjects(XfsNotificationEngine.java:723)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.run(XfsNotificationEngine.java:220)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#00144F3E9F4B005A000000130000124100043F954E691DA8#1195810405029#com.sap.engine.services.prtbridge#sap.com/irj#com.sap.engine.services.prtbridge#Guest#0####05b79de099a711dcaaad00144f3e9f4b#Thread[com.sap.pcd.gl.xfs.LocalNotificationThread,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server#Java###An Error has been occured during PRTBridge operation
    [EXCEPTION]
    #1#com.sap.engine.frame.cluster.message.NoListenerOnDestinationException: There is no listener registered on the destination 12,751,750 for service "prtbridge".
         at com.sap.engine.core.cluster.impl6.ms.MSEventListener.isServiceRunning(MSEventListener.java:392)
         at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.sendMessage(MSConnectionImpl.java:146)
         at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendMessage(ClusterManagerImpl.java:2382)
         at com.sap.engine.core.service630.context.cluster.message.MessageContextImpl.send(MessageContextImpl.java:85)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:138)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:169)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.broadCastMessage(PRTBridgeCommunicationManager.java:305)
         at com.sap.portal.prt.sapj2ee.core.clustercommunication.MessageContextWrapper.broadCastMessage(MessageContextWrapper.java:252)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.publish(NotificationSAPJ2EE630.java:683)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.publish(NotificationServiceDispatcher.java:160)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.handleMsgContainer(SynchronousNotificationCommunication.java:134)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.createNotification(SynchronousNotificationCommunication.java:183)
         at com.sapportals.portal.softcache.SoftCaches.createNotification(SoftCaches.java:310)
         at com.sapportals.portal.softcache.SoftCache.createNotification(SoftCache.java:579)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.notifyCrossServer(XfsNotificationEngine.java:789)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.sendNotifications(XfsNotificationEngine.java:813)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.updateAllCachedObjects(XfsNotificationEngine.java:723)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.run(XfsNotificationEngine.java:220)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#00144F3E9F4B005A000000150000124100043F954E692C7F#1195810405033#com.sap.engine.services.prtbridge#sap.com/irj#com.sap.engine.services.prtbridge#Guest#0####05b79de099a711dcaaad00144f3e9f4b#Thread[com.sap.pcd.gl.xfs.LocalNotificationThread,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server#Java###An Error has been occured during PRTBridge operation
    [EXCEPTION]
    #1#com.sap.engine.frame.cluster.message.NoListenerOnDestinationException: There is no listener registered on the destination 12,751,750 for service "prtbridge".
         at com.sap.engine.core.cluster.impl6.ms.MSEventListener.isServiceRunning(MSEventListener.java:392)
         at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.sendMessage(MSConnectionImpl.java:146)
         at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendMessage(ClusterManagerImpl.java:2382)
         at com.sap.engine.core.service630.context.cluster.message.MessageContextImpl.send(MessageContextImpl.java:85)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:138)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:169)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.broadCastMessage(PRTBridgeCommunicationManager.java:305)
         at com.sap.portal.prt.sapj2ee.core.clustercommunication.MessageContextWrapper.broadCastMessage(MessageContextWrapper.java:252)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.publish(NotificationSAPJ2EE630.java:683)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.publish(NotificationServiceDispatcher.java:160)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.handleMsgContainer(SynchronousNotificationCommunication.java:134)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.createNotification(SynchronousNotificationCommunication.java:183)
         at com.sapportals.portal.softcache.SoftCaches.createNotification(SoftCaches.java:310)
         at com.sapportals.portal.softcache.SoftCache.createNotification(SoftCache.java:579)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.notifyCrossServer(XfsNotificationEngine.java:789)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.sendNotifications(XfsNotificationEngine.java:813)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.updateAllCachedObjects(XfsNotificationEngine.java:723)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.run(XfsNotificationEngine.java:220)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#00144F3E9F4B005A000000170000124100043F954E693536#1195810405036#com.sap.engine.services.prtbridge#sap.com/irj#com.sap.engine.services.prtbridge#Guest#0####05b79de099a711dcaaad00144f3e9f4b#Thread[com.sap.pcd.gl.xfs.LocalNotificationThread,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server#Java###An Error has been occured during PRTBridge operation
    [EXCEPTION]
    #1#com.sap.engine.frame.cluster.message.NoListenerOnDestinationException: There is no listener registered on the destination 12,751,750 for service "prtbridge".
         at com.sap.engine.core.cluster.impl6.ms.MSEventListener.isServiceRunning(MSEventListener.java:392)
         at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.sendMessage(MSConnectionImpl.java:146)
         at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendMessage(ClusterManagerImpl.java:2382)
         at com.sap.engine.core.service630.context.cluster.message.MessageContextImpl.send(MessageContextImpl.java:85)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:138)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:169)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.broadCastMessage(PRTBridgeCommunicationManager.java:305)
         at com.sap.portal.prt.sapj2ee.core.clustercommunication.MessageContextWrapper.broadCastMessage(MessageContextWrapper.java:252)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.publish(NotificationSAPJ2EE630.java:683)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.publish(NotificationServiceDispatcher.java:160)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.handleMsgContainer(SynchronousNotificationCommunication.java:134)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.createNotification(SynchronousNotificationCommunication.java:183)
         at com.sapportals.portal.softcache.SoftCaches.createNotification(SoftCaches.java:310)
         at com.sapportals.portal.softcache.SoftCache.createNotification(SoftCache.java:579)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.notifyCrossServer(XfsNotificationEngine.java:789)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.sendNotifications(XfsNotificationEngine.java:813)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.updateAllCachedObjects(XfsNotificationEngine.java:723)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.run(XfsNotificationEngine.java:220)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#00144F3E9F4B005A000000190000124100043F954E693DD2#1195810405038#com.sap.engine.services.prtbridge#sap.com/irj#com.sap.engine.services.prtbridge#Guest#0####05b79de099a711dcaaad00144f3e9f4b#Thread[com.sap.pcd.gl.xfs.LocalNotificationThread,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server#Java###An Error has been occured during PRTBridge operation
    [EXCEPTION]
    #1#com.sap.engine.frame.cluster.message.NoListenerOnDestinationException: There is no listener registered on the destination 12,751,750 for service "prtbridge".
         at com.sap.engine.core.cluster.impl6.ms.MSEventListener.isServiceRunning(MSEventListener.java:392)
         at com.sap.engine.core.cluster.impl6.ms.MSConnectionImpl.sendMessage(MSConnectionImpl.java:146)
         at com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendMessage(ClusterManagerImpl.java:2382)
         at com.sap.engine.core.service630.context.cluster.message.MessageContextImpl.send(MessageContextImpl.java:85)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:138)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.send(PRTBridgeCommunicationManager.java:169)
         at com.sap.portal.prt.bridge.service.managers.PRTBridgeCommunicationManager.broadCastMessage(PRTBridgeCommunicationManager.java:305)
         at com.sap.portal.prt.sapj2ee.core.clustercommunication.MessageContextWrapper.broadCastMessage(MessageContextWrapper.java:252)
         at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.publish(NotificationSAPJ2EE630.java:683)
         at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.publish(NotificationServiceDispatcher.java:160)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.handleMsgContainer(SynchronousNotificationCommunication.java:134)
         at com.sapportals.portal.softcache.SynchronousNotificationCommunication.createNotification(SynchronousNotificationCommunication.java:183)
         at com.sapportals.portal.softcache.SoftCaches.createNotification(SoftCaches.java:310)
         at com.sapportals.portal.softcache.SoftCache.createNotification(SoftCache.java:579)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.notifyCrossServer(XfsNotificationEngine.java:789)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.sendNotifications(XfsNotificationEngine.java:813)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.updateAllCachedObjects(XfsNotificationEngine.java:723)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.run(XfsNotificationEngine.java:220)
         at java.lang.Thread.run(Thread.java:534)
    #1.5#00144F3E9F4B0058000003B10000124100043F9553F57EE1#1195810498117#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003B20000124100043F9553F57F8D#1195810498117#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSRD_GET_PORTAL_USERS; name application = com.sap.ip.bi.broadcasting.broadcasting_users#
    #1.5#00144F3E9F4B0058000003B40000124100043F9553F59B7C#1195810498124#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003B50000124100043F9553F59C11#1195810498124#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSRD_MAP_TO_PORTAL_USERS; name application = com.sap.ip.bi.broadcasting.broadcasting_users#
    #1.5#00144F3E9F4B0058000003B80000124100043F9553F5C008#1195810498134#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003B90000124100043F9553F5C0B6#1195810498134#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSRD_STORE_ONLINE_LINK; name application = com.sap.ip.bi.broadcasting.online_link#
    #1.5#00144F3E9F4B0058000003BD0000124100043F9553F68A8E#1195810498185#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003BE0000124100043F9553F68B28#1195810498186#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSPOR_NODES_READ; name application = com.sap.ip.bi.portalnavigation.binavigationrfcservice#
    #1.5#00144F3E9F4B0058000003C00000124100043F9553F6A821#1195810498193#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003C10000124100043F9553F6A8B7#1195810498193#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSPOR_NODES_SAVE; name application = com.sap.ip.bi.portalnavigation.binavigationrfcservice#
    #1.5#00144F3E9F4B0058000003C30000124100043F9553F6C51F#1195810498200#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003C40000124100043F9553F6C5B7#1195810498200#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSPOR_PORTAL_CALL; name application = com.sap.ip.bi.portalnavigation.binavigationrfcservice#
    #1.5#00144F3E9F4B0058000003C60000124100043F9553F6E1E8#1195810498208#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003C70000124100043F9553F6E27D#1195810498208#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSPOR_SHORT_TO_URL_CONVERT; name application = com.sap.ip.bi.portalnavigation.binavigationrfcservice#
    #1.5#00144F3E9F4B0058000003C90000124100043F9553F6FEBD#1195810498215#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003CA0000124100043F9553F6FF55#1195810498215#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSPOR_URL_TO_SHORT_CONVERT; name application = com.sap.ip.bi.portalnavigation.binavigationrfcservice#
    #1.5#00144F3E9F4B0058000003CC0000124100043F9553F71BA6#1195810498222#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003CD0000124100043F9553F71C3C#1195810498223#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSRD_FOLDER_WRITABLE; name application = com.sap.ip.bi.portalnavigation.binavigationrfcservice#
    #1.5#00144F3E9F4B0058000003D00000124100043F9553F73F1B#1195810498232#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003D10000124100043F9553F73FB1#1195810498232#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSWR_ABAP_EXCEPTION_TEST; name application = com.sap.ip.bi.portalrfctest.biportalrfctest#
    #1.5#00144F3E9F4B0058000003D30000124100043F9553F75C0B#1195810498239#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003D40000124100043F9553F75CA0#1195810498239#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSWR_LOGGER_CONFIG_GET; name application = com.sap.ip.bi.portalrfctest.biportalrfctest#
    #1.5#00144F3E9F4B0058000003D60000124100043F9553F778EC#1195810498246#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003D70000124100043F9553F77981#1195810498247#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSWR_LOGGER_CONFIG_SET; name application = com.sap.ip.bi.portalrfctest.biportalrfctest#
    #1.5#00144F3E9F4B0058000003D90000124100043F9553F795C9#1195810498254#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003DA0000124100043F9553F7965E#1195810498254#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSWR_RFC_SERVICE_LISTENERS_GET; name application = com.sap.ip.bi.portalrfctest.biportalrfctest#
    #1.5#00144F3E9F4B0058000003DC0000124100043F9553F7B2C0#1195810498261#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003DD0000124100043F9553F7B355#1195810498261#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSWR_RFC_SERVICE_TEST; name application = com.sap.ip.bi.portalrfctest.biportalrfctest#
    #1.5#00144F3E9F4B0058000003DF0000124100043F9553F7CF5B#1195810498269#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003E00000124100043F9553F7CFF0#1195810498269#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSWR_RFC_VERSION_INFO_GET; name application = com.sap.ip.bi.portalrfctest.biportalrfctest#
    #1.5#00144F3E9F4B0058000003E20000124100043F9553F7EC1C#1195810498276#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003E30000124100043F9553F7ECB0#1195810498276#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSWR_TIME_GET; name application = com.sap.ip.bi.portalrfctest.biportalrfctest#
    #1.5#00144F3E9F4B0058000003E60000124100043F9553F80FB2#1195810498285#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003E70000124100043F9553F81052#1195810498285#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSWR_BINARY_CONTENT_GET; name application = com.sap.ip.bi.portalrfctest.filebrowserrfcservice#
    #1.5#00144F3E9F4B0058000003E90000124100043F9553F82E6B#1195810498293#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003EA0000124100043F9553F82F00#1195810498293#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSWR_FOLDER_CONTENT_GET; name application = com.sap.ip.bi.portalrfctest.filebrowserrfcservice#
    #1.5#00144F3E9F4B0058000003EC0000124100043F9553F84C5B#1195810498300#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003ED0000124100043F9553F84CF9#1195810498301#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSWR_ROOT_FOLDER_GET; name application = com.sap.ip.bi.portalrfctest.filebrowserrfcservice#
    #1.5#00144F3E9F4B0058000003EF0000124100043F9553F86A0A#1195810498308#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003F00000124100043F9553F86AA0#1195810498308#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSWR_SAP_ROOT_FOLDER_GET; name application = com.sap.ip.bi.portalrfctest.filebrowserrfcservice#
    #1.5#00144F3E9F4B0058000003F20000124100043F9553F886D3#1195810498315#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003F30000124100043F9553F88768#1195810498316#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSWR_STRING_CONTENT_GET; name application = com.sap.ip.bi.portalrfctest.filebrowserrfcservice#
    #1.5#00144F3E9F4B0058000003F50000124100043F9553F8A365#1195810498323#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003F60000124100043F9553F8A3F8#1195810498323#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSWR_ZIP_STREAM_GET; name application = com.sap.ip.bi.portalrfctest.filebrowserrfcservice#
    #1.5#00144F3E9F4B0058000003F80000124100043F9553F8C0A5#1195810498330#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003F90000124100043F9553F8C139#1195810498330#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = RSWR_CLUSTER_INFO_GET; name application = com.sap.ip.bi.portalrfctest.filebrowserrfcservice#
    #1.5#00144F3E9F4B0058000003FB0000124100043F9553F93261#1195810498359#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000003FC0000124100043F9553F93364#1195810498360#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = SALV_WD_EXPORT_PDF; name application = com.sap.ip.bi.webdynpro.alv.pdf.exportpdfservice#
    #1.5#00144F3E9F4B0058000004010000124100043F95592D3367#1195810585654#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000004020000124100043F95592D340D#1195810585654#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = LSO_COL_GET_ROOMS; name application = com.sap.netweaver.coll.appl.room.rfcadapter.RFCService#
    #1.5#00144F3E9F4B0058000004040000124100043F95592D5080#1195810585661#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000004050000124100043F95592D5115#1195810585661#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = LSO_COL_GET_ROOM_OWNERS; name application = com.sap.netweaver.coll.appl.room.rfcadapter.RFCService#
    #1.5#00144F3E9F4B0058000004070000124100043F95592D6CE1#1195810585668#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000004080000124100043F95592D6D75#1195810585668#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = LSO_COL_GET_ROOM_USERS; name application = com.sap.netweaver.coll.appl.room.rfcadapter.RFCService#
    #1.5#00144F3E9F4B00580000040A0000124100043F95592D8932#1195810585676#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B00580000040B0000124100043F95592D89C6#1195810585676#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = LSO_COL_GET_ROOM_INFO; name application = com.sap.netweaver.coll.appl.room.rfcadapter.RFCService#
    #1.5#00144F3E9F4B00580000040D0000124100043F95592DAB29#1195810585684#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B00580000040E0000124100043F95592DABCB#1195810585684#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = LSO_COL_GET_EXT_ROOMACCESSURL; name application = com.sap.netweaver.coll.appl.room.rfcadapter.RFCService#
    #1.5#00144F3E9F4B0058000004100000124100043F95592DCD8F#1195810585693#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000004110000124100043F95592DCE2A#1195810585693#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = LSO_COL_GET_INT_ROOMACCESSURL; name application = com.sap.netweaver.coll.appl.room.rfcadapter.RFCService#
    #1.5#00144F3E9F4B0058000004130000124100043F95592DEAB7#1195810585701#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000004140000124100043F95592DEB4C#1195810585701#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = LSO_COL_GET_ALL_CATEGORIES; name application = com.sap.netweaver.coll.appl.room.rfcadapter.RFCService#
    #1.5#00144F3E9F4B0058000004160000124100043F95592E06DC#1195810585708#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000004170000124100043F95592E0771#1195810585708#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = LSO_COL_GET_ROOM_PRIVACYTYPES; name application = com.sap.netweaver.coll.appl.room.rfcadapter.RFCService#
    #1.5#00144F3E9F4B0058000004190000124100043F95592E230F#1195810585715#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B00580000041A0000124100043F95592E23A4#1195810585715#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = LSO_COL_GET_TEMPLATES; name application = com.sap.netweaver.coll.appl.room.rfcadapter.RFCService#
    #1.5#00144F3E9F4B00580000041C0000124100043F95592E3F4E#1195810585722#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B00580000041D0000124100043F95592E3FE3#1195810585722#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = LSO_COL_GET_TEMPLATE_INFO; name application = com.sap.netweaver.coll.appl.room.rfcadapter.RFCService#
    #1.5#00144F3E9F4B00580000041F0000124100043F95592E5B36#1195810585729#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000004200000124100043F95592E5D97#1195810585730#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = LSO_COL_CREATE_ROOM; name application = com.sap.netweaver.coll.appl.room.rfcadapter.RFCService#
    #1.5#00144F3E9F4B0058000004220000124100043F95592E793D#1195810585737#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000004230000124100043F95592E79D2#1195810585737#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = LSO_COL_DELETE_ROOM; name application = com.sap.netweaver.coll.appl.room.rfcadapter.RFCService#
    #1.5#00144F3E9F4B0058000004250000124100043F95592E9860#1195810585745#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000004260000124100043F95592E98FF#1195810585745#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = LSO_COL_ADD_USER_TO_ROOM; name application = com.sap.netweaver.coll.appl.room.rfcadapter.RFCService#
    #1.5#00144F3E9F4B0058000004280000124100043F95592EB5DD#1195810585753#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B0058000004290000124100043F95592EB672#1195810585753#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = LSO_COL_REMOVE_USER_FROM_ROOM; name application = com.sap.netweaver.coll.appl.room.rfcadapter.RFCService#
    #1.5#00144F3E9F4B00580000042B0000124100043F95592ED292#1195810585760#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService]: registerToRFCDispatcher Ok#
    #1.5#00144F3E9F4B00580000042C0000124100043F95592ED327#1195810585760#com.sap.portal.RFCLogger#sap.com/irj#com.sap.portal.RFCLogger#Guest#0####eeeec03099a511dc854500144f3e9f4b#SAPEngine_Application_Thread[impl:3]_30##0#0#Info##Plain###[RFCEngineService] setFunctionCallListener: name function = LSO_COL_SET_ROOM_USERS; name application = com.sap.netweaver.coll.appl.room.rfcadapter.RFCService#
    #1.5#00144F3E9F4B00580000042E0000124100043F95592EEF09#1195810585767#com.sap.portal.RFCLogge

  • Problem when saving to .pdf from .ai..

    How do I fix this? I save a document from .ai to .pdf in CS5 and it automatically goes to the size of the artwork bounds instead of the artboard or paper size. Please help...

    I beleive we are having the same problem.
    If I take an active file and "save as" a pdf, the artboard behaves as it should (open file in Acrobat and the Page Size matches the Illustrator Artboard).
    If I continue to work in that file and do a "save" the Illustrator artboard is not "honored". If you open the file in Acrobat it now does not match the Illustrator artboard. The PDF page size becomes some kind of hybrid of the Ilustrator artwork bounds and the artboard???
    If I take that problematic file and then do a "Save As" and overwrite the same file, the problem is fixed, as long as I keep using save as.
    So far the only work around that has worked for me is to only use "save as" for PDFs. This is inconvienent for sure.
    I had suspected that the problem was related to some ESKO plugins, but now I am not sure. Do you happen to have ESKO plugins on your machine?
    Illustrator CC 17.1.0
    OSX 10.6.8
    imac 2.93 Ghz 16GB ram

  • Cannot Generate a PDF from Word 2007

    I have inherited a 100-page file in Word 2007, and have just encountered a problem when generating a PDF.  (BTW, I have Adobe Reader installed, and I have not yet receieved Acrobat for generating a PDF.)  To reduce file size and to send the file to others in remote locations, I have been saving the Word 2007 file as a PDF, and it has been working up until today.  When the file generated a PDF, it stopped on page 33 and asked if I wanted to send an error report. I have not changed anything on that page.  There is a figure and a table on that page, in addition to some text.  What could be causing the file to stop generating a PDF?  I removed the table and figure, but still the file stops generating on the following page.  I also have checked to make sure I do not have any styles that seem out of place.  Could you provide me with some guidance on what kinds of things I should try and troubleshoot?  Thanks!

    If you only have Reader, you can not create a PDF. You would need Acrobat.
    If you are "saving" as a PDF from Word, you are using the Microsoft PDF utility rather than Adobe's. You'll want to ask Microsoft support.

  • I have problem when transferring book (PDF/Epub) from Computer to iPad with the new iTune? Please Help....

    I have problem when transferring book (PDF/Epub) from Computer to iPad with the new iTune? Please Help....

    With iTunes 11 you can enable the left-hand sidebar via control-S on a PC, option-command-S on a Mac. If you are trying to get it to the iBooks app then with the sidebar enabled the process should be similar to how it was on previous versions of iTunes e.g. add it to your iTunes library via File > Add To Library, connect the iPad and select it on the left-hand sidebar, and then use the Books tab on the right-hand side to select and sync it to the iBooks app.

  • Problems when i copy text from Pdf and paste on Word

    In Pdf documente the text is in perfect conditions, but, when i copy the text and paste in WORD document the character change into random crazy character like: "()*"*&!(!*"(!"(!)"( )*"()!*("!&("@*")(!*@"!*@(
    how i fix this??

    I have the same problem when copying the PDF into a Word file. I tried Save as RTF doc. and it is still just symbols.
    It could be a font problem, because it has some weird Gill Sans and Futura fonts. I am sending a picture as an example.
    The option of exporting as Tiff and then applying OCR is interesting but still is kind of slow when i have a 100 pages document. If the fonts is the problem is there any way i could select the whole text and apply it a known font like Arial?
    Thanks for any info!
    Cheers,
    Sebastian

  • Generating a PDF from a OTF (imported from CLOSE_FORM) and send it by mail.

    Hello!
    I have a problem.
    I'll try to explain it toy you.
    I have a SapScript that the user has the option to send it to the printer or have a Print Preview. I need to send it by mail in PDF format.
    If the user select PRINT, a spool id is created, I can get the OTF, generate the PDF and send it by mail. Everything OK with that.
    The problem is if the user select PRINT PREVIEW I don't get a spool id. So, what I did is to get the OTF from the CLOSE_FORM MF and generate de PDF from there. I tried several FM to generate the PDF but for sure I'm doing something wrong, because or the PDF is corrupted or I have a problem with the parameters in the SO_NEW_DOCUMENT_ATT_SEND_API1 FM.
    So, what I need it: Generate a PDF from a OTF imported from CLOSE_FORM FM and send it by mail.
    Examples or the FM I can use are welcome.
    I tried to do search here, but I couldn't find anything that may help me..
    So, please... Show me the light!!!
    Thanks!!!
    Bettina

    Part 3
    * Send Report
      clear:    maildata, mailtxt, mailbin, mailpack, mailhead, mailrec.
      refresh:  mailtxt, mailbin, mailpack, mailhead, mailrec.
    * Creation of the document to be sent File Name
      maildata-obj_name = 'REPORT'.
    * Mail Subject
      maildata-obj_descr = 'Your Report'.
      describe table mailtxt lines tab_lines.
      read table mailtxt index tab_lines.
      maildata-doc_size = ( tab_lines - 1 ) * 255 + strlen( mailtxt ).
    * Creation of the entry for the compressed document
      clear mailpack-transf_bin.
      mailpack-head_start = 1.
      mailpack-head_num = 0.
      mailpack-body_start = 1.
      mailpack-body_num = tab_lines.
      mailpack-doc_type = 'RAW'.
      append mailpack.
    * Creation of the document attachment
      loop at solisti1.
        move-corresponding solisti1 to mailbin.
        append mailbin.
      endloop.
      describe table mailbin lines tab_lines.
      mailhead = 'REPORT.OTF'.
      append mailhead.
    ** Creation of the entry for the compressed attachment
      mailpack-transf_bin = 'X'.
      mailpack-head_start = 1.
      mailpack-head_num = 1.
      mailpack-body_start = 1.
      mailpack-body_num = tab_lines.
      mailpack-doc_type = 'OTF'.
      mailpack-obj_name = 'ATTACHMENT'.
      mailpack-obj_descr = 'Some Report'.
      mailpack-doc_size = tab_lines * 255.
      append mailpack.
      mailrec-receiver = lv_email_address.  "<-- a valid email address
      mailrec-rec_type  = 'U'.
      append mailrec.
    * Sending the document
      call function 'SO_NEW_DOCUMENT_ATT_SEND_API1'
           exporting
                document_data              = maildata
                put_in_outbox              = 'X'
           tables
                packing_list               = mailpack
                object_header              = mailhead
                contents_bin               = mailbin
                contents_txt               = mailtxt
                receivers                  = mailrec
           exceptions
                too_many_receivers         = 1
                document_not_sent          = 2
                operation_no_authorization = 4
                others                     = 99.
    Regards,
    Rich Heilman

  • Takes a long time to Generate a PDF from Frame 9. Why?

    It takes approximately 1 hour to generate a PDF from a 200 page Frame 9 doc (PDF file size Standard). There are lots of xrefs in the doc (more than 1500) but taking one hour to generate a PDF seems unusual. I remember the Frame 5 days when it took only minutes to generate large PDFs.

    tv95 wrote:
    It takes approximately 1 hour to generate a PDF from a 200 page Frame 9 doc (PDF file size Standard).
    It might help to know your system configuration. I have experienced such long times for PDF creation, when using FM9 in Parallels/Win XP Pro and saving to a shared volume on the same Mac. Now we are saving all documents (including PDFs) to a server, and we're back to PDFs in minutes
    Bernd

  • Adobe Acrobat XI Standard crashes when we create pdf from scanner

    We are using adobe acrobat XI standard, version 11.0.06
    WIndows 7 Pro 64 bit
    scanner: Xerox documate 4799
    Acrobat crashes when we create pdf from scanner

    Spent quite a while on this one..  My problem was related to twain drivers which reside in c:\windows\twain_32.  I'm running windows 7 64-bit.  First it's usually possible to scan in windows 7 maybe vista and from adobe without even using twain (using WIA).  So try renaming the twain_32 folder to _twain_32 and see what happens...  If that stops the crashing look at the contents of the twain folder.  I had a Dell folder for some printer I wasn't even using.  That was causing the crash. I removed the dell folder and renamed the twain folder back to twain_32.  Now everything works as designed.

  • Acrobat crashes when creating a PDF from a web page

    Whenever I ask Acrobat to create a PDF from a web page, it crashes halfway through the process.  Here is an example from the BBC:-
    http://www.bbc.co.uk/news/science-environment-19585341
    Printing to PDF from the browser does not produce an accurate document.  The font is too big, and most of the pictures do not appear.
    I use Acrobat X Pro version 10.1.4.
    This is a PC problem.  On the Mac it works.

    The problem I mentioned is peculiar to Acrobat 10 and also to my PC.  On a Mac I can create PDF's from webpages normally.
    I also notice that when printing to PDF from Opera only the first page comes out.  (Using Firefox all pages are printed to PDF.)

  • When creating a PDF from a PPT or Keynote application on a Mac using Acrobat X Pro, how do I ensure it can be opened on a PC? Do I need to save as a particular version of Acrobat?

    When creating a PDF from a PPT or Keynote application on a Mac using Acrobat X Pro, how do I ensure it can be opened on a PC? Do I need to save as a particular version of Acrobat?

    The system was not my own, it was on a PC belonging to the school where I teach. The error message referred to Acrobat 9.0, so I assume that the problem is to do with the version on which the file was created being more recent than that on which I attempeted to open it.

  • Missing images when printing to pdf from Word

    When printing to pdf from MS Word 2003 in some cases textboxes and/or images disappear in the target PDF, depending on their position.
    Word and Acrobat Standard are the latest updates. If the Word text is converted on a Mac the target pdf has the images present, so it looks like it's a Windows only problem. Any suggestions where to start looking for a fix?

    You may have to turn on "display large images" in the preferences.

Maybe you are looking for