cancel
Showing results for 
Search instead for 
Did you mean: 

RFC & proxy adapters not working

former_member440449
Participant
0 Kudos

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:

StatussystemError
Status DetailsReceiver delivery: Cannot determine receiver channel (Cannot find the receiver channel)
Error CategoryXI_J2EE_ADAPTER_ENGINE
Error CodeCHANNEL_DETERMINATION_FAILED

From the Message Log tab:

29/04/2015 14:56:42.673InformationTrying to put the message into the send queue
29/04/2015 14:56:44.448InformationMessage successfully put into the queue
29/04/2015 14:56:44.452InformationThe message was successfully retrieved from the send queue
29/04/2015 14:56:44.456InformationMessage status set to DLNG
29/04/2015 14:56:44.496InformationMessage selected to be processed again when the receiver channel is started
29/04/2015 14:56:44.501ErrorTransmitting 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.

Accepted Solutions (1)

Accepted Solutions (1)

engswee
Active Contributor
0 Kudos

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

Answers (0)