Http server code 401 reason Unauthorized explanation Unauthorized

Hello to you all,
I have a SRM-XI-SUS scenario and I try to connect to SUS with XI but I am facing the follwoing issue:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="<b>PLAINHTTP_ADAPTER</b>"><b>ATTRIBUTE_SERVER</b></SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3>Unauthorized</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack><b>Http server code 401 reason Unauthorized explanation Unauthorized</b></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can someone guide me towards a solution?
Kind regards,
Kamran

I am not intimate with the SRM-SUS integration via XI, but based on the business scenario configuration guide (https://service.sap.com/~sapidb/011000358700002897402004E/ServiceProcurementNEW.pdf) it seems that communication between SRM and SUS via XI takes place via proxies. Assuming that's what you're trying to do, to communicate to SUS via proxies, you would need to use the adapter type (XI). The communication is still technically over HTTP, but using the XI messaging protocol.
The use of an sm59 destination is optional. The XI type communication channel allows addressing types of "URL Addressing" or "HTTP Destination". If you choose the latter, you would need a sm59 destination of type H and then refer to it from the channel.
Try using a XI type receiver channel instead. If you run into additional problems, check the "XI Settings" section of the guide above.
Regards,
Jin

Similar Messages

Http server code 401 reason Unauthorized

Hi,
I am trying to setup a scenario of sending an IDOC from R/3 to XI and then sending it further to a 3rd party program using the HTTP Channel.
If I go to transaction IDX5 in XI, I can see my IDOC sitting there as Inbound. When I check the error message on it, I get the message "Http server code 401 reason Unauthorized explanation Unauthorized" Also further along on the screen it says that the error category is "PLAINHTTP_ADAPTER" and Error ID is "ATTRIBUTE_SERVER".
Can someone guide me towards a solution?
Thanks in Advance!
Miguel

Hi Rekha,
I have checked the settings and they appear to be correct.
Here is a piece of the trace of the monitor where the error occurs:-
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">---- Plain HTTP Adapter Outbound----</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_HTTP_PLAIN_OUTBOUND-ENTER_PLSRV">
<Trace level="3" type="T">Quality of Service EO</Trace>
<Trace level="1" type="T">Get XML-Dokument from the Message-Objekt</Trace>
<Trace level="2" type="T">HTTP-Destination : SBO_ITK</Trace>
<Trace level="3" type="T">Server pgsap09.sap.pg.co.za</Trace>
<Trace level="3" type="T">Service-Nr. 80</Trace>
<Trace level="3" type="T">URL /SBOWebService/xi</Trace>
<Trace level="3" type="T">~request_method POST</Trace>
<Trace level="3" type="T">~server_protocol HTTP/1.0</Trace>
<Trace level="3" type="T">accept: /</Trace>
<Trace level="3" type="T">content-type: text/xml</Trace>
<Trace level="3" type="T">msgguid: 2F7389425DBE1711E100000082010B5A</Trace>
<Trace level="3" type="T">service: DR0</Trace>
<Trace level="3" type="T">interface namespace: http://sap.com/xi/SBO</Trace>
<Trace level="3" type="T">interface name: MasterDataFunctionModule__vendorMasterUpdate</Trace>
<Trace level="3" type="T">quality of service: EO</Trace>
<Trace level="3" type="T">Header-Fields</Trace>
<Trace level="3" type="T">Prolog conversion Codepage: UTF-8</Trace>
<Trace level="3" type="T">Epilog conversion Codepage: UTF-8</Trace>
<Trace level="3" type="T">content-length 3273</Trace>
<Trace level="2" type="T">HTTP-Response :</Trace>
<Trace level="2" type="T">Code : 401</Trace>
<Trace level="2" type="T">Reason: Unauthorized</Trace>
<Trace level="2" type="T">Code : 401</Trace>
<Trace level="2" type="T">Reason: Unauthorized</Trace>
</Trace>
From this it appears that it is complaining about the user name into the external program, although when I do a test connection in SM59, I get a positive response?
Thanks,
Miguel

HTTP server code 500 reason Internal Server Error explanation Error during

Hi,
I am trying to connect to SAP TM (Tranportation Management) System using HTTP adapter using PI 7.0.The scenario is
ECC ->PI->SAP TM. I have configured HTTP adapter as the receiver with addressing type as HTTP Destination. I have created a RFC destination of type H pointing to SAP TM on PI. I have encountered the following error after executing the scenario.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Error during parsing of SOAP header</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Error during parsing of SOAP header</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
Kiran

Error during parsing of SOAP header
Can you mention what are the settings done in Receiver HTTP channel.....the request that you send to target is not in proper format.
One reason could be incorrect Content Type.....is it text/XML ?
Regards,
Abhishek.

Simple HTTP Receiver - HTTP server code 405 reason Not Allowed explanation

Hi, I am using simple HTTP Receiver to receive the XML file from the below url http://www.bank-ua.com/export/currrate.xml
But receiving the below error in SXMB_MONI
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>405</SAP:P1>
<SAP:P2>Not Allowed</SAP:P2>
<SAP:P3><html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx/1.4.1</center> </body> </html></SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP server code 405 reason Not Allowed explanation <html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx/1.4.1</center> </body> </html></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Initially the same URL was working could you advice what to change to make this working?
Thanks,
Dhill

Hi Senthil,
There is a way, you can expose the function module HTTP_GET as an rfc-enabled FM and use it to call the webservice. Here is a POC I made before:
Proof of Concept: An Alternative HTTP GET using a Remote-Enabled Version of the Function Module HTTP_GET
Another is to create a UDF that uses an HTTP Client class to call the webservice.
Regards,
Mark

Http server code 503 reason Service Unavailable explanation Service Unavail

Hi all
I am trying to send data to a HTTP SITE.
I am getting the following error.
Could somebody guide me how to solve this.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Oxalate</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>503</SAP:P1>
<SAP:P2>Service Unavailable</SAP:P2>
<SAP:P3>Service Unavailable</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Http server code 503 reason Service Unavailable explanation Service Unavailable</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thankyou

Same errors are comming up.
Could not do a RFC connection to website.

HTTP server code 400 reason Bad Request explanation Bad Request

hello everybody,
i'm working with SAP PI 7.1
I designed my interface IDOC-PI-HTTP.
when i send idoc from R3 i see this message in PI monitor:
HTTP server code 400 reason Bad Request explanation Bad Request
i tried to configure a HTTP port in SM59 and use it in my Communication Channell, but when i test connection i have same error.
I'm using a https address.
have you any suggestion?
thanks
Alex

Hello,
I already verify with 3 party developer. He confirmed me he is expecting i send data by POST.
Yes, but how does the HTTP Body looks like?See sample webservice below:
http://ws.cdyne.com/delayedstockquote/delayedstockquote.asmx?op=GetQuickQuote and scroll down to see how an HTTP POST looks like
Content type is a String
Normally, the content-type for an http post is application/x-www-form-urlencoded. But then, you need to know the prolog and epilog in the http body.
he gave me a url address https://.......
where i need set the parameter HTTPS??
https (http with ssl) is configured in mm59 type G (external server). To enable https, you need to select the SSL folder in which you have installed the CA (certificate authority) certs. Make sure that once you have installed the CA certs, you have performend an ICM Restart.
Hope this helps,
Mark
Edited by: Mark Dihiansan on Jul 25, 2011 11:21 AM

HTTP server code 404 reason Not Found explanation Not Found

Hi all
I am facing this error "HTTP server code 404 reason Not Found explanation Not Found" during a asynchronous xml message sent to a buisiness service
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>404</SAP:P1>
<SAP:P2>Not Found</SAP:P2>
<SAP:P3>Not Found</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP server code 404 reason Not Found explanation Not Found</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
could you provide an explanation on this error.

Hi
Go through this
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
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)
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
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
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.
**********Reward points if usefulll.**********

