cancel
Showing results for 
Search instead for 
Did you mean: 

Logon Error when Using soap Web Service

cris_anderson
Explorer
0 Kudos

Hi,

I'm trying to determine why I'm getting the following error message when I submit a Web Service from our Custom Application to SAP. This error is occurring in SAP ECC 6.0 SPS16 (Quality Client) and we do not have the JAVA Stack installed. Our currently Production Installation is SAP ECC 6.0 SPS4 it works with out issues, however the Upgrade to SPS16 has produced alot of differences in web services.

Also note that this service has been tested succesfully using soapUI Version 2.51. and Version 3.5.1 without producing this error.

The user that is being utilized in all tests is an Internet User only. I would also like to know if there is away to trace Internet User authorizatiion issues.

Any help that can be provide is highly appreciated.

Error Message:

-


Logon failed

What has happened?

Call of URL http://bagqs1p1.rac.ray.com:1080/sap/bc/srt/rfc/sap/zwd_material_create/200/zwd_material_create/zwd_...

terminated due to error in logon data.

Note

Logon performed in system AGQ.

Logon performed for client 200, user , and language EN.

What can I do?

Check that you have entered the client, user, and password correctly.

If you do not yet have a user ID, contact your system administrator.

Error Code: ICF-LE-http-c:200-l:E-T:1-C:5-U:84-P:54-L:5

HTTP 401 - Unauthorized

Your SAP Internet Communication Framework Team

-


Sincerely,

Cris Anderson

Accepted Solutions (0)

Answers (3)

Answers (3)

cris_anderson
Explorer
0 Kudos

I did some additional testing using both my Web Application and soapUI and I found the following:

Both of these URLs will succesfully work with Logon Settings established in SICF when executed using soapUI, however the top url will not work when executed from the Web Application but the shorter one will.

http://bagqs1p1.rac.ray.com:1080/sap/bc/srt/rfc/sap/zwd_material_create/200/zwd_material_create/zwd_...

http://bagqs1p1.rac.ray.com:1080/sap/bc/srt/rfc/sap/zwd_material_create

In SICF we noticed that there are unique differences for setting the Logon Settings. The Top Level Node zwd_material_create only requires a few settings (Client, User, Language, Password) along with Security Requirement which we set to Standard and Authentication which is set to Internet User.

The lowest level node zwd_material_create/200/zwd_material_create/zwd_material_create has the same settings exect there is an addition section called Logon Procedure List. Does this have an impact on why soapUI works and the web application does not?

Also, the web application is using Apache AXIS to handle the communication to SAP.

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

hi

if your scenario is WS-PI-SAP i dont know why you define a user in the service (SICF). why dont you create a communication user and use it to access to PI?

cris_anderson
Explorer
0 Kudos

The user we have setup is User Type C "Communications Data". I'm not the person who created this program just the one that has to maintain it and I'm a little lost now that it isn't working.

We are using ENOVIA MatrixOne to Interface data with SAP. In MatrixOne there is a JAVA program the programmer created that sets the URL and appears it is supposed to be setting the User Name and Password however that doesn't appear to work. So the solution they told us was to set the username and password on the Web Service objects in SICF and it fixed our problem, now that we are upgrading to SPS16 this doesn't work the way it used to and now I'm trying to figure out what needs to be fixed.

Ideally, I don't want the username and password set in SICF but I'm not sure how to fix the programming to have it set the Username and Password so far everything I have done has failed until I put the logon settings in SICF as shown in my earlier post.

Thanks.

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

hi criss you missundestand me i didnt say to configure the User in SICF.

the service that is used by ENOVIA must be defined in SAP PI. please copy and paste the URL in your browser and check if it reach to PI.

every sender web service must be created in SAP PI and the sender system use the wsdl that was generated in pi to exchange data.

if i not wrong you interfaces so is WS-PI-SAP.

thanks

cris_anderson
Explorer
0 Kudos

All of the web services were created in SOAManager if that is what you mean by setting them up in SAP PI.

I'm guessing that the HTTP Code 200: OK means they are working correctly.

- <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">

<soap-env:Header />

- <soap-env:Body>

- <soap-env:Fault>

<faultcode>soap-env:Server</faultcode>

<faultstring xml:lang="en">SRT: Wrong Content-Type and empty HTTP-Body received: ("HTTP Code 200 : OK")</faultstring>

- <detail>

- <ns:SystemFault xmlns:ns="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/">

