RFC & proxy adapters not working

Hi Gurus,
We have PI 7.31 single stack installed on our company.
Since the last 2 days, we are not able to have a successful communication between PI and ECC on RFC and proxy adapters.
On the previous days, weeks and months there were no issues like this one.
The error that we are getting on the message monitor is next one for our incoming proxy interfaces:
From the Message Details tab:
Status
systemError
Status Details
Receiver delivery: Cannot determine receiver channel (Cannot find the receiver channel)
Error Category
XI_J2EE_ADAPTER_ENGINE
Error Code
CHANNEL_DETERMINATION_FAILED
From the Message Log tab:
29/04/2015 14:56:42.673
Information
Trying to put the message into the send queue
29/04/2015 14:56:44.448
Information
Message successfully put into the queue
29/04/2015 14:56:44.452
Information
The message was successfully retrieved from the send queue
29/04/2015 14:56:44.456
Information
Message status set to DLNG
29/04/2015 14:56:44.496
Information
Message selected to be processed again when the receiver channel is started
29/04/2015 14:56:44.501
Error
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Channel stopped by administrative task.
For OB proxy calls, this is the error that we get in the sxi_monitor on the ERP:
Status Details column: Error Parsing PI Message
Error while calling Integration Server:
com.sap.aii.af.service.administration.api.cpa.CPAChannelStoppedException: Channel stopped by administrative task. at com.sap.aii.af.service.administration.impl.cpa.CommonCPA.checkChannelState(CommonCPA.java:57) at com.sap.aii.af.service.administration.impl.cpa.LookupManagerDelegate.getCPAObject(LookupManagerDelegate.java:86) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:487) at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
Regarding the RFC adapter, this is the error we can see in the CCM:
Error in processing caused by: RfcException: [qlaspi00.xxx|eq610q0]
    message: CPIC-CALL: SAP_CMACCPTP on convId: 00000000
LOCATION    SAP-Gateway on host qlaerp01.xxx / sapgw01
ERROR       registration of tp eq610q0 from host
            qlaspi00.xxx not allowed
TIME        Wed Apr 29 16:20:22 2015
RELEASE     721
COMPONENT   SAP-Gateway
VERSION     2
RC          720
MODULE      gwxxrd.c
LINE        3644
COUNTER     5492
    Return code: RFC_SYS_EXCEPTION(3)
    error group: 102
    key: RFC_ERROR_COMMUNICATION
Exception raised by qlaspi00.xxx|eq610q0
On the SM59 tx in the ERP the test connections are failing for the RFC destinations that we are using on this environment, and these were working in the past.
Also, BASIS team notify us that the programs are registered so they don't know that else to do on their side.
The actions I took were:
CPA full refresh cache
Restart all PI components (done by BASIS team)
Stop and start channels
Inactivate and Activate channels
Please notice that all these processes were working in the past and there were NO modifications on the same.
Where can I continue looking on these errors to find the issue?
Any help will be very appreciated!
Thanks in advanced!
Regards.

Claudio
The error indicates that the channel has been stopped. Did you check the administrative logs in the comm channel monitor to see if someone or an ATP schedule has stopped the channel?
Rgds
Eng Swee

Similar Messages

Server proxy is not working

Hi Experts,
I have a scenario from jdbc to SAP.I have made serverproxy.The proxy was not working.I have test the proxy backend it is working fine,but i am staring jdbc channel the data was not insert in to the database table in sap.I have checked in sxmb_moni in sap r/3 system is showing scuessfully,but data was not sent to proxy.I have put one break point in the code for debugging the proxy.But data was not comming to breakpoint.Kindly help me.
Thanks
Ravi

Hi,
Make sure that you have not done any changes in your XI structure recently otherwise regenerate the proxy and then try agin.
Secondly if you have not done any changes then it's ok. Just one thing, have you used Commit Work just after modifying/inseting the value into database table. If not use this and then try again.
It seems that smoethig went wrong at R3 side because you said data is successful in R3 MONI, so data is reaching to R3 but not going into proxy.
When you kept the break point then were you able to see the debugger screen in R3?
Regards,
Sarvesh

Proxy was not working in sap r/3

Hi All,
I have a scenario from jdbc to SAP.I have made serverproxy.The proxy was not working.I have test the proxy backend it is working fine,but i am staring jdbc channel the data was not insert in to the database table in sap.I have checked in sxmb_moni in sap r/3 system is showing scuessfully,but data was not sent to proxy.I have put one break point in the code for debugging the proxy.But data was not comming to breakpoint.Kindly help me.
Thanks
Ravi