HTTP server code 500 reason Internal Server Error

HI,
I am getting following error in Call Adapter
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Internal Server Error</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Internal Server Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have a Business system that is sending the material master data to a different Business System via XI. The message is received by XI correctly. XI correctly performs the transformation and identifies the message interface and selects correct receiver for the message. XI communicates with the receiving business system via the appropriate communication channel.
The message "fails" in the receiving system with the following error:
HTTP server code 500 reason Internal Server Exception explanation Error parsing of SOAP header.
The channel is using HTTP Adapter type, and i cross checked the communication channel details like Addressing type, target host, service number, path, user name, user password.......each and every detail is correct.
Please help me out to find the solution to the problem.
Points will be gladly awarded.
Edited by: Ashish Soni on Sep 24, 2008 9:02 PM

try sending the same XML message picking from moni and check whether you are getting same error or not?
if you get same error then check at web server for logs there you can find exact error.

HTTP server code 405 reason Method Not Allowed exception

I get a 405 method not allowed exception in synchronous http receiver. However I have verified that a http post is expected by the receiver system.
Is there anythin else I could check or what could cause the error?

Hi,
what is the receiving system? Usually, you get this error when you try to do POST on static page. In the HTTP header of response you should get the list of allowed methods. You can try to check this list. I would contact an administrator of that system if he can check logs for errors.
Cheers

