Problems RFC- XI

Hi.
When i try to call a RFC function in an R3 backend, i'm getting this message :
'HTTP response contains status code 401 with the description Unauthorized XML element Envelope missing in SOAP message header (SAP XI Extension)'
What's happening?

Hi Inigo,
have you seen this document?
https://websmp201.sap-ag.de/~sapdownload/011000358700005909032005E/XI20XI30_TroublGui.pdf
there are at least a few 401 errors explained over there
have a look at it and try it
BTW
don't forget to check : INTEGRATION_DIRECTORY_HMI rfc dest
Regards,
michal

Similar Messages

Problem RFC sender

Hello,
I have a new Problem about a sending RFC in XI.
Once I send a test-RFC from R/3 se37 it reaches the rfc sender channel but there I get an error in cc-monitoring(the same is displayed in R/3 then as well).
The error says:
Processing error caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'CC_RFC_sender_RFC2JDBC' (104238c5fe4c345e8e85752a84330c5c, party '', schema 'TechnicalSystem', identifier 'E10#400')
Can you help me?
I don't understand the error.
CPA-Cache Refreshs do not work.

Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".
* Give correct appserver and gateway service details in XI.
* Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
Regards,
Prateek

Regarding Safari cookie size problem (RFC 2109)

Latest Safari versions do not comply with RFC 2109 regarding cookies size.
RFC 2109 6.3 Implementation Limits
   Practical user agent implementations have limits on the number and
   size of cookies that they can store. In general, user agents' cookie
   support should have no fixed limits. They should strive to store as
   many frequently-used cookies as possible. Furthermore, general-use
user agents should provide each of the following minimum capabilities
   individually, although not necessarily simultaneously:
* at least 300 cookies
* at least 4096 bytes per cookie (as measured by the size of the
        characters that comprise the cookie non-terminal in the syntax
        description of the Set-Cookie header)
* at least 20 cookies per unique host or domain name
User agents created for specific purposes or for limited-capacity
   devices should provide at least 20 cookies of 4096 bytes, to ensure
   that the user can interact with a session-based origin server.
Latest Safari violates this RFC and has 4 KB limit on total size of all cookies for each domain.
It causes severe problems with many Web Applications including Web Applications which use Microsoft SAML2 federated security.
Safari must support up to 20 cookies per domain and each cookie must be at least 4096 bytes long.
Where can I get a fix fro Safari.
This was tested with Safari for MS Windows, but people reported same problem for many other platforms.

You can provide feedback to Apple here > Apple - Safari - Feedback

XML Problem: RFC Function with XSTRING or raw table (4.6C)

hello,
I have a serialized XML-Document, i.e. a xstring or a raw table. Now I want to write a RFC Function Module that sends/receives this data. I'm running on 4.6C. Is this possible under 4.6C?
I've managed to write a Function module with appropriate parameters (XML in a raw table) that works fine, but I can't declare it as a remote function module. Is there a standard method of importing binary XML Data via RFC in 4.6C?
Regards,
Alexander Schulz

Can you please share the answer?

ChaRM: Technical Problem RFC Module /TMWFLOW/TASK_START

Hi
I am testing ChaRM in Solution Manger 7.1 with three dummy systems.
I am trying to change ZMHF to "Production" and get the following error:
I wasn't getting this last week so not sure what has caused this to start appearing?
Any ideas???
Thanks
Shaun

This is due to the Production system being setup with an incorrect Transport Domain in SMSY

Exception class: RFC not found

Hi,
Do you know whether there is an exception class in web dynpro java that i can catch in case the RFC is not found in the backend system?
Thanks and regards,
Nada

Thank you!
Are the mentioned exceptions general exceptions if something is going wrong with the execute() method or they are specific for the problem 'RFC not found in the backend).
So I need this specfic information that the RFC is not found in the backend.

Sending IDocs via RFC Adapter