Hi ,
Please try with this link.
http://ecohub.sdn.sap.com/irj/scn/index?rid=/library/uuid/b0dec9f5-e9a0-2b10-c1a8-e355d01af932&overridelayout=true

RFC SAPXPG_DBDEST_ DBHOST not working

Dear Experts,
RFC SAPXPG_DBDEST_<DBHOST> not working in our Production system (cluster), due to this I am not able to take backup from DB13.
I have updated latest "sapxpg" in /usr/sap/<SID>/exe/run still it is not working.
Any idea????????
Regards,

Po ssible points of this error:
1) After downloaded this file you have to RUN ./root.sh in kernel.
2) check the environment variable for given path of backup.
3) Also check the RFC connection before schedule the job.

R/3 Proxy is not working

Hi XI Gurus,
Scenario:
The overview of the scenario is as follows.
1.legacy system will send file to XI which will send it to SAP via a ABAP Proxy.
2.The data is then validated in a control program(r/3) as per the various validation rules.
3.The validated data is then send back to XI via ABAP Proxy.
4.XI creates and posts the IDocs in SAP using the validated data.
Problem:
The file is coming successfully to ABAP proxy.
But, it is not returning back to XI(step 3).
This whole configuration was working successfully earlier.
Suddenly , now it is not working.
Even we are not able to Debug these XML Messages.
Any help in this matter will be very usefull.
Regards.
Santosh.

Hi Santosh,
1. Pls do check whether your o/b proxy to XI is holding all the settings for sending the data in source system(R/3).
2. Have you provided the explicit 'Commit Work' statement after the outbound proxy?
3. Check in the debugging of the outbound proxy triggering program to see there is enough data to get into the place where the proxy is triggered.
4. Also check whether the queues for the outbound proxy is registered.
5. Check in the SXMB_MONI of your R/3 system which acts as a sender to see whats happening to your messages if step 3 mentioned was successful.
6. Check whether your RFC destination to the XI system is not changed recently like the service/CPIC user and its password.
Cheers
JK

RFC connections do not work after system restart

Hi PI experts!
We're facing a problem with our PI 7.0 system. After each restart of the system, all RFC sender communication channels do not work. When testing the connection in the sending SAP system, the connection test fails. Currently we workaround the issue by manually restarting the RFC adapter after system restart.
Does anybody has any idea how th fix that problem? <<text removed>>
Cheers,
Matthias
Edited by: Matt on Apr 29, 2009 3:26 PM - don't offer points

Mathias,
Your problem is due to the fact that SAP is not up and running when XI restarts.
there is a parameter in RFC adapter that you can modify in order to fix that
Please, see the following link and let me know: /people/community.user/blog/2006/09/21/xi-rfcadapter-reconnect-issue
best regards,
David

File Attributes from App Server by RFC (GET_FILE_ATTRIBUTES does not work )

Hello,
We have an Objects application that is started through an RFC BAPI call from a Java app. The Java app. passes a file to the BAPI. We want to test, as efficiently as possible, if the file is 0 bytes long. We have tried /epsf/get_file_attributes but there is a problem with it being called remotely. We have Remote Enabled the function module. Local tests work fine (GUI User), but when it is called by the Bapi(Technical User) we receive sy-subrc = 2. I think it is referring to a 'Communication Error'.
I found a nice class, CL_GUI_FRONTEND_SERVICES for the workstation server, but nothing comparable for the application server.
Help is greatly appreciated as I am pulling my hair out.
Best Regards,
Mark Lengel

Hello Andreas,
The GET_FILE_ATTRIBUTES fm is also from the EPS Function Group and provides the file size, it just does not work when called from Rfc/Bapi. Won't the GET_DIRECTORY_LISTING fm just return directory info ?
I am afraid I will have to resort to the OPEN, READ, CLOSE DATASET steps in order to check for a zero length file.
Regards,
Mark

Java webstart proxy bypass not working

java webstart does not work through proxy as the jar files is not getting downloaded. most simple solution would of course be to bypass the proxy for the target server (by entering the server in the system network preference panel). however, that does not work. apparently this bypass is not taken into account by java webstart.
if i remember correctly there once was a possibility to set such things (proxy etc.) in java webstart preferences. this is not existing any more.
how can i solve the problem?
tia
tobias (very desperate)