Http server code 403 in SXMB_MONI

*Hello All,*
*When I am posting an IDoc from R/3 to XI I get the following in SXMB_MONI in the Call Adapter.*
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>403</SAP:P1>
<SAP:P2>Forbidden</SAP:P2>
<SAP:P3>Forbidden</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Http server code 403 reason Forbidden explanation Forbidden</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Could anyone please comment on what could be the possible reason and how can we handle this.
Thanks in Advance..!!
Regards,
Smita

Hi,
Check this
Error: HTTP 403 Forbidden
Description: The server understood the request, but is refusing to fulfill it
Possible Tips:
Path sap/xi/engine not active
HTTP 403 during cache refresh of the adapter framework - Refer SAP Note -751856
Because of Inactive Services in ICF Go to SICF transaction and activate the services. Refer SAP Note -517484
Error in RWB/Message Monitoring- because of J2EE roles Refer SAP Note -796726
Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. Because of the URL is incorrect or the adapter is not correctly deployed.
Regards
Seshagiri

Trex Indexing giving HTTP Status Code 401:Unauthorized error

Dear All,
We have configured TREX search on KM repository of our EP
production server and trying to search using the same our KM repository.
The TREX is installed on the a separate server.
When we try to Index production repository the documents are failing in
the Preparation failed status with return code 6401 and error message
HTTP Status Code 401: Unauthorized.
I also applied SAP-Note 650521 and checked id index_service user and
found that its active and not locked but still issue didnu2019t get
resolved. Moreover i have gone thru most of the previous post regarding this topic but didt help.
I even checked the URL Generator service too which is fine.
On one test system also where SPNego is configured we are getting same
401 error. On this system we disabled SPnego and Indexing started working
fine. When we reverted back the SPNego configuration for confirmation of
our observation we found that it again started to give 401 error.
Any help in this regard will be appreciated.
Regards,
Srinath Pillai
Edited by: Srinath Pillai on Sep 3, 2009 8:59 AM

Dear
Open System Administration--> System Configuration> Knowledge Management--> Content Management> Global Services (Mode : Advanced)> Index Management Service--> Check for Crawling Service User it has to be index_service
If still you have problem than do let me know where is your Repository located are the documents are stored on Portal Server itself or it is stored on some external server...
What kind of repository you use CM Repository(Mode:DB,DBFS,FSDB) , File System Repository....e.t.c....
Regards
Akshit

HTTP response contains status code 401 with the description Unauthorized

Hi,
I have an IDOC-XML mapping,when the IDOC is sucessfully passed on to the XI but in XI I encounter an errror
"HTTP response contains status code 401 with the description Unauthorized".Could somebody let me know what
could be the reson for this error.
Regards,
Arun

