on 08-20-2010 10:41 AM
Hi
I have a java proxy setup going but i keep getting the following error when trying to send messages through the interface (either via ABAP proxy or from the test message tool in RWB) -
<?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">UNAUTHORIZED</SAP:Code>
<SAP:P1>401 </SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:Stack>
</SAP:Stack><SAP:Retry>M</SAP:Retry></SAP:Error>
The proxy has worked on our other environments and i have checked that the user account used in the channel has the correct permissions. Is there anything else that i could be missing? Please help!
Thanks
check the users;
1. roles assigned
2. profiles assigned.
this is definitely something to do with the authorizations
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Riaz,
Check the below links for solutions
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
Regards
Ramesh
Hello,
Apply on of notes below according to your system version:
PI 7.1:
#999962 - PI 7.10: Change passwords of PI service users
XI 7.0
#936093 - XI 7.0: Changing the passwords of XI service users
XI 3.0
#721548 - XI 3.0: Changing the passwords of the XI service users
Ensure you maintain the properly passwords, which must be the same
for all the service users.
For more reference in regard of 403 error, check this blog:
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Regards,
Caio Cagnani
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Riaz,
The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.