Http* Errors in XI

Most common HTTP errors occurring during XI implementations and possible tips to solve the problems.

1) Error: HTP 200 OK

Description: The request has succeeded. The information returned with the response is dependent on
the method used in the request GET an entity corresponding to the requested resource is sent in the
response; HEAD the entity-header fields corresponding to the requested resource are sent in the
response without any message-body; POST an entity describing or containing the result of the action;
TRACE an entity containing the request message as received by the end server.
Possible Tips: Have a look into SAP Note: 871959

2) Error: HTTP 400- Bad Request- ICM_HTTP_CONNECTION_FAILED

Description: The request could not be understood by the server due to malformed syntax. The client
SHOULD NOT repeat the request without modifications.
Possible Tips: May be because of huge message flow. Related SAP Notes-824554, 906435, 783515,
910649, 706563 If it is because of Queue problems have a look into SMQ2 and then go thru this blog-
How to Re-Process failed XI Messages Automatically

3) Error: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized

Description: The request requires user authentication
Possible Tips:
• Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
• If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
• If the error is in Adapter Engine
–then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE
Goto --> Cache.
• May be wrong password for user XIISUSER
• May be wrong password for user XIAFUSER
– for this Check the Exchange Profile and transaction SU01, try to reset the password -Restart the J2EE
Engine to activate changes in the Exchange Profile After doing this, you can restart the message

4) Error: HTTP 403 Forbidden

Description: The server understood the request, but is refusing to fulfill it
Possible Tips:
Path sap/xi/engine not active
• HTTP 403 during cache refresh of the adapter framework - Refer SAP Note -751856
• Because of Inactive Services in ICF –Go to SICF transaction and activate the services. Refer SAP
Note -517484
• Error in RWB/Message Monitoring- because of J2EE roles – Refer SAP Note -796726
• Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. –Because of the URL is incorrect
or the adapter is not correctly deployed.

5) Error: 404 Not Found

Description: The server has not found anything matching the Request-URI. No indication is given of
whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the
server knows, through some internally configurable mechanism, that an old resource is permanently
unavailable and has no forwarding address. This status code is commonly used when the server does
not wish to reveal exactly why the request has been refused, or when no other response is applicable.
Possible Tips:- for HTTP_RESP_STATUS_CODE_NOT_OK 404
• 404 is an HTTP response code that indicates that the resource in question couldn't be found. Usually
this is due to an incorrect URL, so it is better to cross check all URLs. Check pipeline URL in the SLD in
the business system of the Integration Server For this go to SLD->Business System-><yourIntegrtaion
Server>->Pipeline URL: It should be like this http://<host>:<port>/sap/xi/engine?type=entry Where host
is the host name of the Integration Server and port is the HTTP(8xxx) port. To verify this in Integration
Server you can do like this. Go to SXMB_ADM->Integration Engine Configuration->Choose Edit from
Menu -> Change Global Configuration Data to switch to change mode. Then select System Landscape -
Load Configuration. (This is not required always)
• Check that the port really is the ICM HTTP Port and not the J2EE port i.e SMICM then menu GOTO --
> SERVICES and check the port number for HTTP. It should be HTTP port
• If the error is Page cannot be displayed, cannot find server in https configurations Check and correct
the SSL configuration for the ABAP and the J2EE side of the system
• If the error is because of integration server when using Proxy communications then check these. i.e
SXMB_ADM->Integration Engine Configuration->Corresponding Integration Server enrty should be
dest://<Http Integration server-Destination> Where < Http Integration server -Destination > is the RFC
destination (SM59) of type HTTP connection (type H) to the Integration Server. In this case, host name,
port, and path prefix are saved in the RFC destination.

6)Error: 405 Method Not Allowed

Description:The method specified in the Request-Line is not allowed for the resource identified by the
Request-URI
Possible Tips: ICM_HTTP_INTERNAL_ERROR - Refer SAP Note 906435

7) Error: 500 Internal Server Errors

Description: The server encountered an unexpected condition which prevented it from fulfilling the
request.
Possible Tips: Have a look into SAP Notes – 804124, 807000

8) Error: The error message 503 Service unavailable Application stopped! is displayed.
Description:The server is currently unable to handle the request due to a temporary overloading or
maintenance of the server. The implication is that this is a temporary condition which will be alleviated
after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-
After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming
overloaded. Some servers may wish to simply refuse the connection.
Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
• Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --
> View on Application or restart the J2EE engine
• The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator
and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime
tab page. You see a tree in the right window with all applications if you select the APPLICATION radio
button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services
automatically.