HTTP_RESP_STATUS_CODE_NOT_OK (401)

Hi, I am implementing XI scenario using HTML plain sender adapter and RFC receiver adapter ... I am calling R/3 function from third-party system. XI receives the message but always ends with error HTTP_RESP_STATUS_CODE_NOT_OK (401 - Unauthorized). I went through similar threads but did not found any sensible solution, how resolve this problem. Here is the log trace (maybe could be useful) ... Thanks for replies ...
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <Trace level="1" type="B" name="CL_HTTP_PLAIN_INBOUND">
<Trace level="1" type="T">server-protocol HTTP/1.1</Trace>
<Trace level="1" type="T">user-agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.04506; .NET CLR 1.1.4322)</Trace>
<Trace level="1" type="T">host sapdev:8080</Trace>
<Trace level="1" type="T">content-length 2636</Trace>
<Trace level="1" type="T">remote-addr 192.168.106.16</Trace>
</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = A80</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RMOJZIS</Trace>
<Trace level="1" type="Timestamp">2008-07-28T10:08:21Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = C69C8D480E87740CE1000000C0A8C88C</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0008</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0008</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface ice2sap_out</Trace>
<Trace level="1" type="T">select interface namespace http://ave</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = A80</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RMOJZIS</Trace>
<Trace level="1" type="Timestamp">2008-07-28T10:08:21Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTO0___0000</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface ice2sap_out</Trace>
<Trace level="1" type="T">select interface namespace http://ave</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface ice2sap_in</Trace>
<Trace level="1" type="T">select interface namespace http://indra</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = A80</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RMOJZIS</Trace>
<Trace level="1" type="Timestamp">2008-07-28T10:08:21Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="1" type="T">Interface Mapping http://ave ice2sap_map</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="1" type="T">HTTP Multipart document length: 5704</Trace>
<Trace level="1" type="System_Error">HTTP-client: error response= <!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"> 401 &nbsp Unauthorized</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">SAP J2EE Engine/7.00 </td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"> Authentication did not succeed.</td> </tr> <tr bgcolor="#FFFFFF"> <td align="left" valign="top" height="48"> Details:</td> <td align="left" valign="top" height="48"><pre> No details available</pre></td> </tr> </body> </html></Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>

OK, let me summarize what I already know about requirements to connect SAP XI -> SAP R/3 via receiver RFC adapter
a) integration server user must have SAP_XI_APPL_SERV_USER role
b) user specified on receiver communication channel must have on destination system S_RFC authorization object ...
are there any other requirements / conditions required to be met to be able transport request from SAP XI to SAP R/3 ??? for example, is it necessary to define some RFC destinations on R/3 system? ...
Thank you.

Similar Messages

HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized when sending EDI from ICH

Hi
When I try to send an EDI from our ICH-server (SCM) to a R/3-target system via PI-server (v7.0) , I get :
u201Du2026
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
u201C
This error is fetched in the ICH-servers sxmb_moni
I have found several tips and tricks for this situation on SDN.
But, my main-question is:
Which user is not allowed to login?
Is it XIAPPLUSER? I can't find the user in the tracelog for the message. Only the original person who created the EDI. (I'm quite sure that user is not the one the system is complaining about).
Does anybody knows how to analyse this?:
Where can I get clear info on which user that can't login to PI?
Where do I check the password?
Note, the other way around works fine. I.e sending messages from R/3 to ICH via PI.
So, I guess that this has to do be something with the ICH:s configuration.
Appreciated
/Joakim

1) Where can I get clear info on which user that can't login to PI?
Error: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
Description: The request requires user authentication
Possible Tips:
Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
If the error is in Adapter Engine
then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
May be wrong password for user XIISUSER
May be wrong password for user XIAFUSER
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
Http* Errors in XI
2) Where do I check the password?
Check in SU01 if the user is not locked or pwd is OK. Password will be known to basis team. Cross verify with team.
Further,clear adapter engine cache (sxi_cache -> Goto -> Adapter Engine Cache -> Delete cache contents)

HTTP_RESP_STATUS_CODE_NOT_OK 401 error

