on 11-24-2015 5:08 PM
Hi Experts,
We are testing file to proxy scenario in development system and its working fine earlier. But now we are faced HTTP 200 error as a shown below..I have searched blogs in SDN but did not get the resolution steps in my scenario.
<?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="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">OK_BUT_NO_XI_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Previous resolution steps in SDN for same error.
1.File size----need to increase ffile size setting---But in my case we are using 20 kb file.
2.Path prefix---need to maintain path prefix in RFC destination---I have already did this one.
3.XI adapter---need to select xi 2.0 in message protocol in case of SAP ECC version below 6.0-- i have already did this one.
can you please provide other solution except above one.Thank you.
Regards,
Azeem
Hi,
Check password for HTTP Destination in SM59 which is connecting to PI.
Password must be about to expire , that's why it is asking for setting up new password and that is the response you are getting while connecting to PI system, which is not in XI format.
Reset this password of HTTP destination in SM59 and try to resend messages. Hope this will work.
Regards,
Aniket
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Azeem,
By Proxy do you mean ABAP or Java proxy? If ABAP, what does the response payload look like when viewed in SXMB_MONI? Sometimes the server will throw a HTML error page for auth errors which results in an error like this one.
Regards,
Nick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nick,
Yes...its a visible in MONI.
Response payload :
<?xml version="1.0" encoding="UTF-8" ?>
</MessageHeader>
</CollectivePaymentOrderNotification>
</ns1:CollectivePaymentOrderNotification_async>
Regards,
Azeem
Hi Azeem,
Your screenshot shows the HTMLError also in the response under the MainDocument. If you open that error document you should see a HTML page. Save that somewhere on your PC and open it in IE and you should now see the error. If you paste it up here we can assist with the error message.
Regards,
Nick
Azeem,
Try changing the protocol once to XI 3.0 and check.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.