Synch. RFC call error - No Sender Found

Hi,
once execute the synchronous RFC call from BPM, rfc response message returns as following;
<SAP:Code area="RCVR_DETERMINATION">MESSAGE_INCOMPLETE</SAP:Code>
<SAP:Stack>Message is incomplete. No Sender found</SAP:Stack>
i've tried adding header mappings at receiver aggreement for bpm's name as sender service and target sap system name as receiver service. Same error.
Any help is greatly appreciated. Thanks

Hi,
>>>>i've tried adding header mappings at receiver aggreement for bpm's name as sender service and target sap system name as receiver service. Same error.
no need for any header mapping in that case
just configure the routing correctly - via directory wizard
and everything will work
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Similar Messages

RFC Call error..

Hi All XI Expert,
I am facing an issue with regard to RFC call from an external system.Business flow is like, Purachase Requisition(PR) is created from Ariba system/application which is passed to SAP via TIBCO Adapter to create Purchase order(PO).As per my understanding the data flow is like this: Ariba PR data's are captured by Ariba Adater and are send to TIBCO ADAPTER.This TIBCO adapter will invoke request-response service from SAP Adapter for operation of SAP RFC calling.Now i am able to successfully create PR/PO from Ariba application with amount(more than $10mn with after decimal value as 00) say $12,000,000.00 / $15,000,000.00. But while creating PR/PO from Ariba application with amount (more than $10mn with after decimal value as other than 00 i.e .99, .78, .05 etc) say $12,000,000.99 / $15,000,000.08, it gives below error which are captured in Ariba side, hence unable to create PR/PO's more than $10mn, however for less than $10mn amount of PR/PO with after decimal value as other than 00 i.e .99, .78, .05 etc, it is successfully getting created.So the problem is amount with more than $10mn PO with after decimal value as other than 00 i.e .99, .78, .05 etc.
Error found in Ariba side for above scenarion:
" Thu Apr 09 12:21:49 EDT 2009 (integrationExternal:error:4745): Received a Tibco generated message: 2009 Apr 9 12:21:49:079 GMT -5 SAPAdapter.SAInboundRFC.psap1 Error Application AER3-000185 CallReceive failed for operation Z_ARIBA_PO_PUSH; exception : Unable to interpret 1.10000005E7 as a number., RFC error; Group/Key/Message: 104/CONVT_NO_NUMBER/Unable to interpret 1.10000005E7 as a number.
Where could be the problem?Does it a TIBCO Adapter config/ SAP adapter Problem / SAP RFC code issue?
FYI....SAP RFC that is getting called doesnot contain any code of "CONVT_NO_NUMBER" .
Awaiting your reply guys

The problem is that in case the value of the amount is greater than $10mn, then it is converting the numeric value into exponential number 1.10000005E7. This is a number but when RFC tries to treat it as a number, it is throwing the exception. At sender Ariba system, you may change some configuration to avoid changing of numeric field to exponential field and problem would get resolved.
Regards,
Prateek

RFC Call Error - from Portal End - For ESS Personal Information service

