on 2006 Feb 15 11:32 AM
Hi,
I am using soap(3rd Party system) -> XI -> Proxy(R/3). We are using XI3.0 Support pack 13.
I will be using the Function Module to create the documents and trap the errors in the proxy and
The result will be sent back to the 3rd party system.I am experiencing the below problem when
ever there is an error in the function module(HTTP_RESP_STATUS_CODE_NOT_OK-500). R/3 is not able to
send the error status back to the 3rd party.If the data from the source system is proper then i am able to see the sucess message sent from R/3 to 3rd Party.
I have checked the SXMB_ADM and configuration in integration engine(R/3)
.The Role of the system is "Application System" .I am pasting the error message for reference. Do we
need to configure anything in SLD.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><!DOCTYPE html PUBLIC"-//W3C//DTD HTML
4.01Transitional//EN"> <html> <head> <title> 500 Internal Server Error
</title> <META http-equiv="Content-Type" content="text/html;charset=UTF-8">
<style type="text/css"> body {
font-family:tahoma,helvetica,sans-serif;color:#333333;background-color:#FFFF
FF; }td {
font-family:tahoma,helvetica,sans-serif;font-size:70%;color:#333333; } h1
{
font-family:tahoma,helvetica,sans-serif;font-size:160%;font-weight:bold;marg
in-top:15px;margin-bottom:3px;colo r:#003366; }h2 {
font-family:verdana,helvetica,sans-serif;font-size:120%;font-style:italic;fo
nt-weight:bold;margin-top:6px;marg in-bottom:6px;color:#999900; }p {
font-family:tahoma,helvetica,sans-serif;color:#333333;margin-top:4px;margin-
bottom:4px; }ul { font-family:tahoma,helvetica,sans-serif;color:#
333333;list-style-type:square;margin-top:8px;margin-bottom:8px; }li {
font-family:tahoma,helvetica,sans-serif;color:#33333;margin-top:4px; }.empha
size .note a{
font-family:tahoma,helvetica,sans-serif;text-decoration:underline;color:#
336699; }a:visited a:hover { text-decoration:none; }
</style> </head> <body> <table cellpadding="0" cellspacing="0" border="0"
width="100%"> <tr> <td> <h1> Error when processing your request </h1> <br>
<h2> What has happened? </h2> <p> The URL
http://sssc14.in.u1609.unilever.com:8000/sap/xi/engine/ was not called due
to an error. </p> </td> </tr> <tr> <td> </td> </tr> <tr> <td
class="emphasize"> <strong> Note </strong> <br> <ul> <li> The following
error text was processed in the system HS1 : <b> Customer MAS789 has not
been created </b> </li> </ul> <ul> <li> The error occurred on the
application server sssc14_HS1_00 and in the work process 1 . </li> </ul>
<ul> <li> The termination type was: ERROR_MESSAGE_STATE </li> </ul> <ul>
<li> The ABAP call stack was: <br> Form: KNA1_LESEN of program
SAPMF02C<BR>Form: DEBITORENSTAMM_LESEN of program SAPMF02C<BR>Module:
KONTO_LESEN of program SAPMF02C<BR> </li> </ul> </td> </tr> <tr> <td>
</td> </tr> <tr> <td> <p> </p> <h2> What can I do? </h2> <ul> <li> If
the termination type was RABAX_STATE, then you can find more information on
the cause of the termination in the system HS1 in transaction ST22. </li>
</ul> <ul> <li> If the termination type was ABORT_MESSAGE_STATE, then you
can find more information on the cause of the termination on the application
server sssc14_HS1_00 in transaction SM21. </li> </ul> <ul> <li> If the
termination type was ERROR_MESSAGE_STATE, then you can search for more
information in the trace file for the work process 1 in transaction ST11 on
the application server sssc14_HS1_00 . In some situations, you may also need
to analyze the trace files of other work processes. </li> </ul> <ul> <li> If
you do not yet have a user ID, contact your system administrator. </li>
</ul> <br/> <p class="note"> Error code:
ICF-IE-http-c:120-u:RFCUSER -l:E-s:HS1-i:sssc14_HS1_00 -w:1-d:20060215-t:133
046-v: ERROR_MESSAGE_STATE-e: </p><br/> <p> HTTP 500 - Internal Server Error
<br/> <p> Your SAP Internet Communication Framework Team </p> </td> </tr>
</table> </body> </html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 500 with the description
Internal Server Error XML element
Envelope missing in SOAP message
header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Thanks
Sekhar
Hi,
please have a look at note 804124. This should help you to solve the problem. Additionally I think you might be having some problems with the hostname definitions.
Check for that the following notes
750511
677118
654982
434918
regards, Jaime
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rajasekhar,
for error sending you should create fault message types in your interfaces and regenerate the proxies. You will get an exception in the execute method of your proxy class.
I dont understand which function module you are speaking about. Your inbound proxy is a ABAP class.
Regards,
Udo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
66 | |
10 | |
10 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.