cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Demo Error - HTTP response contains status code 404

Go to solution
Former Member

on ‎07-13-2005 2:25 AM

0 Kudos

Dear all,

While configuring the first demo on XI 3.0, I encountered the following errors when executing the scenario. The scenario is "Configuring Integration Scenarios for proxy-to-proxy communication" - Checking flight seat availability.

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

- <!-- Call Integration Server

-->

- <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>404</SAP:P1>

<SAP:P2>Not Found</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Error Report</title> <style> td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active </style> </head> <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0"> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="4" color="#666666"><b>&nbsp;&nbsp;404 &nbsp Not Found</b></font></td> </tr> <tr bgcolor="#3F73A3"> <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td> <td height="23"><img width=1 height=1 border=0 alt=""></td> <td align="right" height="23"><font face="Arial, Verdana, Helvetica" size="2" color="#FFFFFF"><b>SAP J2EE Engine/6.40&nbsp;</b></font></td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> <br><br><br><br><br><br> <p><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><b>&nbsp;&nbsp;The requested resource does not exist.</b></font></p> <p><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><table><tr><td valign="top"><b>&nbsp;Details:</b></td><td valign="top"><PRE>Go to <A HREF="/" target="_parent">main page</A> of this application!</PRE></font></td></tr></table></font></p> </body> </html></SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>HTTP response contains status code 404 with the description Not Found XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

Any pointers on this is greatly appreciated!!

Thanks,

Cyanna

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
‎07-13-2005 5:14 AM
0 Kudos

Hi Cyanna

Go through this thred it

<b>>

Hope it helps.

Regards

Arpit Seth

Show replies
Show replies
Former Member
‎07-13-2005 6:38 PM
0 Kudos

Hi Arpit,

Thanks for replying. I did look at this thread, however, I think the issue that Richard is experiencing might be different from mine. Mine is a proxy-to-proxy communication whereas Richard's was idoc related. However, I did check what Hart mentioned (on the J2EE Admin to make sure XI related services and apps are running), and they are working properly for my system. I did a test on the RFC destination for the integration server via sm59, and noticed it returned the same error stating the object is not found.

~response_line HTTP/1.1 404 Not Found

~server_protocol HTTP/1.1

~status_code 404

~status_reason Not Found

connection close

pragma no-cache

cache-control no-cache

expires 0

content-type text/html

content-length 1539

server SAP J2EE Engine/6.40

date Wed, 13 Jul 2005 17:35:58 GMT

Would this be my problem instead? If so, any idea how I can resolve this?

Thanks in advance for any help on this!

Regards,

Cyanna

MichalKrawczyk
Active Contributor
‎07-13-2005 6:54 PM
0 Kudos

Hi Cyanna,

take a look at question 17:

/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions

if you change it to dest:// in SXMB_ADM

(in SXMB_ADM - integration engine configuration)

try your proxy once more

also make sure your application systems are set as application systems in SXMB_ADM - integration engine configuration

Regards,

michal

Former Member
‎07-13-2005 7:24 PM
0 Kudos

Hi Michal,

Thanks for your response! I followed the instruction on question 17, and recheck my configuration of the integration engines (for client 105/106/107 as stated in the SAp demo), and change the 'Corresponding Inte. Server" back to the format "dest://<RFC destination for inte. server>". I had that initially, and decided to try using the entire http path (http://<local_host:J2EE port>/sap/xi/engine/?type=entry). Neither of them worked.

Do I need to restart or reactivate any components after I changed the corresponding integration server value after the configuration?

Since the above did not work, so I went back to the possible root cause (Integration Server RFC destination). I have set up the integration server RFC destination in client 100, with the following parameters:

Under Technical Settings:

Host: <local_host>

path prefix: /sap/xi/engine/?type=entry

service no.: 5<instance>00

Under Logon/Security:

Logon Precedure: chose Basic Authentication

Client: 100

Login ID : XIAPPLUSER

Afterwards, I did the "Test Connection", and it returns the 404 error.

In addition, on the application systems side (in the demo, the case will be client 105/106/107), I have ensured the business systems are set to "application system".

Any help is greatly appreciated!

Thanks much!

Regards,

Cyanna

MichalKrawczyk
Active Contributor
‎07-13-2005 7:30 PM
0 Kudos

hi,

service no.: 5<instance>00

it should be 80... (http port not j2ee)

check with TCODE SMICM -> GoTo -> Services

and check http port

then test your proxy again

Regards,

michal

Former Member
‎07-14-2005 12:59 AM
0 Kudos

Hi Michal,

Thanks so much for your help! I greatly appreciated it.

So the solution to my issues is as followed:

I changed the http port in both sm59 and under the communication channel for the XI adapters in integration directory, and now everything is working fine.

The http port as Michal has indicated is the ABAP port 80<instance>.

Thanks again, Michal!!

MichalKrawczyk
Active Contributor
‎07-14-2005 4:35 AM
0 Kudos

glad I could help a little:)

Regards,

michal

Answers (0)

Ask a Question