Hi,
Thanks a lot for your reply, Prateek.
I have already checked SAP Note 1142580 - "Java Proxy is not processing messages in parallel" where they ask to modify the ejb-jar.xml. However, on performing the change in ejb-jar.xml and while building the EAR, I get the following error:
Error! The state of the source cache is INCONSISTENT for at least one of the request DCs. The build might produce incorrect results.
Then, on going through the SAP Note 1142580 again, I realised that the SAP Note 1230721 also should be looked onto which will be needed for generating the Java proxy from Message Interfaces in IR for parallel processing.
Kindly help me if any of you have worked on such a scenario.
Thanks in advance,
Regards,
Rosie Sasidharan.

Java Proxy Generation not working - Support for Parallel Processing

Hi Everyone,
As per SAP Note 1230721 - Java Proxy Generation - Support for Parallel Processing, when we generate a java proxy from an interface we are supposed to get 2 archives (one for serial processing and another suffixed with "PARALLEL" for parallel processing of jaav proxies in JPR).
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1230721
We are on the correct patch level as per the Note, however when we generate java proxy from the IR for an outbound interface, it genrates only 1 zip archive (whose name we ourselves provide in the craete new archive section). This does not enable the parallel processsing of the messages in JPR.
Could you please help me in this issue, and guide as to how archives can be generated for parallel processing.
Thanks & Regards,
Rosie Sasidharan.

Hi,
Thanks a lot for your reply, Prateek.
I have already checked SAP Note 1142580 - "Java Proxy is not processing messages in parallel" where they ask to modify the ejb-jar.xml. However, on performing the change in ejb-jar.xml and while building the EAR, I get the following error:
Error! The state of the source cache is INCONSISTENT for at least one of the request DCs. The build might produce incorrect results.
Then, on going through the SAP Note 1142580 again, I realised that the SAP Note 1230721 also should be looked onto which will be needed for generating the Java proxy from Message Interfaces in IR for parallel processing.
Kindly help me if any of you have worked on such a scenario.
Thanks in advance,
Regards,
Rosie Sasidharan.

JMS & File adapters not working after SPS20 update

Hello,
after an update to SPS20, which was proposed by SAP support to resolve an
issue with the CPA cache, the File adapter sender and receiver and the
JMS adapter sender are not working any more, however JMS receiver
adapters are still functional. In communication monitoring the error
message for the file receiver is:
Message processing failed. Cause:
com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in
method process.
resp. for the file sender:
Attempt to process file failed with
com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in
method process.
and for the JMS adapter I006_GX1TG_JMS_Sender:
Error while processing message 'db056357-5232-4c35-028e-bc51fa858038';
detailed error description:
com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException:
Exception in method process.: BaseEJBException: Exception in method
process. at
com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:95)
when invoking an ftp sender channel, polling works, the files are
retrieved from the server, but after that, we get an error. What could be
the cause of this behaviour?
log & trace files could be provided.
Thanks,
Gordon
points will be rewarded ***

Hi Gordon,
Patch 9 for XI 3.0 SP20
SAPXIAFC20P_9
contains a few fixes for the file adapter,
e.g., it is strongly recommended by SAP to apply the note :-
Note 1083488 - XI FTP/JDBC sender channel stop polling indefinitely(04/04S)
Regards
Kenny

ABAP proxy Connection not working in ECC60

Hi All,
We have created the proxies in SPROXY and using it in the report..
All the proxy related configuration are done in LPCONFIG, since SOAMANAGER is not available in this version.
My issue is when I try to establish a connection with a non-sap application through this report, I get HTTP 503, Service unavailable....
When I debugged the report, I see this exception from the proxy "no extended message(SOAP_ESERVER)"....
The report in higher versions works, but the connection is intermittent, which means if I try to execute report first time. I get HTTP 200 OK response.
In this system, I have made the configuration in SOAMANAGER. If I try to execute the same report second time, I get service unavailable, and this is weird. I have
checked with the non-sap application and its up and running. The non-sap application is a Java application. I have imported the SSL certificates, created the Logical port
for the consumer proxy created with the necessary transport settings..
I have done all the configurations in both the systems(lower and higher). Is there anything that I am missing here?
Could anyone suggest me why the connection is intermittent and why its not working in lower version?
Thanks in advance

Hi ,
Please try with this link.
http://ecohub.sdn.sap.com/irj/scn/index?rid=/library/uuid/b0dec9f5-e9a0-2b10-c1a8-e355d01af932&overridelayout=true

"Use system proxy settings" Not working on Mac OS X Snow Leopard

When I change the network location or when I select "Use system proxy settings" on the connetion configuration dialog.
Firefox is not using the proxy defined on the loction set on Mac OS X Snow Leopard.
I usualy change from work to home, at work I've a proxy and at home I don't, and it's a bit annoying to have to change the proxy twice a day. So I tryed this feature, but It's not working for me.
I've tryed also with Firefox 3.6 (I think) and didn't work either.

