Error Opening Web Service Navigator

[Former Member]

I am trying to publish an ABAP Function Module as a Web Service using SOAMANAGER. I can can see that the following are working

Open porttype WSDL document

Open WSDL document for selected binding

But the "Open Web Service navigator for selected binding" is coming up with the error below

___________

Error Message

Service cannot be reached

What has happened?

URL http://host:port/wsnavigator/jsps/explorer.jsp call was terminated because the corresponding service is not available.

Note

■The termination occurred in system M2P with error code 404 and for the reason Not found.

■The selected virtual host was 0 .

What can I do?

■Please select a valid URL.

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

ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:m2bm2p_M2P_07-v:0-s:404-r:Notfound

HTTP 404 - Not found

Your SAP Internet Communication Framework Team

-

---

Can you help me troubleshoot this error?

Thanks,

Manoj

Edited by: Trevor Naidoo on Nov 1, 2010 10:11 AM

[Former Member · Accepted solution]

Hi Manoj,

Have you activated the service using TCode SICF?

Path: /default_host/sap/bc/srt/xip/sap/(your service name)

Please also refrain from posting host & port details of your system on SDN, I've edited your URL accordingly.

Regards, Trevor

Edited by: Trevor Naidoo on Nov 1, 2010 10:10 AM

[Former Member · Accepted solution]

Trevor, thanks for the help. Yes, the service is activated SICF.

[Former Member · Accepted solution]

Manoj, another possibility is that not all the WebDynpro services have been activated in SICF.

Refer to this thread where I've referenced a useful guide that indicates some WebDynpro services that can be checked for activation in TCode SICF:

[;

Regards, Trevor

[Former Member · Accepted solution]

Thanks Trevor. I followed the instructions from the link, the J2EE settings are ok but I found that WSNAVIGATOR is not working.

Here is the error I got

http://host:port/wsnavigator call was terminated because the corresponding service is not available.

What do you think I should do?

Thanks,

Manoj

[Former Member · Accepted solution]

Hi Manoj,

There's a couple of important points to remember here:

1. WSNavigator needs a Java stack to run. If you have only an Abap stack but you have a Java stack (e.g.a Portal installation) somewhere else in you landscape then you can use that too. If that's the case, i.e. you have a Java stack somewhere else, then your settings (at the bottom of page 3 of the guide) must point to that Java Application Server.

2. The other important point to remember is that all the required services (for WebDynpro applications like those in the 'Services Activation' section at the top of page 3 of the guide) need to be activated in the ECC (Abap stack) application server that you're launching TCode SOAMANAGER from.

3. It could be that you user authorisations are insufficient, you can reference the previous forum posting I referred to to see a list of possible authorisations.

4. If your Java stack is a separate installation (e.g. Portal) and you've referenced it as in point 1 then you might want to check if the WSNavigator on that Java stack is allowed to test Web Services on other systems by adding the systems to the WSNavigator white list in Netweaver Administrator on the Portal Java Application Server as per this help guide:

[http://help.sap.com/saphelp_nwce711core/helpdata/en/30/2b552f20da49e291c9d26b675f9019/content.htm]

5. If you have an HTTP network proxy configured in your environment, you'll also need to configure those proxy setting on the Java application server where WSNavigator runs as per this help guide:

[http://help.sap.com/saphelp_nwce711core/helpdata/en/48/1d3a6498f633f4e10000000a42189d/content.htm]

6. You can also reference the above link for Web Service Test Scenarios.

If all else fails, ask your basis guy to fix it

Regards, Trevor

[Former Member · Accepted solution]

Trevor Thanks so much for the detailed steps. The BASIS asked me to switch to a new port and WSNavigator worked. I then tested my Web Service, after I put in my request, the response is failing with the error below

SRT:Authorization Denied

Response

-

---

HTTP/1.1 500 Internal Server Error

content-type: text/xml; charset=utf-8

content-length: 1762

accept: text/xml

sap-srt_id: 20101103/161319/v1.00_final_6.40/DFE786CAF2A427F18533000C2911DE31

server: SAP Web Application Server (1.0;701)

<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"><soap-env:Header></soap-env:Header><soap-env:Body><soap-env:Fault><faultcode>soap-env:Server</faultcode><faultstring xml:lang="en">SRT: Authorization denied</faultstring><detail><ns:SystemFault xmlns:ns="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/"><Host>Provider</Host><Component>SECURITY</Component><ChainedException><Exception_Name>CX_SOAP_CORE</Exception_Name><Exception_Text>SRT: Authorization denied</Exception_Text></ChainedException></ns:SystemFault><ns:SystemFault xmlns:ns="http://www.sap.com/webas/711/soap/runtime/abap/fault/system/"><Host>Provider</Host><Component>SECURITY</Component><ChainedException asx:root="asx:abap" version="1.0" xmlns:asx="http://www.sap.com/abapxml"><asx:values><EXCEPTION href="#o190"></EXCEPTION></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="o190"><CX_ROOT><TEXTID>0018FE864EEE1DECA69CF9C71ACB337F</TEXTID><PREVIOUS></PREVIOUS><KERNEL_ERRID></KERNEL_ERRID><INTERNAL_SOURCE_POS><PROGID>99</PROGID><CONTID>1077</CONTID></INTERNAL_SOURCE_POS></CX_ROOT><CX_NO_CHECK></CX_NO_CHECK><CX_SOAP_CORE><E_LOCATION><CLASS>CL_WS_SECURITY_PROTOCOL</CLASS><METHOD>AUTHORITY_CHECK</METHOD><ID>0</ID></E_LOCATION><E_TEXT>SRT: Authorization denied</E_TEXT><E_ID>1100</E_ID><E_FAULT_LOCATION>1</E_FAULT_LOCATION><E_AREA>SECURITY</E_AREA><E_HOST>1</E_HOST><E_PROCESS_CONTROL></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>

-

---

I have asked BASIS to provide the roles you pointed me to.

Does anything stand out to you when you look at this giant response message?

Thanks,

Manoj

[Former Member · Accepted solution]

I just wanted to add that my WSDL is on a different port from WSNAVIGATOR. Do you think that will pose a problem? If so how do I shift to the new port?

Manoj

[Former Member · Accepted solution]

Hi Manoj,

The problem is most likely related to this thread:

[;

Get someone from authorizations to assist you. You'll need to have either the role SAP_BC_WEBSERVICE_CONSUMER or SAP_BC_WEBSERVICE_ADMIN

assigned to the user you're using. Then in TCode PFCG you'll need to check that that both of the roles above have the underlying authorization

object called 'S_SERVICE'. If not, re-generate them in TCode PFCG until you have all green lights there. Then re-test your webservice with WSNavigator.

At least you're starting to get more generic errors now that you'll find by searching in SDN. I think you should be able to tackle them yourself from here.

Regards, Trevor

[Former Member]

Thanks Trevor the security changes you directed me to did the trick