Dear Arun,
1) This might cause due to wrong permissions.
2)Try with this Login XIISUSER
3)Tcode SICF -> Default_host -> sap -> xi
( Check right password for the user id )
Regards
Agasthuri Doss

HTTP response contains status code 401 with the description Unauthorized Er

Hi All,
I am getting the below error, i have reset the password and username also but i am not getting where exactly it is failing out.
<b>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>Enter User Name and Password</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 401 with the description Unauthorized Error when sending by HTTP (error code: 401, error text: Unauthorized)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
</b>
Can anyone have the idea how can i check it out...??
Thanks in advance.

<b>I have changed every password and username from XIAPPLUSER to XIAPPLTEST, but still in MONI--->oubound binding ..,, i am getting the logon user as the XIAPPLUSER... I check the perticular communication channel it is maintained XIAPPLTEST but still i am getting XIAPPLUSER.....
Do i have to refresh somewhere.
Can anyone have the idea is there anywhere else it is maintained..</b>
================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SAP:OutboundBindingEntry version="30">
<SAP:OutboundBindingObjectId>041B892AC87B38A4AE46D4E443C88E55</SAP:OutboundBindingObjectId>
<SAP:FromPartyName />
<SAP:FromServiceName>BS_PSEWC</SAP:FromServiceName>
<SAP:ToPartyName />
<SAP:ToServiceName>BS_SAPRP1</SAP:ToServiceName>
<SAP:ToInterfaceName>sub_MeterReading</SAP:ToInterfaceName>
<SAP:ToInterfaceNamespace>urn://WCM_SR3_02/SAP/Meterreading</SAP:ToInterfaceNamespace>
- <SAP:OutboundBindingAttributes>
<SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:OutboundBindingAttributes>
- <SAP:HeaderMapping>
<SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:HeaderMapping>
- <SAP:ChannelEntry version="30">
<SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">BS_SAPRP1</SAP:ServiceName>
<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">CCO_Proxy_WCM_MeterReading</SAP:ChannelName>
<SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">XI</SAP:AdapterName>
<SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
<SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">3B787A8035C111D6BBE0EFE50A1145A5</SAP:AdapterSWCV>
<SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">IS</SAP:AdapterEngineType>
<SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">XI</SAP:MessageProtocol>
<SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">2.0</SAP:MessageProtocolVersion>
<SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">HTTP</SAP:TransportProtocol>
<SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">1.0</SAP:TransportProtocolVersion>
<SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
<SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
- <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:Attribute>
<SAP:Name>addressingMode</SAP:Name>
<SAP:Value>url</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>authenticationModeBasicAnon</SAP:Name>
<SAP:Value>basicSAP</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>host</SAP:Name>
<SAP:Value>drprd-db1</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>httpDestination</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonClient</SAP:Name>
<SAP:Value>300</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonLanguage</SAP:Name>
<SAP:Value>E</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonPassword</SAP:Name>
<SAP:Value isPassword="true" />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonUser</SAP:Name>
<b><SAP:Value>XIAPPLUSER</SAP:Value></b> </SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>path</SAP:Name>
<SAP:Value>/sap/xi/engine?type=receiver</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>port</SAP:Name>
<SAP:Value>8001</SAP:Value>
</SAP:Attribute>
</SAP:AdapterTypeData>
</SAP:ChannelAttributes>
</SAP:ChannelEntry>
</SAP:OutboundBindingEntry>
</SAP:OutboundBinding>

Help needed to resolve Received HTTP response code 401 : Unauthorized

2011-04-08 11:37:48 Error Transmitting the message to endpoint http:---/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 401 : Unauthorized
while i was executing file to file scenario. the error occoured.
Edited by: subbuk76 on Apr 8, 2011 8:12 AM

As the error indicates, the username/PWD you are using in file adapter to write the file (FTP) at target location is incorrect and hence the error. Please check and let us know.
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 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
Also, for HTTP errors in future do refer this blog:
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
It will help you

Received HTTP response code 401 : Unauthorized

