Just in one line you have asked for the sun, moon and the stars. You i think don't realize the magnanimity of your question.
Errors in XI can be classified under various headers and it would not be not wise for someone to even try to give you a complete list. The closest that you can come to is https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5038. [original link is broken][original link is broken][original link is broken]
Rest all errors you can come across as you gain experience in XI.
Rest all errors you can come across as you gain experience in XI.
You will come to know regarding XI error codes and its corresponding solutions only once you face those errors. Even though you have seeen any documenation of any particular Error code or issue and if you doesnt work on that or if you didn;t face that issue you will not get an exact picture and grip..untill you face those issues directly in real time.
I will suggest you an easy way. Go to alert configuration in RWB. There you will find the complete list of error codes. It is available for raising alert for an individual error code. But I am not sure what you will be doing with it.
1) See you can easily find any error in the Communication Channel Monitoring Add Time Stamp and also in the Message Monitoring and END to END montioring.
2) If the mssages are realted to BPM you can easily find where exactly the scenario strucks in the BPM WORK FLOW in the business process engine SXMB_MONI_BPE
3) You can also view the status of messages and error information in the Message Display Tool
Also while doing IDOC scenarios based on the IDOC code you need to find solution from the Trouble shooting guide..It depends upon the ERROR CODE:: as told by Prateek.
ALso here I am providing some links as well as some HTTP Error codes. See based on this HTTP Error codes you can get an Idea and also you can apply the same solution in your case. It implies for example if it is authroization error like RFC_RESP_STATUS_CODE_NOT_OK 401 Unauthorized means there is some issue with RFC login details at which the actual HTTP error code is HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
In this way you can resolve based on some Http error codes.
*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:
u2022 Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
u2022 If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
u2022 If the error is in Adapter Engine
u2013then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
u2022 May be wrong password for user XIISUSER
u2022 May be wrong password for user XIAFUSER
u2013 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
u2022 HTTP 403 during cache refresh of the adapter framework - Refer SAP Note -751856
u2022 Because of Inactive Services in ICF u2013Go to SICF transaction and activate the services. Refer SAP Note -517484
u2022 Error in RWB/Message Monitoring- because of J2EE roles u2013 Refer SAP Note -796726
u2022 Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. u2013Because 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
u2022 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)
u2022 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
u2022 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
u2022 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 u2013 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
u2022 Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
u2022 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.
Also go through some links::[Mapping Fails for a Certain Message Type
[Message Failed on the Adapter Engine |http://help.sap.com/saphelp_nw04/helpdata/en/49/e3fb40ef74f823e10000000a155106/content.htm]
[Sending an IDoc through XI Failed |http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm]
[How to Re-Process failed XI Messages Automatically|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2728] [original link is broken][original link is broken][original link is broken];
[Some errors in an XI production environment|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5038] [original link is broken][original link is broken][original link is broken];
Also you can get some idea regarding Error while implementing proxy Interfaces::
Below are some common errors that would arise due to the configuration or connectivity errors in this scenario. Details on how to fix some of these errors are listed below.
1) While implementing Proxy scenarios, by default the connection between ECC and XI is not established. Hence, in SPROXY Tcode it says u201CNO CONNECTION TO ESRu201D. As a result we will not be able to see the ESR objects in the ECC system. To rectify this situation we need to follow the steps described in the prerequisites section of this document, which is generally the task of the BASIS team (Connecting XI and ECC systems).
[NOTE: Also, another very important step we need to follow in SLD is the creation of Technical and Business systems. While creating technical system of type AS ABAP, we need to give the details of our ECC system. Similarly, we need to create a business system of type AS ABAP in the above created technical system. Finally, we need to assign this business system to our software component. In case the above settings are not done you are likely to get an error u201CBUSINESS SYSTEM NOT FOUNDu201D while executing the report in ECC system (Linking ESR and ID of XI).]
2) While creating proxy from our interface it asks for a package and prefix. In case we donu2019t give a prefix (Y or Z) it asks for an access key to modify the standard object class CO_SI_SENDER.
Usually 'Y' or 'Z' is for custom development and hence it tries to change the standard SAP Object.
3) If the RFC destination name is incorrectly spelt (case sensitive) in SXMB_ADM, the error shown below is likely to occur.
4) Incase the RFC desination is incorrectly configured(User Name password u2013 Authorization error) the below error would occur. HTTP_RESP_STATUS_CODE_NOT_OK
5) Authorization check failed: S_ICF_ADM with Parameters ACTVT 07.
This is an Authentication Error: S_ICF_ADM Authorization has to be given for user in ECC server for the corresponding client.
Regards::
Amar Srinivas Eli
Edited by: Amar Srinivas Eli on Mar 23, 2009 4:07 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.