Showing results for 
Search instead for 
Did you mean: 


Former Member
0 Kudos

Hi All,

I'm getting the below error in SXMB_MONI. I get this for all the scenarios..


Kindly let me know your valuable inputs...



Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Hi Nazim,

Just check the mentioned possibilities for your error one by one:

1.Did you maintain Client, userid, password, and lang information in SICF transaction -> sap/xi/engine? Double click on service and check whether you have entered correct information.

2.Then you might check the roles of the XIISUSER in SU01. In some case there are some double roles, i.e., two times the role SAP_XI_IS_SERV_USER assigned. One might have the date of the last update, the other one might have apparently the older version. Delete the older roles manually and the error should disappear. send messages to xi you need a service id / pwd which is specific to your landscape usually its xiappluser. Contact your basis group for password.


- Activated all services on the r3 system.

- Create HTTP connection to XI from r3

sm59-> http connetons to r3

- let us say you have created a HTTP connection in the integrationserver_XI, make sure in its settings the prefix path is set to /sap/xi/engine?type=entry. Also check its log on credentials, you can use xiappluser.

- IN Integration builder, receiver communication channel make sure you have entered proper

host service number

path = /sap/xi/enigne?type = receiver.

5. It might also be that you have authorization problems with your XISUPER. In the visual administrator and in ABAP SU01, make your XISUPER has all the necessary(SAP_SLD* and SAP_XI*) roles assigned to it. If not, try to assign these and see if this can be of any help.

6. can you also try the following;

Visual Admin -> start the service,


Please go through the followings links also :


I hope the info provided help you solve your error.



Active Participant
0 Kudos

Hi Nazim...

Salawalaykum...vijaya is right...

check this

The prerequisites to configuration for ABAP Proxy include: (landscape dependent)

1. The business systems should be based on SAP Web AS 6.20 and SAP Web AS 6.20 kernel patch level above 1253

2. You have installed the XI Add-On in each of these business systems as described in the Installation Guide SAP Exchange Infrastructure 3.0

3. The business systems and your central Integration Server are maintained in the System Landscape Directory (SLD).

Configuration required on the Business System:

1. Create HTTP connection in the business system.

Configuration Details:

Technical Setting:

1. Following Inputs are required for technical setting

1 Connection Type: H

2 Target Host: System name

3 Service Number: HTTP Port name

4 Path Prefix: /sap/XI/engine/?type=entry

Logon Security

On the Logon/Security tab page, enter the following logon data:

1 User: XIAPPLUSER (for example); this user should represent the sending business system (see also the SAP XI Security Guide under Service Users for Message Exchange).

2 Password: the password you have specified for this user

3 Client: SAP XI Integration server

4 Language: Language required

2. Configuration Business system as local Integration Engine.

1. Goto Transaction SXMB_ADM

2. Choose Edit --> Change Global Configuration Data.

3. Select Role of Business System: Application system

4. Corresponding Integration server: dest://<HTTPDESTINATION>. Here <HTTPDESTINATION> SAPISU_XID created in step 1. Dest://SAPISU_XID.

5. Under Specific Configuration Data you can specify additional configuration data

1.Select the relevant category under Specific Configuration Data.

2.Choose Change Specific Configuration Data.

For ABAP Proxies, Add the following configuration:

1.Category RUNTIME

2.Parameters: IS_URL

3.Current Value: dest://SAPISU_XID

Configuration of the Integration Engine

3. Connection between Business System and System Landscape Directory

1. Create RFC destination (TCP/IP) LCRSAPRFC and SAPSLDAPI for the SLD connection.

1.Execute transaction SM59 in the business system.

2.Choose Create.

3.Enter at least the following:

1.RFC Destination: LCRSAPRFC

2.Connection Type: T

3.Description: <your description>

4.Choose ENTER.

5.Choose the Technical settings tab page and do the following:

6.In the Program ID field under Registered Server Program, enter LCRSAPRFC

7.This program ID must correspond to a program ID specified in the RFC engine settings of the SAP J2EE Engine on the Integration Server host.

RFC Destination

2. Maintaining the SAP J2EE Connection Parameters for LCRSAPRFC and SAPSLDAPI in SAP J2EE engine

1. Goto J2EE Engine

2. Choose Cluster --> Server --> Services. JCo RFC provider

3. Under RFC destination specify the following:


Gateway Host: <Integration Server host>

Gateway Service: <Integration Server gateway service>

Number of process: 3

4. Under Repository specify the following:

Application Server: <Integration Server host>

5. Choose Set.

3. Maintain SLD access details in Transaction SLDAPICUST

1. You can reuse this program ID for all Business systems

2. If there is HTTP error during connection, first run transaction SLDCHECK in the Business system. Also check that HTTP connection is working fine.

3. In XI Adapter use HTTP connection rather then giving R/3 input details as this is easier to transport and maintenance

4. One receiver adapter can be used for all Interfaces connecting to a Business system.

0 Kudos

Hav a look at these threads...

Former Member
0 Kudos

Hi Nazim,

Please take a look at these threads..

Hope these help you



Former Member
0 Kudos


Please can you check your pipeline URL in SLD if it's


SLD> Business system> IntegrationServer --> Pipeline URL



Former Member
0 Kudos

Hi Vijaya,

I just checked the SLD settings as suggested below ..


SLD> Business system> IntegrationServer --> Pipeline URL .

The following are the settings in my system...


- <SOAP:Envelope xmlns:SOAP="">

<SOAP:Header />

- <SOAP:Body>

- <SOAP:Fault xmlns:SOAP="">


<faultstring>Empty HTTP request received</faultstring>


- <detail>

- <SAP:Error xmlns:SAP="" xmlns:SOAP="" SOAP:mustUnderstand="1">



<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Empty HTTP query received. No message processing possible</SAP:Stack>






As you can see above I find the error message "Empty HTTP query received. No message processing possible"..

Can you suggest what could be the reason....



Former Member
0 Kudos


Please can you check in transaction SXMB_ADM-->Integration Engine >COnfiguration> Check.

Run transaction SLDCHECK