Hi,
I am doing sender ABAp proxy and receiver Webservice , Proxy is running sucessfully till yesterday but while executing the ABAp proxy 2day i am getting following error
HTTP_RESP_STATUS_CODE_NOT_OK 401 error
HTTP response contains status code 401 with the description Unauthorized Authorization error while sending by HTTP (error code: 401, error text: Unauthorized

Check the RFC Dest of type H in ECC which is connect to XI system is working or not if it not working check the credentials
Below are some tgreads which may help u to solve u r problem
How do you activate ABAP Proxies?
Re: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
Re: Regarding HTTP_RESP_STATUS_CODE_NOT_OK error.

Error: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized

Hi all,
I am having one issue i.e Error: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
I am doing HTTP to RFC..
Plz anyone can help me on this

Hi,
Check SND search help for more info, mean time you can have a look at these steps..
u2022 Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
u2022 If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
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
Regards,
Sarvesh

HTTP_RESP_STATUS_CODE_NOT_OK 401 unauthorized

Hi All
my interface is File to proxy,
i am getting this error ,HTTP_RESP_STATUS_CODE_NOT_OK
when i checked the trace it is saying
HTTP response contains status code 401 with the description Unauthorized Authorization error while sending by HTTP (error code: 401, error text: Unauthorized
i needed to know what all the roles i need to have to have over come problem
i hope this is only cause of roles problem has i dont have authorisation for all tracsation
i should add in R/3 ECC 6.00 for my roles
thankingyou
Sridhar

Hi
use similar thread
In SXMB_MONI i am gettin error status 500
Received HTTP response code 500..
HTTP_RESP_STATUS_CODE_NOT_OK 500 error
Re: Proxy error - HTTP status code 500

IDOC to XI : HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized

Hi Guys,
I meet a problem while send idoc from ECC to XI in testing enviroment. I check the messege ID, find red flag with error message
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
I guess something wrong with configuration. Because can not see the port number here. Any one can tell me how to solve this problem? Thanks !!!
 <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Attribute>
<SAP:Name>SecurityProfile</SAP:Name>
<SAP:Value>securityProfileWSSE</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>addressingMode</SAP:Name>
<SAP:Value>destination</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 />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>httpDestination</SAP:Name>
<SAP:Value>XI_SUS_RGQCLNT301</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>isMessageSecurity</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonClient</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonLanguage</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonPassword</SAP:Name>
<SAP:Value isPassword="true" />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonUser</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>passHopList</SAP:Name>
<SAP:Value>1</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>path</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>port</SAP:Name>
<SAP:Value />
</SAP:Attribute>

Hi,
This Error - HTTP_RESP_STATUS_CODE_NOT_OK Might also occur because of authorization Check sm59 HTTP destination on R3 that points to the XI integration engine.
Check this
HTTP_RESP_STATUS_CODE_NOT_OK
Regards
Seshagiri

ERR: HTTP_RESP_STATUS_CODE_NOT_OK - 401 Unauthorized

Hi All,
 I have a scenario which transfers data from ABAP Proxy(client 200 of XI) to XI(client 100 of XI) IS using the interface "ValueMappingReplicationOut" and the receiver adapter is XI. While executing an ABAP program from client 200 (to trigger the proxy), I'm getting the following error in the receiver side (SXMB_MONI client 100).
"HTTP response contains status code 401 with the description Unauthorized Error when sending by HTTP (error code: 401, error text: Unauthorized)"
XI adapter Settings:
Target :Host XI server IP address
Service :Port Number (8010)
path : /MessagingSystem/receive/JPR/XI
User :XIAPPLUSER
I have gone thru most of the related forum/blogs available. Couldn't figure out the problem.
Looking forward for some help.
Thanks in Advance.
Ajay.

Hi Sudharshan and Udo,
 Thanks for your prompt reply. It was the problem with the Authentication Type. Now it is not showing any error.
 The scenario is to update the data in the run time cache of the IS. But it is not happening.
REPORT ZVALUEMAPPING.
data: lcl_value_mapping type ref to co_svmr_value_mapping_rep,
ls_value_mappings type svmr_value_mapping_replication,
ls_item type svmr_value_mapping_rep_item,
lcl_system_fault type ref to cx_ai_system_fault.
ls_item-operation = 'Insert'.
ls_item-group_id = '315286378563858425463215845123345'.
ls_item-context = 'http://test'.
ls_item-identifier-scheme = 'FormOfAddress'.
ls_item-identifier-agency = 'CRM'.
ls_item-identifier-value = '2'.
append ls_item to ls_value_mappings-value_mapping_replication-item.
ls_item-operation = 'Insert'.
Use the same guid for another value of the same group
ls_item-group_id = '315286378563858425463215845123345'.
ls_item-context = 'http://test'.
ls_item-identifier-scheme = 'FormOfAddress'.
ls_item-identifier-agency = 'R3'.
ls_item-identifier-value = '1'.
append ls_item to ls_value_mappings-value_mapping_replication-item.
create object lcl_value_mapping.
try.
call method lcl_value_mapping->execute_asynchronous
exporting
output = ls_value_mappings.
commit work.
catch cx_ai_system_fault into lcl_system_fault.
write: 'Error: ', lcl_system_fault->errortext.
The above mentioned is the program we used.
And when I check for the scheme 'FormOfAddress' and agency 'CRM' in the ID -> Tools -> Value Mapping, there is no value as such. Kindly calrify.
Thanks,
Jothivel.
Message was edited by: Jothivel Sundaram

HTTP_RESP_STATUS_CODE_NOT_OK status 401

Hello,
We have PI 7.0 SP 12.
The server has a strange behavior. It is only happening on the production environment, which is very stressed.
Everything is working fine, but after 2 or 3 days, all messages are in error in sxmb_moni :
Category : XIServer
Code area = INTERNAL : HTTP_RESP_STATUS_CODE_NOT_OK
Stack : HTTP response contains status code 401 with the description Unauthorized Authorization error while sending by HTTP
I have already been through all other forum posts, but they are related to a specific scenario. In my case, ALL the messages have this status, but when I restart the server, everything is fine again, until the next 2-3 days when it "crashes" again. We can not connect to the Repository, Directory or RWB anymore neither, as if the authentication process in PI java part was gone (we can still connect on the ABAP part).
Has anyone been through that error or have any suggestion ?
Many thanks,
Best regards,
GL

hi,
i never have this kind of error.
lokking in some blogs and threads i got it:
Blog: /people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Error: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
Description: The request requires user authentication
Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
If the error is in Adapter Engine
then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
May be wrong password for user XIISUSER
May be wrong password for user XIAFUSER
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
it is not only the following users that are impacted
this are communication users of pi. i adviced you to check when before restart the server if any of this users are lock.
Thanks
Rodrigo
Edited by: Rodrigo Pertierra on Apr 29, 2008 11:20 AM

Problem with error code 401

Hi I had a problem yesterday with my receiver determination... I had an XICACHE update error along with
SAP:AdditionalText>Error when reading HTTP destination: INTEGRATION_DIRECTORY_HMI.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while refreshing the XI runtime cache</SAP:Stack>
I have since seemed to of solved this problem while using SXI_CACHE and refresh...
Now we are getting the following...

- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for adapter engine: RFC</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">no values in cache (no lock found) - start reading from SLD</Trace>
<Trace level="1" type="T">error reading SAP_XIAdapterFramework from SLD</Trace>
<Trace level="2" type="T">Adapter Framework(s) found</Trace>
<Trace level="2" type="T">Service Port(s) found - take first one</Trace>
<Trace level="2" type="T">URL found</Trace>
<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
<Trace level="3" type="T">URL = http://mxavie0:56800/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="3" type="T">User = XIISUSER</Trace>
<Trace level="3" type="T">Cached =</Trace>
<Trace level="3" type="T">Creating HTTP-client</Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Security: Basic authentication</Trace>
<Trace level="3" type="T">Serializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="3" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="3" type="T">HTTP-client: status code = 401</Trace>
<Trace level="3" type="System_Error">HTTP-client: error response= <!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"> 401 &nbsp Unauthorized</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">SAP J2EE Engine/7.00 </td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"> Authentication did not succeed.</td> </tr> <tr bgcolor="#FFFFFF"> <td align="left" valign="top" height="48"> Details:</td> <td align="left" valign="top" height="48"><pre> No details available</pre></td> </tr> </body> </html></Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 023</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:[email protected]">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description />
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope>
Anyone have ideas as to why this is coming?

HI,
Error: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
If the error is in Adapter Engine
then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
May be wrong password for user XIISUSER
May be wrong password for user XIAFUSER
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
Regards
Chilla..
Points rewarded if it is helpful..

HTTP_RESP_STATUS_CODE_NOT_OK - Error in ABAP proxy

Dear all,
I work in a scenario in which we send data from the R/3 to XI using the ABAP proxies.
But the messages are not received in XI.
The messages are in error in SXMB_MONI of the R/3 system.
The error message we get in SXMB_MONI of the R/3 system is "HTTP_RESP_STATUS_CODE_NOT_OK"
<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 />
Could anyone kindly suggest a solution to rectify this error?
Thanks.
Best Regards,
Thangesh

Hi,
>>401
1) Might cause due to insufficient right of the User ID
2)Try with this Login XIISUSER
3)Tcode SICF -> Default_host -> sap -> xi
( Check right password for the user id )
4) Check the RFC connection User Id..and it's settings.
This Might Help you
HTTP_RESP_STATUS_CODE_NOT_OK - 401 Unauthorized
HTTP_RESP_STATUS_CODE_NOT_OK 404 Error
HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
Regards
Agasthuri Doss

