cancel
Showing results for 
Search instead for 
Did you mean: 

Error in WSDL parsing: Exception occurred in library handler

Lukas_Weigelt
Active Contributor
0 Kudos

Hi,

EDIT: System Information ECC 6.0 EHP4 SP 51 STack 11

first of all, sorry in advance in case this issue doesn't belong in this subforum; but this forum was the closest sounding one I found concerning my problem.

I'm trying to create a logical port in Transaction SOAMANAGER by means of a WSDL. However, the following error is thrown:

Error in WSDL parsing: Exception occurred in library handler

There's no further explanation from the system, no long text, nothing. Debugging didn't help either.

I've searched through SCN, google in general, SAPxSearch and SapNote Library. I found many open threads describing the same problem but not a single solution for this.... I tried consuming this Webservice outside of SAP via the Program SoapUI (in case anybody knows this...) and it works perfectly fine. The problem resides in SAP, not with the Service/WSDL.

Can anybody help here? This is direly frustrating...

EDIT: after debugging into about 50 billion levels in the callstack, I found the root cause of this misery. Maybe somebody with more expertise in WSDL/Webservices/SOAP than me (shouldn't be hard ) can explain WHY this is going wrong or why this error is "genuine"...:

CL_SLIB_GENERIC_URI===========CP / CL_SLIB_GENERIC_URI===========CM001

METHOD / CONSTRUCTOR

...

* base uri
   if me->is_relative_uri_ref( ) eq abap_true and m_base_obj is initial.
     m_err_msg = 'Relative URI &1 erfordert Angabe einer absoluten Base-URI'(e01).
     l_uri = me->compose_components( ).
     replace first occurrence of '&1' in m_err_msg with l_uri.
     raise exception type cx_slib_generic_uri
           exporting textid  = cx_slib_generic_uri=>base_uri_error
                     message = m_err_msg.
   endif.

...


That's the target namespace from my WSDL:

<s0:definitions targetNamespace="de.bahn.mep.bahndirekt.publicservices.b2bretrieval" xmlns="" xmlns:s0="http://schemas.xmlsoap.org/wsdl/" xmlns:s1="java:de.bahn.mep.bahndirekt.auftrag.b2bretrieval" xmlns:s2="de.bahn.mep.bahndirekt.publicservices.b2bretrieval" xmlns:s3="http://schemas.xmlsoap.org/wsdl/soap/">

Cheers, Lukas

Message was edited by: Lukas Weigelt

Message was edited by: Lukas Weigelt

Accepted Solutions (0)

Answers (4)

Answers (4)

Oh, Chad,

Thanks so much, this solved it for me:

  1. Execute TA SPROXSET.
  2. Create a new parameter NO_RPC_STYLE with your username and set the value to 'X'

Marius.

jjairoph
Explorer
0 Kudos

It solve my issue, thanks a lot

Former Member
0 Kudos

Lukas,

Refer to the "Error handling in proxy generation" section of the following link:

http://wiki.scn.sap.com/wiki/display/Java/Consume+SOAP+WebService+by+SAP+and+add+custom+Header

Depending on your WSDL type, you may need to make an entry in table SPROXSET via SM30.

Regards,

Chad

0 Kudos

Hi Lukas,

I am also facing the same issue. Could you please update the steps which you have followed to resolve this?

Thanks and Regards,

Peet.

Lukas_Weigelt
Active Contributor
0 Kudos

bump...

Former Member
0 Kudos

Right, I'm bumped now...

While I recall encountering this error, I can't seem to recall how I managed to resolve it (yes I know, great help that is).

Some suggestions I can offer...

- Check the WSDL (for compliance) using the WSDL Analyzer Tools (SOAMANAGER --> Tools (Tab) --> WSDL Analyzer)

- Try creating the logical port manually (search SCN for some help on this - I think I may have adopted this approach).

- Check that the WSDL has only one port / binding (see bottom of WSDL definition).

Regards, Trevor

Lukas_Weigelt
Active Contributor
0 Kudos

Hi Trevor,

thanks for the hints. Your post gave me back some hope for this forum too, you are the first one to reply to one of my billions of posts for the past few weeks (while I am contributing to other billions of posts).

Would you mind providing a screenshot for the WSDL Analyzer? I can't find it; not sure if it's my stupidity or whether our system doesn't fullfil the requirements (ECC 6.0 EHP4 SP51 Stack 11).

Cheers, Lukas

Former Member
0 Kudos

It's probably a version thing then, I see the following screen:

Regards, Trevor

Lukas_Weigelt
Active Contributor
0 Kudos

Can you provide the SAP_BASIS level of your system? I want to compare with mine:

SAP_BASIS    701    0011

I really want this WSDL Tool, now you've brought it up

Cheers, Lukas

Former Member
0 Kudos

I'm on 7.02 0008 but I recall the tool from a previous version too Lukas. I'll try and research when it was released & revert if I find anything.

Regards, Trevor

Lukas_Weigelt
Active Contributor
0 Kudos

'Aight, thanks a lot Trevor.

marksmyth
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Lucas,

I think the Service-Oriented Architecture (SOA) and SAP forum is the best location for this query. I have moved the thread to this forum and hopefully you will get a better response here.

Regards

Moderator