401 unauthorized in RWB ?

[Former Member]

Hi Guys,

I am testing the scenario RFC-HTTP in RWB. I used my id and pw which was copied to pisuper while sending the message and i am getting 401 unauthorized.

I am posting the xml messages to the following url

http://sapdev03:50000/MessagingSystem/receive/AFW/XI

which user id and pw shld be used while testing messages in the rwb corresponding to the above url ?

any help would be apreciated

Thanks,

srini

[agasthuri_doss]

Hi,

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 )

4) Check the note 764176

Regards

Agasthuri Doss

[Former Member]

Hi Srinivas,

this may help you

Regards,

Ram

[Former Member]

Hey

guess ur URL is wrong

change it as per the following

/people/michal.krawczyk2/blog/2005/08/25/xi-sending-a-message-without-the-use-of-an-adapter-not-possible

thanx

ahmad

[Former Member]

Hi Ahmad,

I have changed the url to http://sapdev03:8000/sap/xi/engine?type=entry

I used my id and pw and i am still getting the same error.

In SICF transaction the id and pw for adapter_plain was set to TOAPPLUSER which was copied to piappluser. Is this user id and pw giving a conflict ?

Thanks,

srini

[Former Member]

did u log out and then login again after the password was changed

thanx

ahmad

[Former Member]

Hi Ahmad,

I have resolved the issue, the admin was using one single master pw for all users and it is giving 401 unauthorized errors for other id and pw.

How to make it work for my id and pw ?

Thanks,

srini

[Former Member]

Kapu,

Have you seen this weblog for some analysis on this error:

/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

---Satish

[Former Member]

Hey

>>I have resolved the issue, the admin was using one single master pw for all users and it is giving 401 unauthorized errors for other id and pw.

is ur scenario working with the master password?if yes then there is something wrong with ur authorizations or ur password.

thanx

ahmad

[Former Member]

Hi Ahmad,

I have send the message and i found error in the rwb as below

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

<SAP:P2>Unauthorized</SAP:P2>

<SAP:P3 />

<SAP:P4 />

any help would be appreciated

Thanks,

srini

[Former Member]

Hi -

After some of the bad logins, make sure your user isn't locked - use SU01.

Regards,

Jin

[Former Member]

Hi Jin,

ya u r right. The user id TOAPPLUSER which was copied to piappluser was locked. This id was used in sicf transaction. I htink i shld test it now.

Thanks,

srini

[Former Member]

Hi Jin,

I have changed the pw in sicf to piisuser and now when i test the messages in the sxmb_moni, i am getting the HTTP_RESP_STATUS_CODE_NOT_OK error.

I have RFC-HTTP type scenario. I have created a rfc destination of type G to the external server and made the test connection and it was ok.

I am getting this because of 3rd party system resoponse problem ?

Thanks,

srini

[Former Member]

Hi Srini -

If I understand you correctly, you've used RWB test tool to send a message to XI's pipeline url (i.e. .../sap/xi/engine?type=entry) and now you see that the message has made it into XI and in MONI you see this 401. Correct?

What pipeline step in MONI (e.g. Call Adapter) does the error occur? Based on what you described, yes, I'd say that the 401 now is coming from your target system. In your receiver HTTP channel, are you using/referring to the sm59 destination that you have created and tested successfully with?

Regards,

Jin

[agasthuri_doss]

Hi,

1) Did you maintain Client, userid, password, and lang information in SICF transaction -> sap/xi/engine ? Double click on service and check whether you have entered valid one.

2) check whether r the user is locked or not.

3) check the role of that user Role must be a green indicator in SU01 of XI server.

4) check ur http port that you are using in IS pipeline

http://>host>:8020/sap/xi/engine?type=entry

5)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

Regards

Agasthuri Doss

[Former Member]

Hi Jin,

yu r right. I maintained a RFC dest in sm59 for the target 3 rd party system.

Thanks,

srini

[Former Member]

Hi Agasthuri,

I have maintained the client and user i am maintaning is PIISUSER in sicf. Is it correct or do i need to change it to PIAPPLUSER.

In moni the call is failing at integration server.

help would be appreciated

Thanks,

srini

Message was edited by:

srinivas kapu

[Former Member]

Hey

yeah PIISUSER should work fine

thanx

ahmad

[Former Member]

Hi Srini -

