PDF transfer R/3 RFC - XI - Portal DB scenario
Hi XI experts,
we have build up a scenario where we want to transfer generated PDF documents from R/3 over to a EP7. Would be a couple of docent per day about 20kb each.
The PDF gets generated in R/3 and is stored in db using CHAR255 chunks. Current plan is to get it into the portal db, from where it get pulled out and displayed to the user.
We have some serious problems in getting it there based on best practice and experience. We thought we had it already there but then realized that the data got corrupt by transfer probably because of wrong data types selected (?).
A couple of questions:
1. Which data type(s) should be used for storage in R/3 and Portal db and for transfer in XI?
2. Should we transfer in a table of small chunks or a big one (would be about 20kb max)?
3. Would it be easier to store them as files in portal server filesystem?
Thanks in advance,
ok
Hi,
How about using proxy or webservices with attachment?
Regards,
Wojciech
Similar Messages
-
HI
i start to buield rfc to portal and i wont to now what is the limit of time that the function have to run ,i now that the function for the portal have to run very fast.
i heard that if the function run to much time maybe u have to use a job to in night that select some data and help to bapi and i wont to now when i have to use it in numbers.
4,110,168 Microseconds FOR rfc its o.k. ?
thankeshi gurus
plz i need to now if there IS recommended time to run bapi for the portal?
<b>i reward</b>
Regards -
Will Export PDF transfer graphics to Word as well as text?
Does Export PDF transfer graphics as well as text to Word?
Hi Mary,
Yes it will as long as the entire file is below 100 MB. Let me know if you have further questions!
Regards, Stacy -
Rfc---xi---web service scenario error
Hi All,
I am doing rfc-xi--webservice synchronous scenario.
I followed this blog steps
RFC -> XI -> WebService - A Complete Walkthrough (Part 1)
I have deployed my own webservice and when i use it with xml spy it works fine.
But when i try to execute it from RFC module I got this error.
CALL_FUNCTION_REMOTE_ERROR
In XI monitoring both messages are with red status and i got theses error is xi message monitoring
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
- <!-- ************************************
-->
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Append context with name =ppActivated and value =false</Trace>
<Trace level="3" type="T">Das Mapping wurde bereits in der Interface-Ermittlung bestimmt.</Trace>
<Trace level="3" type="T">Objekt-Id des Interface-Mappings DA022058F9BB3E548D9760DEFC9240DA</Trace>
<Trace level="3" type="T">Versions-Id des Interface-Mappings 2A29312036EB11DDBE1AE1ED8D2C2629</Trace>
<Trace level="1" type="T">Interface-Mapping http://www.dummy.com/xi/01 IM_calculate</Trace>
<Trace level="3" type="T">Mapping-Schritte 1 JAVA com/sap/xi/tf/_MM_ws_dum_req_</Trace>
<Trace level="3" type="T">Dynamische Konfiguration ( http://sap.com/xi/XI/System/RFC ppActivated false )</Trace>
<Trace level="2" type="T">Modus 0</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_ws_dum_req_.</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_ws_dum_req_</Trace>
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_MM_ws_dhl_req_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:MT_DHL/productid. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.
I checked message mappings and those were correct
Any help or guidence please,
Regards
hussaanHI,
I tried to do that. When I test in IR it works but when I use XMl file to test as you indicated I am getting errors
I do not Know why.
Error is
Start of test
Compilation of MM_WS_DUM_REQ successful
Document start
Start tag [ns1:MT_TESTDDUM]
Add raw attribute [ xmlns:ns1="urn:DUM_FreightVi"]
Cannot produce target element /ns1:MT_TESTDUM/CALCULATE. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd Cannot produce target element /ns1:MT_TESTDUM/CALCULATE. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
16:38:37 End of test
I changed xml namespace in Message Type as it is indicated in How-to guides and other forums
Waiting for response
Regards
Hussaan -
Gettinfg error in RFC to Web Service scenario
hi friends,
I am getting the following error while configuring RFC to Web Service scenario.
I have used the ws :http://webservices.imacination.com/distance/Distance.jwsPlease help me out.
<!-- Inbound Message
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML; HTTP 407 Proxy Authentication Required ( The ISA Server requires authorization to fulfill the request. Access to the Web Proxy service is denied. )</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>Hi
check this thread
Getting error in target SOAP communication channel
regards
krishna -
Error in RFC to FTP asynchronous scenario
Hi Experts,
I have created RFC to File(FTP) scenario in SAP PI 7.31 AEX(java only) server.
When I execute RFC in sender SAP server, it gives run-time error(dump) as "call to messaging system failed".
But it successfully creates text file in target FTP server.
In message monitoring I found 2 messages for this.
First has status 'Canceled' with below message log,
Second message has status as 'Log Version' with no message log and with below message details.
Please suggest/guide me how to rectify this run-time error.
Thanks,
Amit PatilHi Jens,
I tried your suggestion, but couldn't work.
But I found 1 doubtful thing which is Quality of Service. It is found as
Quality of Service
BE
in message details of 1st message.
Also in message content of 1st message it is as
9/18/2014 1:36:51.053 PM
Information
File adapter receiver: processing started; QoS required: BestEffort
I don't know from where is getting set as 'BE'. It should be 'EO' since my scenario is asysnchronous.
Please suggest.
Thanks,
Amit Patil -
Hi,
I have a scenario like RFC to JDBC synch scenario, so what would be the QOS for sending( RFC) communication channel and as well as JDBC communicaiton channel.
Thanks n Advance.,
XeonHi,
Neither the Sender RFC adapter nir the Receiver JDBC adapter provide the option to select the QOS.
In your case if the report triggering the call to XI is making a Synch Call then the QOS in the SOAP header will be BE. If the Inbound Interface for the Receiver JDBC adapter is also a Synchronous Interface the QOS is taken as BE for the Receiver JDBC adapter.
You need not manually change the QOS anywhere as long as you are using Synch message interfaces.
Regards
Bhavesh -
How to use IDOC and RFC adapter in 1 scenario?
We have AAA field and BBB field and we want to send AAA field to receiver sap system using IDOC adapter and BBB field to receiver sap system using RFC adapter. But how to use IDOC and RFC adapter in 1 scenario and how to map and what are the design and configuration objects we require to create?
To achieve this you have to use
Two Interface Determinations
Two Communication Channels (IDOC & RFC)
& Two Receiver Aggrements.
Use the Enhanced Interface determination and give your conditions there. Based on you condition your interface mapping will be triggered and data will be sent to IDOC & RFC respectively. -
How to test the RFC to Flat File scenario
Hi,
How to test the RFC to Flat File scenario
regards,
kiranHi,
After running the RFC it's going Dump.
this is the error message i got.
"Error analysis
An error occurred when executing a Remote Function Call.
"CPI-C error CM_RESOURCE_FAILURE_NO_RETRY"
Status of connection.... "CODE=CM_RESOURCE_FAILURE_NO_RETRY -1 -1 SAPCODE=666
CONV="
Internal error code.... "RFC_IO5"
There is an error in the communication system. To clarify
and resolve the error, contact your system administrator. " -
RFC - XI - TCP/IP scenario. Pls help urgent
Hi All,
I have RFC -> XI -> TCP/IP scenario.
My scenario is quite similar to scenario given in blog:
/people/saravanakumar.kuppusamy2/blog/2005/12/15/socket-integration-with-xi
Questions.
1. Pls explain how Java Mapping is done in XI. ?
2. In real scenario static void main (String[] args) method will
not be there because request will come automatically from
SAP source and response from tcp/ip system.
Am I corrcet?
3. My response is not xml. Pls send me updated code that
can convert string array byte format to xml.
Is there any simple way to do this scenario.
Full points will be awarded.
ThanksHi Rider,
You can implement mapping programs in Java. To process XML documents, use Java API for XML Processing (JAXP), for example. The JAXP supports the Document Object Model (DOM) and the Simple API for XML (SAX). This gives you great flexibility for mapping definitions with Java.
The runtime environment for Java mappings has an mapping API. To use Java mapping, you must define a Java class that implements the Java interface com.sap.aii.mapping.api.StreamTransformation. This interface has two methods:
● public void execute(java.io.InputStream in, java.io.OutputStream out)
At runtime, the Integration Engine calls this method to execute a mapping. This method contains an input stream for the source document and an output stream for the target document as parameters. These streams are usually XML documents. You can import the substructures to be converted from the input stream and output the converted target document in the output stream.
● public void setParameter(java.util.Map param)
The Integration Engine transfers parameters to the mapping program with this method. It evaluates these parameters at runtime in the method execute(). This enables you to control the process flow of the mapping.
The transferred object that implements the Java interface java.util.Map contains seven key/value pairs as parameters. These correspond to corresponding fields in the message header. Apart from the MAPPING_TRACE constant, the value objects are of type java.lang.String. The key objects are defined in the class com.sap.aii.mapping.api.StreamTransformationConstants:
(plz check this in the link):
http://help.sap.com/saphelp_nw04/helpdata/en/e2/e13fcd80fe47768df001a558ed10b6/content.htm
For Key-Value Pairs, check out the link:
http://help.sap.com/saphelp_nw04/helpdata/en/b3/9a2aeb24dc4ab6b1855c99157529e4/content.htm
Plz reward points if satisfied.
Regards,
Sushama -
(SOAP sender) --- XI ---- R/3 (RFC receiver) this sync scenario
Hi Experts,
Webservice(SOAP sender) < - > XI <--> R/3 (RFC receiver) this sync scenario tested with Infopath successfully.
I have given partner number,student object id are the two input fields(request) and i am getting student number as response. This scenario is working when i use MS infopath.
I have generated WSDL file embedded with below URL
http://xxxx.yyytec.passh.ed:7271/XISOAPAdapter/MessageServlet?channel=:Webservice_Sender_BS:GET_NUMBERS_Sender_CC&version=3.0;amp;Sender.Service=Webservice_Sender_BS;amp;Interface=urn%Apache
Sender business system: Webservice_Sender_BS
Sender CC: GET_NUMBERS_Sender_CC
Msg Interface: STU_GET_NUMBERS_Synch_MI
now we want to test from third party website, what are the things to be provided to the website developer to test the scenario.
the way i generated URL, is it correct?
if i provide above URL and generated WSDL in XI , is it enough for web developer to enter the input fields to RFC(r/3) via XI as webservice request and getting back response from RFC(r/3) to webservice via XI.
can you please advice if any body worked on this kind of scenario.
Thanks
Dhanush.For the developer you have to provide WSDL file so that they know the input/output fields and write the code.
URL is correct.
Other informatino they required is Username and password of you PI system.
Gaurav Jain
Points if answer is helpful -
CRM factsheet and BI 7.0 Web-Templates in Federated Portal Network Scenario
Hi All,
i have some essential questions regarding a Federated Portal Network Scenario.
Our costumer works with 1 CRM-Portal (CRM 5.0, EP 7.0) and 1 BI-Portal (BI/EP 7.0).
He decided to implement a Federated Portal Network, using the CRM-Portal as the Consumer-Portal.
In the CRM-Portal we are working with the Business Package for SAP_CRM which also comprises Reports that are called from the BI.
The BI-Reports (BI 7.0 Web Templates) are now stored in the BI-Portal
How i can assign these BI-Reports (producer) into the factsheet of the CRM-Portal (consumer)?
Is that generally possible that the facsheet of the Consumer Portal (CRM) works togehther with BI 7.0 Web Templates from the Producer-Portal (BI)?
Best regards
Mustafa DarwishIt's been solved.
See note: 1058268 - BI 7.0 WebTemplates do not run in CRM 5.0 specific iViews -
Hi,
I have to carry out a RFC to multi-file scenario. The requirement is that Error generating on whatever part XI will handle have to be reported. Is this possible in this scenario? What can be the mechanism?
I want to report these errors via a mail to an e-mail id.
Since i haven't done this scenario, i would appreciate if some link for carrying this out step-by-step is given.Also tell me what configuration for receiving RFC has to be done on XI and R/3.Hi Arpit
<b>go through these blogs for the querry</b>
<b>For email alerts</b>
/people/aravindh.prasanna/blog/2005/12/24/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-2
/people/aravindh.prasanna/blog/2006/02/20/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-3
/people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
You have to do SMTP Configuration for EMail and SMS.....
http://help.sap.com/saphelp_nw04/helpdata/en/af/73563c1e734f0fe10000000a114084/content.htm
Thanks !! -
Convert PDF to XSTRING and dysplay in portal(html)
Hi experts :
I need your help once again. I've read all the post regarding this issue but can't find a solution for my problem.
Basically, I have to create a PDF from a spool, convert it to xstring and send it to the web via RFC.
What I do is :
Convert the spool to PDF using FM CONVERT_OTFSPOOLJOB_2_PDF.
Convert the PDF tline table into XSTRING using a field symbol and a table of tlines (as described in one of the SDN blogs).
Then, I send to the web the value reurned from the conversion of the PDF line to XSTRING.
But, when opening the xstring there is nor PDF file but and error. If I download the PDF tline table, it works and can create the PDF, but nothing from the XSTRING.
My questions are :
Do we have to do any conversion on the portal side to convert the XSTRING into PDF?
is there any possibility of downloading the xstring to my desktop in order to check if I could create the PDF file from it?.
Helpful answer will be rewarded.
Regards,
Carlos.For the last question, use this code:
FORM write_bin_file
USING
i_filename TYPE string
i_file_xstring TYPE xstring.
TYPES xx(50) TYPE x.
DATA lt_xstring TYPE TABLE OF xx.
DATA l_length TYPE i.
CALL METHOD cl_swf_utl_convert_xstring=>xstring_to_table
EXPORTING
i_stream = i_file_xstring
IMPORTING
e_table = lt_xstring
EXCEPTIONS
OTHERS = 3.
l_length = XSTRLEN( i_file_xstring ).
CALL METHOD cl_gui_frontend_services=>gui_download
EXPORTING
bin_filesize = l_length
filename = i_filename
filetype = 'BIN'
CHANGING
data_tab = lt_xstring
EXCEPTIONS
OTHERS = 3.
ENDFORM. "write_bin_file -
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 PHi 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
Maybe you are looking for
-
Can't get batch from droplet to start processing
I'm using Compressor 4.0.7 running 10.8.5, but I've seen similar posts on other boards (Creative Cow) reaching back 2-3 years with same issue so I don't think it is new. When using a droplet to submit a batch vs. submitting manually through Compresso
-
Is this website loading slow to u?
Click to check my website I has tried to clean the codes and use background images more and less graphics Can anyone help to tell me? and give me some advices? Many thanks.
-
Can you save Picture In Picture settings as a favorite, like you would save a transition? (I know you can copy and paste attributes from another clip in the timeline) I am making PIPs using the Motion Tab on the Viewer, is there another way?
-
NSP (nw04sSP9) installed OK, but SAPgui fails on start
Hi I installed NSP Ok and it starts OK in sap console. When I login using SAPGUi I get the following error even before sap login screen. Runtime Error: DBIF_RSQL_INVALID_REQUEST Error Analysis: an invalid request was made to the SAP database interfac
-
HT4085 Why isn't "hold" an option for the side switch on the iPad?
Why isn't "hold" an option for the side switch on the iPad? I'd like to be able to let my 3 year old watch videos on the iPad, but young kids want to touch the screen. I need a method to disable the touch screen. Seems simple, why isn't this an opt