401 - Unauthorized error in Value Mapping Replication scenario

Hi,
I'm trying to push some Value Mapping replication data from one of the clients (which is a non-Integration Server) of XI system to IS. When I execute the program which calls the outbound proxy, the XI message fails with the error HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorised.
As given in SAP help, I registered the inbound java proxies and generated the outbound proxies. I confiured the receiver channel with path /MessagingSystem/receive/JPR/XI. In authentication data, I tried several users such as XISUPER, XIAPPLUSER, XIISUSER..Still I get the same error.
What is missing/wrong?
Thanks in advance
Praveen Sirupa

Hi Praveen,
Could you pls do the following...just for verification....
enter the url http://<was_server>:5<sysnr>00/MessagingSystem/receive/JPR/XI
and when it asks for authentication give the XIAPPLUSER and password...you should get an xml that looks like this...
<?xml version="1.0" encoding="UTF-8" ?>
- <scenario>
<scenname>MSG_SCEN</scenname>
<scentype>SERV</scentype>
<sceninst>MSG_001</sceninst>
<scenversion>001</scenversion>
- <component>
<compname>SERVLET</compname>
<compdesc>Messaging System</compdesc>
<comphost>localhost</comphost>
<compinst>MSG_001</compinst>
- <message>
<messalert>OKAY</messalert>
<messseverity>100</messseverity>
<messarea>QR</messarea>
<messnumber>801</messnumber>
<messparameter>na</messparameter>
<messtext>MessagingServlet is active.</messtext>
</message>
</component>
</scenario>
Thanks,
Renjith

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