Hi,
I am getting "Syntax error in program SAPLHRXSS_PER_MAC ., error key: RFC_ERROR_SYSTEM_FAILURE " error Message on the portal (ESS--->Personal Information Screen).
When I did RFC trace analysis (using ST 22) this is what i get.
Can you let me know what could be the issue.
We are running HR Backend(Support Pack 15,ecc 5.0).
Portal (EP 6.0 SP19, ESS 100 (SP 10)).
Could you please let me know what could be the issue ?
Syntax error in program "SAPLHRXSS_PER_MAC ".
 What happened?
 Error in ABAP application program.
 The current ABAP program "SAPMSSY1" had to be terminated because one of the
 statements could not be executed.
 This is probably due to an error in the ABAP program.
 In program "SAPLHRXSS_PER_MAC ", the following syntax error occurred
 in the Include "IF_HRPA_PERNR_INFTY_XSS=======IU " in line 114:
 "The type "HRXSS_PER_SUPPLD_SUBTY_INFO_T" is unknown."
 Author and last person to change the Include are:
 Author "SAP "
 Last changed by "C5069405 "
 What can you do?
 Please eliminate the error by performing a syntax check
 (or an extended program check) on the program "SAPLHRXSS_PER_MAC ".
 You can also perform the syntax check from the ABAP/4 Editor.
 If the problem persists, proceed as follows:
 Print out the error message (using the "Print" function)
 and make a note of the actions and input that caused the
 error.
 To resolve the problem, contact your SAP system administrator.
 You can use transaction ST22 (ABAP Dump Analysis) to view and administer
 termination messages, especially those beyond their normal deletion
 date.
 is especially useful if you want to keep a particular message.
 Error analysis
 In program "SAPLHRXSS_PER_MAC ", the following syntax error occurred:
 "The type "HRXSS_PER_SUPPLD_SUBTY_INFO_T" is unknown."
 How to correct the error
 Probably the only way to eliminate the error is to correct the program.
 If you cannot solve the problem yourself and you wish to send
 an error message to SAP, include the following documents:
 1. A printout of the problem description (short dump)
 To obtain this, select in the current display "System->List->
 Save->Local File (unconverted)".
 2. A suitable printout of the system log
 To obtain this, call the system log through transaction SM21.
 Limit the time interval to 10 minutes before and 5 minutes
 after the short dump. In the display, then select the function
 "System->List->Save->Local File (unconverted)".
 3. If the programs are your own programs or modified SAP programs,
 supply the source code.
 To do this, select the Editor function "Further Utilities->
 Upload/Download->Download".
 4. Details regarding the conditions under which the error occurred
 or which actions and input led to the error.
 System environment
 SAP Release.............. "640"
 Application server....... "srv006"
 Network address.......... "167.116.230.56"
 Operating system......... "HP-UX"
 Release.................. "B.11.11"
 Hardware type............ "9000/800"
 Character length......... 8 Bits
 Pointer length........... 64 Bits
 Work process number...... 1
 Short dump setting....... "full"
 Database server.......... "srv006"
 Database type............ "ORACLE"
 Database name............ "H81"
 Database owner........... "SAPR3"
 Character set............ "en_US.iso88591"
 SAP kernel............... "640"
 Created on............... "May 21 2006 20:29:01"
 Created in............... "HP-UX B.11.00 A 9000/800"
 Database version......... "OCI_920 "
 Patch level.............. "129"
 Patch text............... " "
 Supported environment....
 Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
 10.2.0.."
 SAP database version..... "640"
 Operating system......... "HP-UX B.11"
 Memory usage.............
 Roll..................... 16128
 EM....................... 4189928
 Heap..................... 0
 Page..................... 0
 MM Used.................. 629192
 MM Free.................. 3558216
 SAP Release.............. "640"
 User and Transaction
 Information on where terminated
 The termination occurred in the ABAP program "SAPMSSY1" in
 "REMOTE_FUNCTION_CALL".
 The main program was "SAPMSSY1 ".
 The termination occurred in line 68 of the source code of the (Include)
 program "SAPMSSY1"
 of the source code of program "SAPMSSY1" (when calling the editor 680).
 Source Code Extract
 Line SourceCde
 38
 39 module %_rfcdia_call output.
 40 "Do not display screen !
 41 call 'DY_INVISIBLE_SCREEN'.
 42 perform remote_function_diacall.
 43 endmodule.
 44
 45 module %_cpic_start.
 46 if sy-xprog(4) = '%RFC'.
 47 perform remote_function_call using rfctype_external_cpic.
 48 else.
 49 call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.
 50 perform cpic_call using convid.
 51 endif.
 52 endmodule.
 53
 54
 55 form cpic_call using convid type c.
 56 communication send id convid buffer header.
 57 if sy-subrc eq 0.
 58 perform (sy-xform) in program (sy-xprog).
 59 else.
 60 message a800.
 61 endif.
 62 endform.
 63
 64 form remote_function_call using value(type).
 65 do.
 66 * test if sy-xprog and sy-xform are set
 67 * sy-xform = 'quatsch'. sy-xprog = 'quatsch'.
 >>>>> call 'RfcImport' id 'Type' field type.
 69 perform (sy-xform) in program (sy-xprog).
 70 rsyn >scont sysc 00011111 0.
 71 enddo.
 72 endform.
 73
 74 form remote_function_diastart.
 75 do.
 76 call 'RfcImport' id 'Type' field rfctype_rfcdia.
 77 perform (sy-xform) in program (sy-xprog).
 78 "Parking position for next request
 79 rsyn >scont sysc 00011111 10.
 80 "ALternativ : Free mode
 81 "COMMIT WORK.
 82 "SYSTEM-CALL FREE MODE 0.
 83 enddo.
 84 endform.
 85
 86 form remote_function_diacall.
 87 sy-xcode = '%_@no@'.
 Contents of system fields
 Name Val.
 SY-SUBRC 0
 SY-INDEX 2
 SY-TABIX 0
 SY-DBCNT 0
 SY-FDPOS 0
 SY-LSIND 0
 SY-PAGNO 0
 SY-LINNO 1
 SY-COLNO 1
 SY-PFKEY
 SY-UCOMM
 SY-TITLE CPIC and RFC Control
 SY-MSGTY
 SY-MSGID
 SY-MSGNO 000
 SY-MSGV1
 SY-MSGV2
 SY-MSGV3
 SY-MSGV4
 Active Calls/Events
 No. Ty. Program Include Line
 Name
 2 FORM SAPMSSY1 SAPMSSY1 68
 REMOTE_FUNCTION_CALL
 1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30
 %_RFC_START
 Chosen variables
 Name
 Val.
 No. 2 Ty. FORM
 Name REMOTE_FUNCTION_CALL
 %_DUMMY$$
 2222
 0000
 SY-REPID
 SAPMSSY1
 5454555322222222222222222222222222222222
 310D339100000000000000000000000000000000
 SYST-REPID
 SAPMSSY1
 5454555322222222222222222222222222222222
 310D339100000000000000000000000000000000
 %_ARCHIVE
 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 TYPE
 3
 0000
 0003
 SY-XPROG
 SAPLSYST
 5454555522222222222222222222222222222222
 310C393400000000000000000000000000000000
 SY-XFORM
 HRXSS_PER_CLEANUP
 455555545544444552222222222222
 82833F052F3C51E500000000000000
 %_SPACE
 2
 0
 No. 1 Ty. MODULE (PBO)
 Name %_RFC_START
 %_PRINT
 000 0 ##
 2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223200
 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 RFCTYPE_INTERNAL
 3
 0000
 0003
 Internal notes
 The termination occurred in the function "ab_genprog" of the SAP
 Basis System, specifically in line 1374 of the module
 "//bas/640_REL/src/krn/runt/abgen.c#10".
 The internal operation just processed is "CALY".
 The internal session was started at 20070502223335.
 Program name.........: "SAPLHRXSS_PER_MAC ".
 Error message........: "The type "HRXSS_PER_SUPPLD_SUBTY_INFO_T" is unknown.".
 Active Calls in SAP Kernel
 Lines of C Stack in Kernel (Structure Differs on Each Platform)
 ( 0) 0x40000000016d6a8c CTrcStack2 + 0x2bc [dw.sapH81_DVEBMGS33]
 ( 1) 0x40000000016d67c0 CTrcStack + 0x18 [dw.sapH81_DVEBMGS33]
 ( 2) 0x4000000001d41438 rabax_CStackSave__Fv + 0x100 [dw.sapH81_DVEBMGS33]
 ( 3) 0x4000000001d4dbf8 ab_rabax + 0x1f68 [dw.sapH81_DVEBMGS33]
 ( 4) 0x40000000018cc09c ab_genprog__FPcPvUii + 0xdbc [dw.sapH81_DVEBMGS33]
 ( 5) 0x4000000000d3b4cc newload__FPcP13TmpSubpoolDirUi + 0x29c [dw.sapH81_DVEBMGS33]
 ( 6) 0x40000000016a7324 ab_LoadProg__FPcUi + 0xec [dw.sapH81_DVEBMGS33]
 ( 7) 0x40000000016831fc ab_link + 0x334 [dw.sapH81_DVEBMGS33]
 ( 8) 0x40000000015694d4 ab_rfcimport + 0xccc [dw.sapH81_DVEBMGS33]
 ( 9) 0x40000000018cff98 ab_jcaly__Fv + 0x598 [dw.sapH81_DVEBMGS33]
 (10) 0x4000000000f98df8 ab_extri__Fv + 0x17a0 [dw.sapH81_DVEBMGS33]
 (11) 0x40000000016ab2d8 ab_xevent__FPCc + 0x38 [dw.sapH81_DVEBMGS33]
 (12) 0x400000000189c9a8 ab_dstep + 0x120 [dw.sapH81_DVEBMGS33]
 (13) 0x4000000000ed4c00 dynpmcal + 0xd0 [dw.sapH81_DVEBMGS33]
 (14) 0x4000000000ed1554 dynppbo0 + 0x1e4 [dw.sapH81_DVEBMGS33]
 (15) 0x4000000000ed0af4 dynprctl + 0x43c [dw.sapH81_DVEBMGS33]
 (16) 0x4000000000ecb7a0 dynpen00 + 0x2118 [dw.sapH81_DVEBMGS33]
 (17) 0x4000000000fa598c Thdynpen00 + 0x6a4 [dw.sapH81_DVEBMGS33]
 (18) 0x4000000000fa49b8 TskhLoop + 0x50d8 [dw.sapH81_DVEBMGS33]
 (19) 0x4000000000f999f8 tskhstart + 0x1e0 [dw.sapH81_DVEBMGS33]
 (20) 0x4000000000d42194 DpMain + 0x484 [dw.sapH81_DVEBMGS33]
 (21) 0x400000000220d41c nlsui_main + 0x14 [dw.sapH81_DVEBMGS33]
 (22) 0x4000000000992794 main + 0x14 [dw.sapH81_DVEBMGS33]
 (23) 0xc000000000020ab0 $START$ + 0xa0 [/usr/lib/pa20_64/dld.sl]
 List of ABAP programs affected
 Index Ty. Program Group Date Time Size Lang.
 0 Prg SAPMSSY1 0 06.11.2003 20:53:07 18432 E
 1 Prg SAPLSYST 1 10.05.2006 09:57:38 30720 E
 2 Typ SYST 0 04.12.2000 14:54:51 27648
 Directory of Application Tables
 Name Date Time Lngth
 Val.
 Program SAPMSSY1
 SYST . . : : 00002404
 ABAP Control Blocks (CONT)
 Index Name Fl PAR0 PAR1 PAR2 PAR3 PAR4 PAR5 PAR6 SourceCde
 118 CLEA 00 0035 SAPMSSY1
 119 CLEA 00 0036 SAPMSSY1
 120 CLEA 00 0037 SAPMSSY1
 121 MESS 00 001C SAPMSSY1
 122 ENDF 00 0000 SAPMSSY1
 123 -
 00 0000 SAPMSSY1
 124 PERP 00 0001 SAPMSSY1
 125 PERP 02 0000 SAPMSSY1
 126 WHIL 00 0002 0000 0000 0000 0000 0000 0000 SAPMSSY1
 130 WHIL 00 0003 0000 0000 0000 0000 0000 0000 SAPMSSY1
 134 BRAN 05 000E SAPMSSY1
 135 CALY 00 0003 0038 002A 0005 002B 0000 0000 SAPMSSY1
 >>>>> CALY 02 0000 0039 8000 0000 0000 0000 0000 SAPMSSY1
 143 xper 02 0000 0010 0011 SAPMSSY1
 145 PERP 80 0000 SAPMSSY1
 146 SYSC 1F 0000 SAPMSSY1
 147 BRAX 00 FFEF SAPMSSY1
 148 WHIL 00 0004 0000 0000 0000 0000 0000 0000 SAPMSSY1
 152 ENDF 00 0000 SAPMSSY1
 153 -
 00 0000 SAPMSSY1