Hello!
In an itegration scenario, we need to send (non XML) IDocs via RFC to a remote R/3 system (4.6C). As we don't want to get these IDocs persisted on the target system, it's intended to address the remote functions directly.
Now the problem:
- RFC Adapter only works with XML IDocs (so we cannot transfrom back to native IDoc)
- IDoc-Adapter sends native IDocs, but only to IDOC_INBOUND_ASYNCHRONOUS on target system (and the Idocs will be persisted)
In a next step, we also tried to implement a workaround with a local ABAP proxy on the XI system. But it seems, that it's not allowed to call a abap proxy locally on the integration engine.
Has anybody any idea to solve this problem? Maybe I'm thinking too complicated Help is highly appreciated!
Cheers,
Matthias

Hi,
what kind of document you want to post?
most (many) IDOCs use BAPIs so you can
just call the BAPI (RFC) from XI
>>>But it seems, that it's not allowed to call a abap proxy locally on the integration engine.
you can call it on another client on the XI
(which is set as application system in SXMB_ADM)
Regards,
michal

Call different RFC Functions depending on variable

Hi,
I have to implement following requirement:
My program generates a report for the user and the user can choose which data he wants to have.
Depending on the user decissions, I have to use different RFC - Functions to get the data.
I have the name of the RFC Function und I want to call the RFC Function with this name dynamically.
For example:
rfcName = "Z_FUNC_1";
rfc = get the object for Z_FUNC_1 somehow. This is my problem
rfc.execute();
Is there any way how to solve this? I know that I can solve this like this, but this is not the flexible way that i want:
if (whichRFC == 1) {
Z_Func_1_input rfc = new Z_Func_input();
rfc.execute();
Any ideas?
Best regards,
Peter

Dear Peter,
There are how many RFC models are you going to make? In my opinion it would be too tedious and redundant as you have to create diifferent models fo each RFC.
Instead of this you may create a single RFC and in that you can call your required RFC depending on the user selection.
It will simplify your application as well as your task.
Hope it helps!!
Warm Regards
Upendra Agrawal

EXCEPTION_ACCESS_VIOLATION error in SapJCo DLL'S

Hi All, 
I have been having EXCEPTION_ACCESS_VIOLATION errors crashing the JVM in our SapJCo Client. 
The error appears intermitant at the moment and we are still unable to replicate it on demand. I have found several references to similar issues but with no conclusive solution, eg 
JCO Client Problem
RFC ERROR
 
One recomends looking at OSS Note 774813, Ive looked for this note, but I cant find it, can someone please help me by providing Idiot proof instructions on just how to get to this note. (Im not really an idiot, just new to the SAP support portals, honest) 
Alternatively if anyone can shed some light on these type of errors it would be appreciated...below the top of the hotspot error log file. 
Cheers 
Paul 
<code>
An unexpected error has been detected by HotSpot Virtual Machine:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x4c27c57a, pid=788, tid=7212
Java VM: Java HotSpot(TM) Server VM (1.5.0_12-b04 mixed mode)
Problematic frame:
C [sapjcorfc.dll+0xc57a]
T H R E A D -
Current thread (0x4893ae50): JavaThread "pool-1-thread-2" [_thread_in_native, id=7212]
siginfo: ExceptionCode=0xc0000005, reading address 0x61733b70
Registers:
EAX=0x497ada08, EBX=0x00000501, ECX=0x00000002, EDX=0x61733b70
ESP=0x4e16f4e0, EBP=0x4e16f500, ESI=0x00000000, EDI=0x4c5f4aa8
EIP=0x4c27c57a, EFLAGS=0x00010247
Top of Stack: (sp=0x4e16f4e0)
0x4e16f4e0: 4e409a54 00000001 00000500 497ada08
0x4e16f4f0: 61733b71 497ada0a 61733b71 497ada0e
0x4e16f500: 4e16f548 4c273e5f 4c5f4aa8 61733b70
0x4e16f510: 00000001 497ada08 497ada0c 4e16f538
0x4e16f520: 00000010 4893af10 61733b70 00000000
0x4e16f530: 497ada08 00000054 00000000 00000000
0x4e16f540: 00000001 00000001 4e16f588 4c274a15
0x4e16f550: 4893af10 61733b70 00000010 00000000
Instructions: (pc=0x4c27c57a)
0x4c27c56a: fc 01 4d 18 66 89 30 03 c1 03 d1 01 4d f8 eb 19
0x4c27c57a: 0f b6 32 8b 5f 10 66 8b 34 73 01 4d fc 01 4d 18
Stack: [0x4e130000,0x4e170000), sp=0x4e16f4e0, free space=253k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [sapjcorfc.dll+0xc57a]
C [sapjcorfc.dll+0x3e5f]
C [sapjcorfc.dll+0x4a15]
C [sapjcorfc.dll+0xbc9f]
j com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeExecute(Lcom/sap/mw/jco/JCO$Client;Ljava/lang/String;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Ljava/lang/String;Ljava/lang/String;I)V+0
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeExecute(Lcom/sap/mw/jco/JCO$Client;Ljava/lang/String;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Ljava/lang/String;Ljava/lang/String;I)V+0
v ~C2IAdapter
J com.sap.mw.jco.JCO$Client.execute(Ljava/lang/String;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Lcom/sap/mw/jco/JCO$ParameterList;Ljava/lang/String;Ljava/lang/String;I)V
</code>
 
Edited by: Paul Henry on Aug 20, 2009 9:44 AM

You are supposed to provide the java source code that lead to this system error, we are not assembler debuggers! but we can find a workaround if you display your code

Mapping Error :JCO_COMMUNICATION_FAILURE

Hi All,
Scenario: File ->XI->File
I am getting following error in Mapping (in Runtime)
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error opening an RFC connection.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>&quot;COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection.</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
This is a simple Message Mapping. Before this error occurs the message is going to Queue with "Running Status" But it never ends.
When I restart the Queues , it goes to SYSFAIL status with the error "XI Error JCO_COMMUNICATION_FAILURE.MAPPING: Queue"
Can anybody come accross this situation ?
Is it because of some Java components are not running ?
Thanks in advance,
Regards,
Moorthy

Hi,
>>>>Can anybody come accross this situation ?
of course:)
>>>Is it because of some Java components are not running ?
no, it's rather because of memory problems + RFC cache
but just have a look at our previous answers
(recreating RFC dest + Udo's answer)
Jco System Failure
Regards,
michal

No_messaging_url_found: Unable to find URL for Adapter Engine

Hi,
I am facing the same problem. I have configured a RFC-File scenario.
I get the error"no_messaging_url_found: Unable to find URL for Adapter Engine af.<SID>.<server>"
and <INTERNAL.AE_DETAILS_GET_ERROR>
I get the error "no_messaging_url_found: Unable to find URL for Adapter Engine" when I execute the Function Module SAI_AE_DETAILS_GET.
This error occured in the line 235( sap_xi_adapter_services = sld_accessor->associators( iref = sap_xi_adapter_framework assocclass = 'SAP_HostedXIAdapterServi) of the FM.
The value is not filled and i get the error mentioned.
I have gone through thread and verified all the points mentioned.
I have checked SXI_CAHCE,there are no locked users in RSUSR200,
SXI_CACHE, Goto->AdapterEngine Cache, I have an entry af.<sid>.<server>
In SLD,Technical Landscape,Exchange Infrastructure I have the entry <SID>.<Server> against the Adapter Engine
But as was mentioned in the thread the line 241 of the Fucntion Module has 'adapterType' and not 'Adaptertype' as in the exchange profile.I did not try changing 'a' to 'A'.
Could you please let me know how to solve the problem.
Thanks in advance.

Hi Vani,
Check the pipeline URL in the SLD
Business System->URL
It should be
http://host:HTTPport/sap/xi/engine?type=entry
Just check this thread- may be useful-
File Adapter - Sender Problem
RFC adapter - AE_DETAILS_GET_ERROR - no adapter engine
https://websmp103.sap-ag.de/~sapdownload/011000358700002757652005E/HowtoMintorAF.pdf
Hope this helps,
Regards,
Moorthy

What is Necessity of TCODE BD87 in ALE /Idocu0092s?

What is Necessity of TCODE BD87 in ALE /Idocs?

Hi,
If one IDOC is created on the system, but due to some problem (RFC not working or System is down) it is not received by other system.
So we can reprocess the same IDOC by using this T-code after solving the system problem. There is no need to create new IDOC.
Reward points, if helpful,
Sandeep Kaushik

EOIO Idoc processing

Hi,
We have an IDoc - XI - Idoc scenario. We need to mantain the order of sender Idocs in the receiver side.
If we have connections problems (RFC, ...) we lost the order in sender side and in XI Outbound processing.
We don't know if it's possible to configure something in R/3 4.6C (sender side) to avoid loosing the order when restarting the RFC connection.
When we receive Idocs in XI, and RFC connection with receiver (R/3 4.6C) is down, the message are processed correctly but are scheduled on outbound side. When the RFC connection is up, XI doesn't mantain the order of the inbound, and try to resend idocs in a different order.
Finally, we get the idocs in the receiver system with a different order respect to the sender system.
Is there any way to resolve this kind of problems?
We have seen in sap help the possibility of use EOIO queues (XBQ*), but we are not sure if it is compatible with SAP R/3 4.6c Sender and receiver systems.
Is someone experienced at this scenario?
Thank you
Best regards
Luis

How will you process the error in the backend to clear and process subsequent documents??
What version is the backend?
You will have to look at serialisation.
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a66c9507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/frameset.htm

RWB - sxmb_ifr - no messages

hi experts,
i can't see any message in rwb (-> message monitorig) and sxmb_ifr
the comunication channels are all ok, green.
in xi server i have the entries
RUNTIME parameter:Logging value :1
RUNTIME parameter:Logging_sync value :1
RUNTIME parameter:Trace_level value :3
i don't understand what occurs..
very thanks

Hi,
For your problem "rfc to jdbc -> first testing today and i can't see anything. From R3, i execute a program nothing occurs, any error.."
1) check if there are any messages entering into the XI system in sxmb_moni
2) check whether the RFC channel is active (green colour) or is it showing any errors.
3) check whether your program id is registered or not in smgw go to logged on clients see if your corresponding entry is present or not.
4) do a test connection in SM59 to see if RFC destination is working.
5) Check sxmb_moni in R/3 system to see if atleast data is going out of R/3 or not.
6) use tcode ST22 to check for any dumps.
The above steps will help isolate the problem.
Rgds
joel
Edited by: joel trinidade on Feb 18, 2009 12:09 PM
Edited by: joel trinidade on Feb 18, 2009 12:10 PM

Regarding BD87 TCode

Can anyone brief me regarding BD87 tcode...

Hi,
BD87 is used to monitor the inbound and outbound IDoc and also can be used to process a single IDoc.
In ALE Administration choose Monitoring ..>Status Monitor (BD87), select the IDocs and then select Process. for example, creating setup tables), post the request IDoc as usual in the mirror system (meaning NOT with the report that was used in the original system). To do this, start transaction BD87 and choose "Posting" of the IDoc with status 64.
The logic for posting an application document is coded in inbound function modules. Verifying the logic of the inbound function module is the most important step for custom function modules. You verify not only that the posting function module is working correctly, but also that the logic and interface of the function module are correct. If problems exist, you might also want to debug the process one step at a time.
The IDoc created in the "Verifying the Creation of successful IDocs" section is used to test this
process. To start, execute program RBDAPP01 via SE38, or execute BD87. Then, enter your IDoc number and start the process
What is Necessity of TCODE BD87 in ALE /Idocs?
If one IDOC is created on the system, but due to some problem (RFC not working or System is down) it is not received by other system.
So we can reprocess the same IDOC by using this T-code after solving the system problem. There is no need to create new IDOC.
Thanks
Vikranth

Problems RFC- XI

Similar Messages

Maybe you are looking for