How Resolve Sip 401 response code ?

hi all m trying to register with sip server but getting 401 unauthorised as response code..
how to solve this issue so that 200 OK should be received ..please help
how to send Digest Authentication ??
how to fix error: unable to retrieve credentials from RMS!
mail id [email protected]
Edited by: rahulsapra on Aug 17, 2010 9:33 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

Error while posting data from SCM to XI

Dear Expertise,
I got a requirement where I need to post data from SCM to XI server. From SCM
side it is an ABAP proxy. When I tested the scenario and checked in the MONI of
SCM I got an error. But SCM is correctly configured pointing to XI under Tcode
SM59 (SM59 --> Connection Type H (HTTP Connection to ABAP System) -->with
correct user credentials and PIPE line URL of XI server).
Please let me know is this the correct settings for ABAP proxy for connecting
from SCM system to XI system.
Error Dump in SXMB_MONI:
<?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><!DOCTYPE html PUBLIC"-//W3C//DTD HTML 4.01Transitional//EN">
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 401 with the description Unauthorized Authorization error while sending by HTTP (error code: 401, error text: Unauthorized)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks in Advance,
Gujjeti

HI
Check these
For Error: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
Description: The request requires user authentication
Possible Tips:
Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
If the error is in Adapter Engine
then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
May be wrong password for user XIISUSER
May be wrong password for user XIAFUSER
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