<Host>undefined</Host>

<Component>COREMSG</Component>

- <ChainedException>

<Exception_Name>CX_SOAP_CORE</Exception_Name>

<Exception_Text>SRT: Wrong Content-Type and empty HTTP-Body received: ("HTTP Code 200 : OK")</Exception_Text>

</ChainedException>

</ns:SystemFault>

- <ns:SystemFault xmlns:ns="http://www.sap.com/webas/711/soap/runtime/abap/fault/system/">

<Host>undefined</Host>

<Component>COREMSG</Component>

- <ChainedException asx:root="asx:abap" version="1.0" xmlns:asx="http://www.sap.com/abapxml">

- <asx:values>

<EXCEPTION href="#o176" />

</asx:values>

- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">

- <cls:CX_SOAP_CORE id="o176">

- <CX_ROOT>

<TEXTID>0018FE864EEE1DECA69CF9C71ACB337F</TEXTID>

<PREVIOUS />

<KERNEL_ERRID />

- <INTERNAL_SOURCE_POS>

<PROGID>98</PROGID>

<CONTID>1113</CONTID>

</INTERNAL_SOURCE_POS>

</CX_ROOT>

<CX_NO_CHECK />

- <CX_SOAP_CORE>

- <E_LOCATION>

<CLASS>CL_SOAP_HTTP_TPBND_ROOT</CLASS>

<METHOD>get_http_headers</METHOD>

<ID>3</ID>

</E_LOCATION>

<E_TEXT>SRT: Wrong Content-Type and empty HTTP-Body received: ("HTTP Code 200 : OK")</E_TEXT>

<E_ID>1032</E_ID>

<E_FAULT_LOCATION>1</E_FAULT_LOCATION>

<E_AREA>COREMSG</E_AREA>

<E_HOST>0</E_HOST>

<E_PROCESS_CONTROL />

</CX_SOAP_CORE>

</cls:CX_SOAP_CORE>

</asx:heap>

</ChainedException>

</ns:SystemFault>

</detail>

</soap-env:Fault>

</soap-env:Body>

</soap-env:Envelope>

former_member202208
Active Participant
0 Kudos

Hi Cris,

Did you resolve the above issue? I am also getting the same response, whats the solution?

<faultstring xml:lang="en">SRT: Wrong Content-Type and empty HTTP-Body received: ("HTTP Code 200 : OK")</faultstring>

Thanks,


Former Member
0 Kudos

Did you check your user exist in the system?

Logon performed for client 200, user , and language EN.

you have removed the user name or the error is like this?

if error is like this that means it is not able to read the user name itslef.

So check for that.

Thanks,

Hetal

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

hi

did you check if the user is bloked at SU01?

does the user has the permission to access the WS?

check if any system user is bloked

Edited by: Rodrigo Alejandro Pertierra on Jun 17, 2010 5:28 PM

also see this

http://wiki.sdn.sap.com/wiki/display/XI/Http+Codes

Edited by: Rodrigo Alejandro Pertierra on Jun 17, 2010 5:32 PM

cris_anderson
Explorer
0 Kudos

The user is not blocked. We have assigned the user to the web service in SICF. All web services were tested using soapUI with the username\password not set in SICF and they all ran successfully when the username\password is set in soapUI only. We then tested the username\password setting in SICF and soapUI with no username\password and they were all successful again. We are using the same username\password on all web services so I don't understand why this one is failing.

I do have a question on which level do you populate the logon data, each of the web services has 4 objects in SICF. In SPS4 there was only one object and that object is the one we assigned the Logon Data. In SPS16 using SOAManager it creates 4 Objects:

default_host/sap/bc/srt/rfc/sap/zwd_material_create

default_host/sap/bc/srt/rfc/sap/zwd_material_create/200

default_host/sap/bc/srt/rfc/sap/zwd_material_create/200/zwd_material_create

default_host/sap/bc/srt/rfc/sap/zwd_material_create/200/zwd_material_create/zwd_material_create

We currently have the Logon Data set on:

default_host/sap/bc/srt/rfc/sap/zwd_material_create

default_host/sap/bc/srt/rfc/sap/zwd_material_create/200/zwd_material_create/zwd_material_create

What I can't figure out is why the web services work correctly when using soapUI but fail when using a different application. All of these web services work in SPS4, but there may be some additional differences that I'm unable to identify with the SPS16 Version.

Did the setting of the Username and Password change in SPS16?