I run it from eclipse, and on debug mode i checked the value of
java.library.path, and it was ok.
Any way, how can i do what you suggested on mac?It's just a command line argument, but there's no reason to add it if your
java.library.path is ok. One of its componenents must be a directory where
your shared lib is stored, that's all. BTW, the Mac is unix based isn't it?
Shouldn't it be an .so file then? (just a wild guess)
kind regards,
Jos

After Windows 10 Pro N succesfull update all Network Adapters not working and not showing up

Hi all, After succesfully installing the new Windows 10 Pro N onto my Windows 8.1 Pro N operating system and restarting the system, I realized that all drivers are migrated succesfully, withouht any incompatibility issue, but none of the network adapters were working, so no WiFi, no LAN connection was ready to be used, checking the list of available network adapters showed an empty list. I am using a ThinkPad T520 laptop. I have tried to update all drivers from a USB, had several restarts, but no result. Any ideas I could use to get Windows 10 up-n-running with network connections? Thank you in advance, Regards, Gyula

Hello and welcome,
Do you have VPN software on your laptop? https://support.microsoft.com/en-us/kb/3084164
Z.

Communication between SOAP and java proxy does not work

Hi Group,
i want to proceed following scenario:
SOAP->XI->JavaProxy
For that i have created of the message interface of a remote function module my java proxy.
Calling the java proxy with following scenario works successfully:
RFC->XI->JavaProxy
Further, i have created in the integration engine(configuration) my wsdl file. In the SAP
Netwaever Developer Studio, i have made a standalone proxy project, that is consuming the
web service out of the wsdl file.
Testing the web service client with following example works fine:
SOAP->XI->RFC
But when i try the scenario SOAP->XI->JavaProxy, i get following rmi exception on client side:
java.rmi.RemoteException: Service call exception; nested exception is:
java.lang.Exception: Element 'Z_GPS_PING.Response' not found in response message.
at com.demo.sap.MI_WEBSRV_GPS_PING_OUTBBindingStub.MI_WEBSRV_GPS_PING_OUTB(MI_WEBSRV_GPS_PING_OUTBBindingStub.java:86)
at com.demo.test.TT_Pinger.main(TT_Pinger.java:36)
Caused by: java.lang.Exception: Element 'Z_GPS_PING.Response' not found in response message.
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.getResponseDocument(MimeHttpBinding.java:942)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1231)
at com.demo.sap.MI_WEBSRV_GPS_PING_OUTBBindingStub.MI_WEBSRV_GPS_PING_OUTB(MI_WEBSRV_GPS_PING_OUTBBindingStub.java:79)
... 1 more
In the monitoring, the execution of both directions is ok. In the response message, i can see the result of the java proxy.
Here is the result:
<ns:Z_GPS_PING.Response xmlns:ns="urn:sap-com:document:sap:rfc:functions">
<E_RETURNCODE>PINGOK </E_RETURNCODE>
</ns:Z_GPS_PING.Response>
My first thought, was, that i have a problem with the prefix, so i have changed it via xslt transformation into "rfc",
but it got the same error message.
Does anyone know, which problem we have here?
For any hint or suggestion, i would be much obliged.
Greetings,
Sigi
P.S. WAS and Sap Netweave Dev Studio is on patch level 12

Hi Group,
the SAP has solved the Problem now.
The coresponding OSS note is: 862926
(release date 18.07.05)
The reason was, that the response payload name wasn't
"maindocument". For that, the adapter didn't found the payload and returned an emty one.
Greetings,
Sigi

PI 7.11 - Alert creation for RFC Exceptions does not work

Hi folks!
In our PI 7.11 SP04 system we have created an Alert Category as well as an Alert Rule to be informed about errorneous messages in the Integration Engine (ABAP).
The scenario is synchronous SOAP Axis to sRFC, where the RFC answers with an exception that is transferred to a SOAP Fault response message.
Now we see messages with Application Errors in the Integration Engine, but no alert is created. Having a look at the alert creation log using report SXMSALERT_LOGREADER shows us that the system even does not try to create an alert for these messages. Alerts are only created for errors in the Adapter Engine.
Question:
Why does the system not create alerts in this case and how can we achieve this?
Thanx for any hint!
Kind Regards,
Volker

Hi!
Additional information for all:
When forcing an error like "receiver not found" both kinds of alerts are created: AE Alert and IE Alert. Thus in general the alert configuration and the alert rule for IE errors are correct and working - only not for RFC exceptions ....
Regards,
Volker

RFC & proxy adapters not working

Similar Messages

Maybe you are looking for