"Message Rejection Handler" for the file/ftp adapter using fault policy

Hi guys,
We are trying to implement "Message Rejection Handler" for the file/ftp adapter using following fault policy configuration.
Fault Policy:
`````````````
<?xml version='1.0' encoding='UTF-8'?>
<faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy">
<faultPolicy version="2.0.1" id="ProcessNameGenericPolicy"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Conditions>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
name="bpelx:remoteFault">
<condition>
<action ref="ora-retry"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
name="bpelx:bindingFault">
<condition>
<action ref="ora-rethrow-fault"/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id="ora-retry">
<retry>
<retryCount>3</retryCount>
<retryInterval>1</retryInterval>
<retryFailureAction ref="ora-rethrow-fault"/>
</retry>
</Action>
<Action id="ora-rethrow-fault">
<rethrowFault/>
</Action>
<Action id="ora-human-intervention">
<humanIntervention/>
</Action>
<Action id="ora-terminate">
<abort/>
</Action>
</Actions>
</faultPolicy>
<faultPolicy version="2.0.1" id="ProcessNameHumanInterventionPolicy"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Conditions>
<faultName xmlns:medns="http://schemas.oracle.com/mediator/faults"
name="medns:mediatorFault">
<condition>
<test>contains($fault.mediatorErrorCode, "TYPE_TRANSIENT")</test>
<action ref="ora-retry-with-intervention"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
name="bpelx:remoteFault">
<condition>
<action ref="ora-retry-with-intervention"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
name="bpelx:bindingFault">
<condition>
<action ref="ora-rethrow-fault"/>

</condition>
</faultName>
</Conditions>
<Actions>
<Action id="ora-retry-with-intervention">
<retry>
<retryCount>3</retryCount>
<retryInterval>1</retryInterval>
<retryFailureAction ref="ora-human-intervention"/>
</retry>
</Action>
<Action id="ora-retry">
<retry>
<retryCount>3</retryCount>
<retryInterval>1</retryInterval>
<retryFailureAction ref="ora-rethrow-fault"/>
</retry>
</Action>
<Action id="ora-rethrow-fault">
<rethrowFault/>
</Action>
<Action id="ora-human-intervention">
<humanIntervention/>
</Action>
<Action id="ora-terminate">
<abort/>
</Action>
</Actions>
</faultPolicy>
<faultPolicy version="2.0.1" id="RejectedMessages">
<Conditions> 
<faultName xmlns:rjm="http://schemas.oracle.com/sca/rejectedmessages" name="rjm:PartnerLinkName">

<condition>
<action ref="writeToFile"/> 
</condition>
</faultName>
</Conditions>
<Actions> 
<Action id="writeToFile">
<fileAction>
<location>Server/Loc/path</location>
<fileName>Rejected_AJBFile_%ID%_%TIMESTAMP%.xml</fileName>
</fileAction>
</Action>
</Actions>
</faultPolicy>
</faultPolicies>
Fault Binding:
``````````````
<?xml version='1.0' encoding='UTF-8'?>
<faultPolicyBindings version="2.0.1"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<composite faultPolicy="ProcessNameGenericPolicy"/>
<service faultPolicy="RejectedMessages">
<name>PartnerLinkName</name>
</service>
<reference faultPolicy="RejectedMessages">
<name>PartnerLinkName</name>
</reference>
</faultPolicyBindings>
We have SyncFileRead partner link.
The expectation is: when the message read by SyncFileRead partner link is rejected,
that rejected message should come to particular directory in the server.
Could you please help us fixing this.
TIA.

HI..
Have a look at this blog :
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 XI Adapter, then your port entry should J2EE port 5<System no>
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
Http* Errors in XI
Thanks,
Pooja

HTTP_RESP_STATUS_CODE_NOT_OK (401)

Similar Messages

Maybe you are looking for