If you see your message in MONI as you indicated above, it has made it to the Integration Engine. At this point, SICF settings have nothing to do with any error you see in MONI. You mentioned that you created a type G sm59 destination and that you've tested the connection and is working fine. Assuming this is the case, then make sure in your HTTP receiver adapter channel configuration that you are referencing the sm59 destination correctly.

Regards,

Jin

[Former Member]

Hi Jin,

I am still getting the following error, i think it is failing at the call integration server

plz see the error

body { font-family:tahoma,helvetica,sans-serif;color:#333333;background-color:#FFFFFF; }td { font-family:tahoma,helvetica,sans-serif;font-size:70%;color:#333333; }h1 { font-family:tahoma,helvetica,sans-serif;font-size:160%;font-weight:bold;margin-top:15px;margin-bottom:3px;color:#003366; }h2 { font-family:verdana,helvetica,sans-serif;font-size:120%;font-style:italic;font-weight:bold;margin-top:6px;margin-bottom:6px;color:#999900; }p { font-family:tahoma,helvetica,sans-serif;color:#333333;margin-top:4px;margin-bottom:4px; }ul { font-family:tahoma,helvetica,sans-serif;color:#333333;list-style-type:square;margin-top:8px;margin-bottom:8px; }li { font-family:tahoma,helvetica,sans-serif;color:#33333;margin-top:4px; }.emphasize .note a { font-family:tahoma,helvetica,sans-serif;text-decoration:underline;color:#336699; }a:visited a:hover { text-decoration:none; }</style></head><body><table cellpadding="0" cellspacing="0" border="0" width="100%"><tr><td>h1. Anmeldung fehlgeschlagen <br>h2. Was ist passiert ? <p>Der Aufruf der URL http://sapdev03:8000/sap/xi/engine wurde aufgrund fehlerhafter Anmeldedaten abgebrochen.</p></td></tr><tr><td> </td></tr><tr><td class="emphasize">*Hinweis*<br>Die Anmeldung wurde im System XID ausgeführt. Hierbei wurden keine Anmeldedaten bereitgestellt.</td></tr><tr><td> </td></tr><tr><td><p>  </p>h2. Was können Sie tun ? <ul><li> Falls Sie noch über keine Benutzerkennung verfügen, so wenden Sie sich an Ihren Systemadministrator. </li></ul><br/><p class="note">Fehlercode: ICF-LE-http-c:200-l:-T:-C:6-U:-P:-L:6</p><br/><p> HTTP 401 - Unauthorized<br/><p> Ihr SAP Internet Communication Framework Team</p></td></tr></table></body></html></SAP:AdditionalText> <SAP:ApplicationFaultMessage namespace="" /> <SAP:Stack>HTTP response contains status code 401 with the description Unauthorized Error while sending by HTTP (error code: 401, error text: Unauthorized)</SAP:Stack> <SAP:Retry>N</SAP:Retry> </SAP:Error> - <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"> - <SAP:Hop timeStamp="2007-05-02T15:23:02Z" wasRead="false"> <SAP:Engine type="BS">com_apachecorp_XID_200</SAP:Engine> <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter> <SAP:MessageId>044503D0-F8C1-11DB-82FF-00144F653722</SAP:MessageId> <SAP:Info>3.0</SAP:Info> </SAP:Hop> </SAP:HopList> - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SAP:Date>20070502</SAP:Date> <SAP:Time>102302</SAP:Time> <SAP:Host>sapdev03</SAP:Host> <SAP:SystemId>XID</SAP:SystemId> <SAP:SystemNr>00</SAP:SystemNr> <SAP:OS>SunOS</SAP:OS> <SAP:DB>ORACLE</SAP:DB> <SAP:Language /> <SAP:ProcStatus>023</SAP:ProcStatus> <SAP:AdapterStatus>000</SAP:AdapterStatus> <SAP:User>PIISUSER</SAP:User> <SAP:TraceLevel>1</SAP:TraceLevel> <SAP:LogSeqNbr>000</SAP:LogSeqNbr> <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr> <SAP:PipelineIdInternal>SAP_SENDER</SAP:PipelineIdInternal> <SAP:PipelineIdExternal>SENDER</SAP:PipelineIdExternal> <SAP:PipelineElementId>FEC5B93B44BBA66BE10000000A1148F5</SAP:PipelineElementId> <SAP:PipelineService>PLSRV_CALL_INTEGRATION_SERVER</SAP:PipelineService> <SAP:QIdInternal /> <SAP:CommitActor>X</SAP:CommitActor> <SAP:SplitNumber>0</SAP:SplitNumber> <SAP:NumberOfRetries>0</SAP:NumberOfRetries> <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries> <SAP:TypeOfEngine client="200">SND_CENTR</SAP:TypeOfEngine> <SAP:PlsrvExceptionCode /> <SAP:EOReferenceRuntime type="TID" /> <SAP:EOReferenceInbound type="TID" /> <SAP:EOReferenceOutbound type="TID" /> <SAP:MessageSizePayload>1030</SAP:MessageSizePayload> <SAP:MessageSizeTotal>2884</SAP:MessageSizeTotal> <SAP:PayloadSizeRequest>1030</SAP:PayloadSizeRequest> <SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap> <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse> <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap> <SAP:Reorganization>INI</SAP:Reorganization> <SAP:AdapterInbound>IENGINE</SAP:AdapterInbound> <SAP:AdapterOutbound>AENGINE</SAP:AdapterOutbound> <SAP:InterfaceAction>INIT</SAP:InterfaceAction> <SAP:RandomNumber>15</SAP:RandomNumber> <SAP:AckStatus>000</SAP:AckStatus> <SAP:SkipReceiverDetermination /> </SAP:RunTime> - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30"> - <SAP:RunTimeItem> <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name> <SAP:Timestamp type="begin" host="sapdev03">20070502152302.191351</SAP:Timestamp> </SAP:RunTimeItem> - <SAP:RunTimeItem> <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name> <SAP:Timestamp type="end" host="sapdev03">20070502152302.214701</SAP:Timestamp> </SAP:RunTimeItem> - <SAP:RunTimeItem> <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name> <SAP:Timestamp type="begin" host="sapdev03">20070502152302.21571</SAP:Timestamp> </SAP:RunTimeItem> - <SAP:RunTimeItem> <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name> <SAP:Timestamp type="end" host="sapdev03">20070502152302.219746</SAP:Timestamp> </SAP:RunTimeItem> - <SAP:RunTimeItem> <SAP:Name type="PLSRV">PLSRV_CALL_INTEGRATION_SERVER</SAP:Name> <SAP:Timestamp type="begin" host="sapdev03">20070502152302.221322</SAP:Timestamp> </SAP:RunTimeItem> - <SAP:RunTimeItem> <SAP:Name type="PLSRV">HTTP_SEND</SAP:Name> <SAP:Timestamp type="begin" host="sapdev03">20070502152302.230669</SAP:Timestamp> </SAP:RunTimeItem> - <SAP:RunTimeItem> <SAP:Name type="PLSRV">HTTP_SEND</SAP:Name> <SAP:Timestamp type="end" host="sapdev03">20070502152302.270981</SAP:Timestamp> </SAP:RunTimeItem> - <SAP:RunTimeItem> <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name> <SAP:Timestamp type="end" host="sapdev03">20070502152309.004616</SAP:Timestamp> </SAP:RunTimeItem> </SAP:PerformanceHeader> - <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"> <SAP:TraceLevel>Information</SAP:TraceLevel> <SAP:Logging>Off</SAP:Logging> </SAP:Diagnostic> - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"> <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" /> - <!-- ************************************ --> <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace> <Trace level="1" type="T">COMMIT is done by XMB !</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 = XID</Trace> <Trace level="1" type="T">client = 200</Trace> <Trace level="1" type="T">language = E</Trace> <Trace level="1" type="T">user = PIISUSER</Trace> <Trace level="1" type="Timestamp">2007-05-02T15:23:02Z 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 = 044503D0F8C111DB82FF00144F653722</Trace> <Trace level="1" type="T">PLNAME = SENDER</Trace> <Trace level="1" type="T">QOS = BE</Trace> <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" /> - <!-- ************************************ --> <Trace level="1" type="T">Get definition of external pipeline SENDER</Trace> <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" /> <Trace level="1" type="T">Corresponding internal pipeline SAP_SENDER</Trace> <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" /> <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER" /> - <!-- ************************************ --> - <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="T">URL for integration server read from global configuration</Trace> <Trace level="1" type="T">URL= http://sapdev03:8000/sap/xi/engine?type=entry</Trace>; - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP"> <Trace level="1" type="System_Error">HTTP-client: error response= <!DOCTYPE html PUBLIC"-//W3C//DTD HTML 4.01Transitional//EN"><html><head><title>Logon Error Message</title><META http-equiv="Content-Type" content="text/html;charset=UTF-8"><style type="text/css">body { font-family:tahoma,helvetica,sans-serif;color:#333333;background-color:#FFFFFF; }td { font-family:tahoma,helvetica,sans-serif;font-size:70%;color:#333333; }h1 { font-family:tahoma,helvetica,sans-serif;font-size:160%;font-weight:bold;margin-top:15px;margin-bottom:3px;color:#003366; }h2 { font-family:verdana,helvetica,sans-serif;font-size:120%;font-style:italic;font-weight:bold;margin-top:6px;margin-bottom:6px;color:#999900; }p { font-family:tahoma,helvetica,sans-serif;color:#333333;margin-top:4px;margin-bottom:4px; }ul { font-family:tahoma,helvetica,sans-serif;color:#333333;list-style-type:square;margin-top:8px;margin-bottom:8px; }li { font-family:tahoma,helvetica,sans-serif;color:#33333;margin-top:4px; }.emphasize .note a { font-family:tahoma,helvetica,sans-serif;text-decoration:underline;color:#336699; }a:visited a:hover { text-decoration:none; }

Thanks,

srini

[Former Member]

Hi Srini -

<i>>>><!-- Call Integration Server --></i>

I've never seen this except if the sender is a proxy sender. Are you using a proxy sender? How are you sending your data to the Integration Server? I think now you have to provide in detail exactly how you've implemented your scenario and how you are testing it.

Incidentally, the vast majority of XI customers do not populate a client/user/password in the SICF service (.../sap/xi/engine).

Regards,

Jin

[Former Member]

Hi Jin,

I have configured a RFC-HTTP scenario sysnchronus on both the side. I am not using any proxy. I have configured HTTP receiver and there i have used HTTP destination. For this i have created a RFC of type G in sm59 for the third party system. I have given the ip address, port: 80, path: /xxxx.asp and thats all.

I tested this HTTP connection and it was success and in the response body of the result tab i have the following error

The XML page cannot be displayed

Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.

Reference to undeclared namespace prefix: 'Tobin'. Error processing resource 'file:///C:/Documents and Settings/srinivas.ka...

<body><doc:FDN.Notify.Exception xmlns:doc="urn:sap-com:document:sap:business" xmlns=""><Tobin:Fault xmlns:do...

I have the following in the response text

HTTP/1.1 200 OK

Set-Cookie: ASPSESSIONIDASQDSRRD=EOOJMCODLKCMFJAEOINECEOI; path=/

Content-Type: TEXT/XML

server: Microsoft-IIS/5.0

date: Wed, 02 May 2007 18:09:49 GMT

x-powered-by: ASP.NET

connection: Keep-Alive

Content-Length: 696

cache-control: private

<?xml version="1.0"?><biztalk_1 xmlns="urn:biztalk-org:biztalk:biztalk_1"><header><delivery><message><messageID>10315554</messageID><sent>2007-05-02T13:09:49</sent><subject>EP Funds Deletion Notification Execption</subject></message><to>

<address>DEV200

</address></to><from>

<address>LDDEV

</address></from></delivery></header>

<body><doc:FDN.Notify.Exception xmlns:doc="urn:sap-com:document:sap:business" xmlns=""><Tobin:Fault xmlns:doc="urn:sap-com:document:sap:business" xmlns=""><FAULTCODE>100</FAULTCODE><FAULTSTRING>Null SAP XML</FAULTSTRING><detail><NAME></NAME><MESSAGE><TEXT></TEXT></MESSAGE></detail></Tobin:Fault></doc:FDN.Notify.Exception>

</body></biztalk_1>

I have taken the xml from the request mapping source after giving some source values and tested in the Test message tab in the RWB and while testing i have used PIISUSER

I did not maintain any client, id and pw in sicf logon details. when i send the message from the rwb and in moni i am getting the INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK

any help would be appreciated

Thanks,

srini

[Former Member]

Hi Guys,

I have solved the issue, i have the client, user id and pw in sicf transaction and evrything was fine. I have used PIAPPLUSER, 001 and pw.

Thanks,

srini