Hi,
The error is occuring in the program file SAPLHRXSS_PER_MAC.
In program "SAPLHRXSS_PER_MAC ", the following syntax error occurred
in the Include "IF_HRPA_PERNR_INFTY_XSS=======IU " in line 114:
"The type "HRXSS_PER_SUPPLD_SUBTY_INFO_T" is unknown."
Information on where terminated
 The termination occurred in the ABAP program "SAPMSSY1" in
 "REMOTE_FUNCTION_CALL".
 The main program was "SAPMSSY1 ".
This place where it has terminated is highlighted in bold letters.
form remote_function_call using value(type).
do.
test if sy-xprog and sy-xform are set
sy-xform = 'quatsch'. sy-xprog = 'quatsch'.
 call 'RfcImport' id 'Type' field type. 
 perform (sy-xform) in program (sy-xprog).
 rsyn >scont sysc 00011111 0.
enddo.
endform.
Thanks,
Manoj

RFC call error with no exception associated.

I'm remotelly calling FM L_TO_CREATE_SINGLE. When the ubication is locked up the FM produces an error which results in lose of contact with the remote system or something like that. What I get is a dump with CALL_FUNCTION_RECEIVE_ERROR.
I've looked at ST22 and there is not associated exception, so I can't catch it.
How can I avoid the dump?
Thanks in advance.

