cancel
Showing results for 
Search instead for 
Did you mean: 

Error in BW -> (Proxy) -> XI ->(Receiver SOAP)-> Backend Webservice

former_member191528
Participant
0 Kudos

Hello All,

I am getting the following error in PI 7.1 for almost all of our scenarios. We have a simple scenario which is BW -> (Proxy) -> XI ->(Receiver SOAP)-> Backend Webservice. The scenario was working fone for a long time but today we started getting the following exception. Can anyone guide us on the steps to resolve the issue.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- 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.engine.interfaces.messaging.api.exception.ConfigException: ConfigException in XI protocol handler. There is no connection registered at the Messaging System for adapter type: SOAP_http://sap.com/xi/XI/System</SAP:AdditionalText>

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

I tried running an already existing scenario and it is also giving the same error.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- 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.engine.interfaces.messaging.api.exception.ConfigException: ConfigException in XI protocol handler. There is no connection registered at the Messaging System for adapter type: RFC_http://sap.com/xi/XI/System</SAP:AdditionalText>

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Thanks.

Kiran

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

The error seems saying there is something wrong with your SOAP adapter, then you need to check the audit log to see which step the error occur.

The other area to check the java stack log using log viewer.

Also you need to collect all the system changes related to your scenario, to see if there is any most recent change cause the problem or not.

Regards.

Liang

Former Member
0 Kudos

Hi Kiran,

Have you checked the connection from your back end system to PI, like the LCRSAPRFC, SAPSLDAPI RFC destinations, and SXMB_ADM (int. engine configuration, including the HTTP RFC destination to PI server) whether they are working properly?

Have some one changed the password of the user ID PIAPPLUSER of the RFC destinations? Have the user got locked?

Regards,

Lim...

former_member191528
Participant
0 Kudos

Hello Lim & Liang,

The issue got resolved. I had to actually restart the J2EE instance by going in smicm and AS Java soft shutdown with restart. We were facing this error even for our RFC adapters.

Thanks.

Kiran