Hi Experts!
I know there are lots of posts regarding Received HTTP response code 401 : Unauthorized, and I read a lot of them.
Unfortunately I got not the solution to my problem.
I have following scenario: async; oneway; xml via DataPower (SOAP) to SAP PI to Service Consumer
When sending a message it is led over the DataPower to the PI, but it is not processed through.
It enters the MP and it is successfully put into the queue. You can see the details below.
15.02.2012 15:12:34.611     Information     MP: entering1
15.02.2012 15:12:34.614     Information     MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
15.02.2012 15:12:34.616     Information     SOAP: request message entering the adapter with user PI**
15.02.2012 15:12:34.620     Information     SOAP: request message leaving the adapter (send)
15.02.2012 15:12:34.620     Information     The application tries to send an XI message asynchronously using connection SOAP_http://sap.com/xi/XI/System.
15.02.2012 15:12:34.624     Information     Trying to put the message into the send queue.
15.02.2012 15:12:34.676     Information     SOAP: call completed
15.02.2012 15:12:34.676     Information     SOAP: completed the processing
15.02.2012 15:12:34.676     Information     Message successfully put into the queue.
15.02.2012 15:12:34.676     Information     The application sent the message asynchronously using connection SOAP_http://sap.com/xi/XI/System. Returning to application.
15.02.2012 15:12:34.678     Information     MP: leaving
15.02.2012 15:12:34.682     Information     The message was successfully retrieved from the send queue.
15.02.2012 15:12:34.700     Information     The message status was set to DLNG.
15.02.2012 15:12:34.922     Error     Transmitting the message to endpoint https://<sid>.XXX:port/sap/xi/engine?type=entry using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 401 : Unauthorized.
15.02.2012 15:12:34.940     Information     The message status was set to WAIT.
15.02.2012 15:12:34.941     Information     The asynchronous message was successfully scheduled to be delivered at Wed Feb 15 15:17:34 CET 2012.
I can't say, why I get the 401-response.
From PI Message Monitoring: Monitor Messages I get following informations:
Message-ID     MSG-ID
Richtung     OUTBOUND
Message-Headers     content-length=14391
http=POST
content-type=multipart/related; boundary=SAP_MSG-ID_END; type="text/xml"; start="<soap-MSG-ID[at]sap.com>"
Message-Typ     Send
Verbindungsname     SOAP_http://sap.com/xi/XI/System
Credential     SAPPasswordCredential(PIAFUSER):password=********:sapclient=009:saplang=en:sapsysid=<SID>
Fehlerkategorie     XI_J2EE_ADAPTER_XI_HANDLER
Fehlercode     SEND_CONSUMER_ERROR
Statusdetails     Messaging: allgemeiner Fehler
Quality-of-Service     EO
Empfängerkomponente
Referenz-ID
Senderkomponente     SENDER_COMP
Sequenz-ID
Serialisierungskontext
Status     systemError
Einplanungszeit     2012-02-15 13:49:38.579
Start Time     Wed Feb 15 13:34:37 CET 2012
Transport     HTTPS
Gültig bis
Protokoll     XI
Persistenz bis     2012-02-16 13:34:37.373
Endzeitpunkt     Wed Feb 15 13:49:39 CET 2012
Anwendungskomponente
Softwarekomponente
Service-Definition
Wurde bearbeitet     false
Any clues?
Many thanks in advance
Holger

Hi Ravi,
it's the Java stack's port.
Hi Venkata,
1. Check whether service user maintained in the SM59 destination is with Roles of std. user PIAPPLUSER, PIISUSER
         The Problem is, that the message is not processed in the PI. I don't see them at SXMB_MONI.
         Today I see them on the RWB at the message-monitoring, but only because they are set after the 3rd try to send them to NDLV.
         I can see the messages, after they are triggered, in the comm-channel-monitoring by selecting the appropriate channel.
2. Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
         Checked the PIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
3.May be wrong password for user PIISUSER.
         There was a pwd-change in january, but the passwords are all correctly replaced.
Thank you for your help!
Holger

Http server code 401 reason Unauthorized explanation Unauthorized

Similar Messages

Maybe you are looking for