Are you using the communications and system failure exceptions when calling the RFC?
data: lv_message type char255.
example:
CALL FUNCTION 'RFC_XXXXX'
destination 'YYYY'
exceptions
system_failure = 1 message lv_message.
communication_failure = 2 message lv_message
A short dump (or any other kind of error for that matter) will be stored in the variable lv_message.
Kind regards,
Micky.

SOAP to RFC Scenario - Error at Sender Communication channel !!

Hi Experts ,
I am trying to execute a SOAP to RFC scenario . At SOAP sender channel level I am getting the error in RWB .
My findings :-
1. Error at RWB 9/24/09 4:24:10 PM error occured
 9/24/09 4:24:06 PM request received
2. At SOAP UI client tool :
 <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>ADAPTER.JAVA_EXCEPTION</code>
 <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:UPDATE:HTTP status code401 Unauthorized
 at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
 at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
 at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:917)
 at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(AccessController.java:207)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>
3. At SOAP UI level - "requires authentication with the realm 'XISOAPApps'"
1. I don't see any issue in authorization as i am having SAP_ALL .
2. URL string seems to be O.K :
 http://ABC:50000//XISOAPAdapter/MessageServlet?channel=:BSer_SOAP:CC_SOAP_Sender&version=3.0&Sender.Service=BSer_SOAP&Interface=urn:ABC.com:%5EMI_CustomerInfo
Kindly advice !!!
Regards ,

1. Check PI id and password is working fine.
Check if the user you are using has SAP_XI_APPL_SERV_USER role.
Another way is to pass id and pwd in URL
Try to pass the User ID and Password in the URL( the URL which is given to the webservice).
Example: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel &sap-user=xxxx&sap-password=xxxx
2.Provide SOAP URL like -
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel

JDBC to RFC synch RFC call not executing.

Hi,
I am working on the synchronous JDBC to RFC without BPM. After completing design and config when I test the complete scenario the data from databse is not getting updated in R/3. And I do not see any errors in MONI. But when compared the moni logs I observed the following between the working scenario and not working scenario.
Working scenario log in MONI:
<SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>ECS300</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/XI/System">InterfaceCollection</SAP:Interface>
- <SAP:Mapping notRequired="S">
<SAP:ObjectId>YYgNVKC9PTCW4JlMapfxZQ==</SAP:ObjectId>
<SAP:SWCV>IrmTYNPLEdqKItGjlusuXw==</SAP:SWCV>
Not working log from the MONI:
++++++++++++++++++++++++
<SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>ECS300</SAP:Service>
<SAP:Interface namespace="http://my_Own_namespace">JDBC_Rfc_Synch_MI</SAP:Interface>
- <SAP:Mapping notRequired="M">
<SAP:ObjectId>28ZZbGggOw6UcnigDXMD7A==</SAP:ObjectId>
<SAP:SWCV>IrmTYNPLEdqKItGjlusuXw==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
Could some body point me where I am doing wrong ?
Thaks
Steve.

Hi Steve,
I think the error is because your database table is expecting some kind of input and the input you are passing has some error in it.Just cross check the table using DESCRIBE <tablename> with the data you are trying to enter.
Also Just look at Query SQL Statement part ubnder this link,
http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/content.htm
Regards,
abhy

Rfc call error bps

Hi,
I am getting this error when I am uploading file for bps.
You have selected a function to execute this the system must set up an RFC Connection to another SAP System. However, setting up this connection was not successful. The following internal error message was generated
"You do not have authorization for Infocube <infocubename>"
please guide me which authorization is missing.

Check if your profile contains S_RS_ICUBE authorization object with following settings for the cube in which you are trying to load the data:
ACTVT 03
RSICUBEOBJ CHAVLREL, DATA, DATASLICE, DEFINITION, EXPORTISRC, UPDATERULE
RSINFOAREA *
RSINFOCUBE <Cube name>
Or if your have any anyalsis authorizations created, go in RSECADMIN and check your analysis authorization object for below:
0TCAACTVT 02, 03
0TCAIPROV <Cube Name>
TCAVALID *

SRFC-adapter and file adapter with error: no adapter found

Hello,
we have two scenarios here in an XI 3.0 SP12:
First scenario connects two R/3 systems via RFC adapter (outbound / inbound) for an RFC in a standard R/3 function module SUSR_ZBV_GET_REMOTE_PROFILES.
The RFC is synchronous.
Second scenario uses file adapter to send file from A to B.
When starting the RFC call from the sender system the error message in area "call adapter" for XML message in the trace is "exception while reading from SLD:Property sap_xiadapterservice.adapterType does not exist".
Message in RWB:
"Transmitting the message using connection http://abc038.ceu.test.com:8077/sap/xi/engine?type=entry failed, due to: XIServer:AE_DETAILS_GET_ERROR:Property sap_xiadapterservice.adapterType does not: Unable to find any Adapter Engines."
Same problem for file adapter!
Here is the message from the file adapter error log entry in SXMB_MONI:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.kx1.test038</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>Property sap_xiadapterservice.adapterType does not: Unable to find any Adapter Engines</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.kx1.test038</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Looks like an identical problem for both adapter.
What we have done (checked) so far:
- SLD connection is working
- Vis.Admin.: no problems found
(SAP RFC adapter active, file adapter active)
- Component monitoring: no errors, adapters are fine
- all rfc connections checked: ok
- have checked user and pwd and replaced to be sure
- cache refresh: ok
- reimport of SWCV to IR for RFC: done, no result
Does anybody have an idea, how to get rid of that?
Best regards
Dirk

Hello Udo,
in Adapter monitoring all adapters are listed and per adapter (here RFC and FILE) all adapter entries from the scenarios are available (sender / receiver comm. channel entries - in green)!
Pipeline URL in SLD Bus. Syst. is fine ( and an IDOC adapter scenario is running successfully) !
I think this is a really tricky one!
Best regards
Dirk

RFC mapping error

Hi,
I tried to test a scenario WS to RFC call. I send a SOAP req and got this error in moni.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="RFC_ADAPTER">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="urn:sap-com:document:sap:rfc:functions">ZPI_CONSUMER_PAYMENT_BILL_DATA.Exception</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Regards
Satt

Hi Sathish,
The RFC which you are using in the PI, test it manually or statically in the source system. Use the same data you are passing to it in PI. This will provide you the exception that RFC has thrown.

Error with Asynchronous RFC call to JDBC

Hi all,
We are working on a scenarion where in we have to make an asynchronous RFC call to JDBC.
We have configured RFC sender adapter following this weblog
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
We have created data types only for the database as RFC does not require any data types.
And also we have created message types,message interfaces accordingly.
In Message Mappping,we mapped the export parameters of RFC to the access fields of database message type.
Also we have created sender agreement,interface determinations etc.... accordingly
And for sending RFC request asynchronously we followed this weblog
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
Once done with all the above steps we could able to trigger the RFC call and caught with the following errors in SXMB_MONI and no errors are seen in communication monitoring
SOAP Error:
+<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>+
+- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_curr_exg_mm2_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" /> <SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_curr_exg_mm2_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also trace shows the following error thogh the interface determinations are properly configured
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface BAPI_EXCHRATE_GETCURRENTRATES*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:rfc:functions</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
the above errors are shown as part of request mapping..
Can any one please let me know what other configurations do we need to do?
I did not map the RFC import parameters,do we need to do that
Any help in this regard is really appreciated
Rgds,
Santhosh

Hi,
I am really happy to hear that the problem with mapping is resolved.
Now as per your requirment It needs to be aynschornous RFC--> XI ---> JDBC call. In XI you should map the RFC Export parameters to the traget structure of JDBC.
then the question is to how to trigger the RFC Function Module in R/3 to XI.
Plesae follow below steps to trigger it from SAP R/3
1. Create a RFC in the R/3 system
2. Configure the SM59 and Sender Communication channle as given in the Michal's blog. Also test if it is succesful.
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
3. Import the RFC in XI
4. Do the mapping to the target strucutre
5. Configure the JDBC receiver adapter
/people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
6. You can trigger the RFC from R/3 sytem by using
Async Call - in ABAP program use below syntax to call RFC. Here the export parameters will be passed on to XI which further have mapped to JDBC.
CALL Function "RFC Name" IN BACKGROUND TASK destination <sm59 destination>
COMMIT WORK.
Sync Call
CALL Function "RFC Name" destination <sm59 destination>
Thanks
Swarup
Edited by: Swarup Sawant on Jan 27, 2008 9:14 AM

Error in Broadcaster - An Active RFC Server could not be found

Hi all,
I am trying to broadcast a workbook to my mailbox through Information Broadcasting, i am trying this in BI 7.0 system. In the Broadcasting wizard, I gave my mailid & the other required credentials. But when i click on Schedule, i am getting a Error message "An Active RFC Server could not be found. Error occured during processing of framework class CL_RSRD_PRODUCER_EXCEL, type PROD".
I checked in SU01 & my mailid is already added there. So, where am i missing or is there any settings need to be done for the Broadcaster to work?
Thanks,
Murali

The precalc server is not needed if you are generating html output, but certainly is mandatory for the Broiacaster to run/distribute BEx Excel Workbooks.
The BW needs access to a Windows computer that has Excel on it. The BW connects to the Precacl and sends it a request it run a BEx wkbk, which the BW then can email to users.
The precalc server is a Windows Service. You can install it locally on your desktop, or it can be installed on a windows server. There is a little config that needs to be done. The How To Troubleshoot Information Broadcasting link in the other resposne will provide all the steps. You should obtain the most current version of the software from SAP.
You'll need a precalc server for each BW system in your landscape that you want to broadcast BEx wkbks from, so if you have Dev and QA systems, you'll need precalcs for them as well.

RFC error when sending logon data

Hi;
We cannot configure the STMS of our development system. When we try to
configure it, system gives an error message: Errors during distribution
of tp configuration; TMS Alert Viewers tells us
RFC_COMMUNICATION_FAILURE: RFC communications error with
system/destination TMSADM-FKT.DOMAIN_FKT RFC error when sending logon
data and READ_PROFILE_FAILED:File
erptest\sapmnt\trans\bin\TPPARAM
could not be opened for reading (No such file or directory).
Is there any advise for solution?
Best regards
Noyan
PS: Please find the profiles below:
START:
#.*       Start profile START_DVEBMGS00_erptest                                                                                *
#.*       Version                 = 000006                                                                                *
#.*       Generated by user = BASIS                                                                                *
#.*       Generated on = 30.12.2010 , 15:40:55                                                                                *
generated by R3SETUP
SAPSYSTEMNAME = FKT
INSTANCE_NAME = DVEBMGS00
SAPSYSTEM = 00
SAPGLOBALHOST = erptest
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
start database
#_DB = strdbs.cmd
#Start_Program_02 = immediate $(DIR_EXECUTABLE)\$(_DB) FKT
start message server
#_MS = msg_server.exe
Start_Program_03 = local $(DIR_EXECUTABLE)\$(_MS) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
Start IGS
Start_Program_05 = local $(DIR_EXECUTABLE)$(DIR_SEP)igswd$(FT_EXE) -mode=profile pf=$(DIR_PROFILE)$(DIR_SEP)FKT_DVEBMGS00_erptest
start application server
#_DW = disp+work.exe
#Start_Program_04 = local $(DIR_EXECUTABLE)\$(_DW) pf=$(DIR_PROFILE)\FKT_DVEBMGS
General parameters for starting the system
#parameter created                          by: BASIS        24.12.2007 23:53:27
#SAPSYSTEM = 00
#parameter created                          by: BASIS        24.12.2007 23:53:27
#SAPSYSTEMNAME = FKT
#parameter created                          by: BASIS        24.12.2007 23:53:27
#INSTANCE_NAME = DVEBMGS00
#parameter created                          by: BASIS        24.12.2007 23:53:27
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
#parameter created                          by: BASIS        24.12.2007 23:53:27
#SAPGLOBALHOST = erptest
Start database
#parameter created                          by: BASIS        24.12.2007 23:53:27
_DB = strdbs.cmd
#parameter created                          by: BASIS        24.12.2007 23:53:27
Start_Program_01 = immediate $(DIR_EXECUTABLE)\$(_DB) $(SAPSYSTEMNAME)
Start message server
#parameter created                          by: BASIS        24.12.2007 23:53:27
MS = msgserver.exe
#parameter created                          by: BASIS        24.12.2007 23:53:27
Start_Program_02 = local $(DIR_EXECUTABLE)\$(_MS) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
Start applications server
#parameter created                          by: BASIS        24.12.2007 23:53:27
_DW = disp+work.exe
#parameter created                          by: BASIS        24.12.2007 23:53:27
Start_Program_03 = local $(DIR_EXECUTABLE)\$(_DW) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
DEFAULT:
SAPDBHOST = ERPTEST
dbms/type = mss
dbs/mss/server = ERPTEST
dbs/mss/dbname = FKT
dbs/mss/schema = fkt
SAPSYSTEMNAME = FKT
SAPGLOBALHOST = erptest
SAPFQDN = tr.delta.is
SAPLOCALHOSTFULL = $(SAPLOCALHOST).$(SAPFQDN)
SAPDBHOST = erptest
SAPTRANSHOST = erptest
DIR_TRANS =
$(SAPTRANSHOST)\sapmnt\trans
#DIR_TRANS = D:\usr\sap\trans
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
SAP Message Server for ABAP
rdisp/mshost = erptest
rdisp/sna_gateway = erptest
rdisp/sna_gw_service = sapgw00
rdisp/vbname = erptest_FKT_00
rdisp/enqname = erptest_FKT_00
rdisp/btcname = erptest_FKT_00
rdisp/msserv = sapmsFKT
rdisp/msserv_internal = 3900
rdisp/bufrefmode = sendoff,exeauto
login/system_client = 200
#GUVENLIK PARAMETRELERI
login/password_expiration_time = 90
login/min_password_lng = 6
#parameter created                          by: BASIS        25.03.2004 08:41:25
rdisp/gui_auto_logout = 10800
#parameter created                          by: BASIS        25.03.2004 08:37:47
#old_value: 3                                 changed: BASIS 25.03.2004 08:42:38
login/fails_to_user_lock = 6
#validasyon geregi, g#venligi artirma ama#i - check active but no check for SRF
#parameter created                          by: BASIS        16.06.2007 17:35:41
#old_value: 2
#changed: BASIS         14.05.2008 15:24:55
auth/rfc_authority_check = 1
#otomatik unlocki iptal eder
#parameter created                          by: BASIS        10.11.2006 17:47:15
login/failed_user_auto_unlock = 0
#AUDIT PARAMETRELER?
#old_value:                                   changed: BASIS 20.04.2005 17:13:37
rsau/max_diskspace/per_day = 1996800000
#old_value: 1000000000                        changed: BASIS 20.04.2005 17:17:01
#old_value: 0                                 changed: BASIS 20.04.2005 17:19:12
rsau/max_diskspace/local = 2048000000
#old_value: 2000000000                        changed: BASIS 28.03.2005 23:17:11
#old_value: 2                                 changed: BASIS 29.03.2005 12:09:14
#old_value: 0                                 changed: BASIS 20.04.2005 17:13:37
rsau/max_diskspace/per_file = 665600000
rsau/enable = 1
rsau/local/file = D:\usr\sap\FKT\DVEBMGS00\log\++++++++######..AUD
rsau/selection_slots = 12
#rec/client = ALL
DIR_AUDIT = D:\usr\sap\FKT\DVEBMGS00\log
FN_AUDIT = ++++++++######..AUD
#DIL PARAMETRELERI
#Turkish codepage settings
abap/import_char_conversion = 0
install/codepage/db/non_transp = 1610
install/codepage/db/transp = 1610
zcsa/installed_languages = DET
#zcsa/system_language = E
zcsa/system_language = T
zcsa/second_language = E
install/codepage/appl_server = 1610
#OS dependent
abap/locale_ctype = Turkish_turkey.28599
#DIR_PUT = D:\usr\sap\FKQ\upg\abap
   *** UPGRADE EXTENSIONS (RELEASE "701") ***
#rdisp/msserv_internal = 3900
#system/type = ABAP
INSTANCE:
SAPSYSTEMNAME = FKT
SAPGLOBALHOST = erptest
SAPSYSTEM = 00
INSTANCE_NAME = DVEBMGS00
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
DIR_EXECUTABLE = $(DIR_INSTANCE)\exe
icm/server_port_0 = PROT=HTTP,PORT=80$$
SAP Message Server parameters are set in the DEFAULT.PFL
ms/server_port_0 = PROT=HTTP,PORT=81$$
#rdisp/wp_no_dia = 10
#rdisp/wp_no_btc = 3
#rdisp/wp_no_enq = 1
#rdisp/wp_no_vb = 1
#rdisp/wp_no_vb2 = 1
#disp/wp_no_spo = 1
rdisp/wp_no_dia = 12
rdisp/wp_no_vb = 3
rdisp/wp_no_vb2 = 0
rdisp/wp_no_enq = 1
rdisp/wp_no_btc = 3
rdisp/wp_no_spo = 1
#PERFORMANS PARAMETRELERI
#parameter created                          by: SAP*         08.08.2001 10:30:18
abap/fieldexit = yes
#parameter created                          by: ALPER        13.10.2000 18:24:16
install/collate/active = 1
rdisp/max_wprun_time = 25000
MEMORY_NO_MORE_PAGING dump nedeniyle
#parameter created                          by: BASIS        27.12.2006 17:00:22
rdisp/PG_MAXFS = 262144
abap/heap_area_nondia = 2000000000
rdisp/PG_SHM = 16384
rdisp/ROLL_SHM = 32768
#'STORAGE_PARAMETERS_WRONG_SET' or 'TSV_TNEW_PAGE_ALLOC_FAILED'
#Note 552209 - Maximum memory utilization for processes on NT/Win2000
#parameter created                          by: BASIS        30.10.2007 10:57:24
#abap/heap_area_nondia = 50000
#parameter created                          by: BASIS        30.10.2007 10:58:54
#rdisp/PG_SHM = 0
#parameter created                          by: BASIS        30.10.2007 10:58:27
#rdisp/ROLL_SHM = 625
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:49:57
dbs/mss/stats_on = 1
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:49:33
dbs/oledb/stats_on = 1
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:48:23
dbs/oledb/add_procs = 8
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:47:29
rsdb/esm/max_objects = 2000
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:47:03
rsdb/otr/buffersize_kb = 4096
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:46:21
rsdb/esm/buffersize_kb = 4096
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:18:14
ztta/parameter_area = 16000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:16:43
enque/table_size = 10000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:16:20
gw/max_sys = 2000
#Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:16:01
gw/max_overflow_size = 25000000
#Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:15:19
rdisp/max_comm_entries = 2000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:14:48
rdisp/tm_max_no = 2000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:14:20
gw/max_conn = 2000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:13:42
rdisp/max_arq = 2000
#Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:12:57
ztta/roll_area = 3500000
#parameter created                          by: BASIS        18.05.2005 09:20:25
#old_value: 90                                changed: BASIS 18.05.2005 09:22:25
rdisp/max_hold_time = 300
#parameter created                          by: BASIS        20.08.2003 12:10:20
#old_value: 6144
#changed: BASIS         03.01.2008 19:42:10
rsdb/obj/buffersize = 20000
#parameter created                          by: BASIS        20.08.2003 12:09:48
#old_value: 6000
#changed: BASIS         03.01.2008 19:42:59
rsdb/obj/max_objects = 20000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:42:11
#old_value: 250000
#changed: BASIS         30.10.2007 10:56:17
#abap/buffersize = 100000
#changed: BASIS         03.01.2008 19:40:36
#abap/buffersize = 300000
#by: BASIS 12.06.2008
abap/buffersize = 400000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:41:32
#zcsa/presentation_buffer_area = 20000000
#64 bite gectikten sonra   by: BASIS 10.06.2008
zcsa/presentation_buffer_area = 30000768
note 103747
#parameter created                          by: BASIS        08.07.2003 20:40:55
rsdb/ntab/ftabsize = 30000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:40:12
rtbb/max_tables = 500
note 103747
#parameter created                          by: BASIS        08.07.2003 20:39:15
#old_value: 20000
#changed: BASIS         03.01.2008 19:41:29
#rtbb/buffer_length = 30000
#64 bite gectikten sonra by: BASIS 10.06.2008
rtbb/buffer_length = 50000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:38:26
zcsa/db_max_buftab = 10000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:37:37
#zcsa/table_buffer_area = 50000000
#64 bite gectikten sonra   by: BASIS 10.06.2008
#zcsa/table_buffer_area = 89000000
by: BASIS 12.06.08
zcsa/table_buffer_area = 99000000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:36:54
sap/bufdir_entries = 10000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:36:12
rsdb/cua/buffersize = 8000
#note 103747
#parameter created                          by: BASIS        08.07.2003 20:34:46
#old_value: 5000                              changed: BASIS 08.07.2003 20:35:39
rsdb/ntab/sntabsize = 5500
#parameter created                          by: BASIS        08.07.2003 20:33:56
#note 103747
#old_value: 10607                             changed: BASIS 08.07.2003 20:34:58
#old_value: 10000                             changed: BASIS 08.07.2003 20:35:39
rsdb/ntab/irbdsize = 11000
#note 103747
#parameter created                          by: BASIS        08.07.2003 20:32:18
rsdb/ntab/entrycount = 40000
#old_value: 2076                              changed: BASIS 28.06.2005 19:36:21
#old_value: 5735                              changed: BASIS 28.06.2005 19:40:01
PHYS_MEMSIZE = 4096
#64 bite gectikten sonra   by: BASIS 10.06.2008
abap/heaplimit = 40894464
abap/heap_area_total = 2000683008
ztta/roll_extension = 2000683008
em/blocksize_KB = 4096
   *** UPGRADE EXTENSIONS (RELEASE "701") ***
#rdisp/elem_per_queue = 2000
#auth/auth_number_in_userbuffer = 9000
#snc/enable = 0

Hi Srikishan;
You are right. The problem was releated with secstore. I found a SAP note ( Note 1532825 - Deleting SECSTORE entries during system export/system copy). I created the program which ise mentioned in the note and than run it. After that everything seems ok now.
Thanks for your help and interest
Best regards
Noyan

Sender RFC adapter Error- request was null while trying to extract it.

Hi All,
I have a scenario running in Production(PI 7.0 system) where SAP ECC sends RFC request through sender RFC adapter. The scenario was working fine but now I am getting the below error in default trace and I couldn't see any error in communication channel monitoring.
java.lang.Exception: RfcServer[BAS_ECC_RFC_Snd]1[AFSenderD] request was <null> while trying to extract it.
I have gone through the below thread and performed a full cache refresh but it didn't help :
[NULL]
I have gone through SAP note:730870 and I couldn't get any help on this error. Can you please suggest your ideas to solve this issue.
Thanks & Regards,
Laawanya

Hi Lawanya,
Check you RFC and input data , whether the RFC call is able to get the data from ECC or not.
you can test the same RFC in ECC with input data and you can check whether the RFC in ECC is return the value or not.
I gues in your case the RFC in ECC is not return any data to PI.

Error when sending message: 404 not found

Hi,
New to XI, practicing file to jdbc scenario. File is pickedup from the source folder but nothing appearing on the receiver end ms access database.
In the Component Monitoring, tried sending message manually with all the right info in Integration engine, getting an error message saying:
"Error when sending message : 404 not found"
Also tried in Adapter Engine and the result same.
Before doing this scenario, I tried file - file scenario then also the sender file pickedup from source folder but nothing happend at the receiver end.
Any idea's?? what might be the issue????
Thanks,
Venu.

Hi Venu,
"404 is a not found error", plz make a check of your URL you're using is correct? do you use the right port? Normally the port is 80<SystemNo>, so rather 8001 than 7001.
Also check in transaction SICF, if the node /sap/xi/adapter_plain has been activated, if not, activate it and try again.
If you are testing sending the message to the Adapter Engine, then the Send Message URL should be like this:
http://<server>:<J2EEport>/MessagingSystem/receive/AFW/XI
For your error, refer to the following threads:
Unable to find an associated SLD element
Unable to refresh cache contents in XI.
Unable to find an associated SLD element
Also check that the Adapter Engine is successfully registered in the SLD. To do this, call the Content Maintenance function in the SLD as follows:
http://<sld-host>:<sld-j2ee-port>/sld u2192 Administration u2192 Content Maintenance.
Select XI Adapter Framework.
Thirteen associations have to be registered.
(Source: https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2498bf90-0201-0010-4884-83568752a857)
If you can't find all the associations, then you will have to create the associations manually.
This is a very good blog which answers ur question:
check this weblog
https://weblogs.sdn.sap.com/pub/wlg/4061?page=last&x-showcontent=off [original link is broken] [original link is broken] [original link is broken]
Regards,
Vinod.

Error in RFC call, after unicode conversion of ERP

Hi,
We have just converted our ERP system to unicode. And we are using xMII 11.5. When i am calling a RFC thro' the BLS, it throws me this error
[ERROR]: RFC Execution Error: An invalid XML character (Unicode: 0x0) was found in the element content of the document.
The same error for all the RFC's i call.
But when i execute the BAPI as such in se37, in ERP , its fine.
What could be the reason for this?

Hima ... try this
http://<server>/Lighthammer/JCOProxy?Mode=Reset

Synch. RFC call error - No Sender Found

Similar Messages

Maybe you are looking for