Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Error when testing a webservice -> Exception raised in class CL_SOAP_REGIST

Former Member
0 Kudos

Dear coleagues,

I've got an issue concerning the AS ABAP SOAP Runtime. The system is an ERP 6.0 with SP13.

If I try to test the service in WSADMIN by using the test-button, I just get an exception after the internet browser opens:

A Soap Core Exception was raised in Method CL_SOAP_REGISTRY::generate_wsdl(6)

Technical Details of Soap Core Exception

Message Text: SRT: ASSERT failed: object reference not bound

Class: CL_SOAP_REGISTRY

Method: generate_wsdl

LocationID: 6

Program: CL_SOAP_REGISTRY==============CP

Include: CL_SOAP_REGISTRY==============CM00J

Line: 59

I did a look into the coding and think that the exception is raised since the methode

Hi folks,

I've got an issue concerning the AS ABAP SOAP Runtime. The system is an ERP 6.0 with SP13.

At first I create a Web Service by using the context menue of an existing rfc-enabled function module. Afterwards the service is visible in SICF. If I try to test the service in WSADMIN by using the test-button I only get an exception in the opening internet browser:

Cannot download WSDL from http://serverurl:8027/sap/bc/srt/rfc/sap/ZSTMA_FUNKTIONSTEST2?sap-client=100&wsdl=1.1: Invalid Response Code: (400) Bad Request. The requested URL was:"http://ciswi.sap.swm.de:8027/sap/bc/srt/rfc/sap/ZSTMA_FUNKTIONSTEST2?sap-client=100&wsdl=1.1"

If I go onto the used url I get the following message:

Your request could not be processed

SRT: ASSERT failed: object reference not bound

What has happened?

A Soap Core Exception was raised in Method CL_SOAP_REGISTRY::generate_wsdl(6)

Technical Details of Soap Core Exception

Message Text: SRT: ASSERT failed: object reference not bound

Class: CL_SOAP_REGISTRY

Method: generate_wsdl

LocationID: 6

Program: CL_SOAP_REGISTRY==============CP

Include: CL_SOAP_REGISTRY==============CM00J

Line: 59

I did a look into the coding and found out that the exception is raised since

Hi folks,

I've got an issue concerning the AS ABAP SOAP Runtime. The system is an ERP 6.0 with SP13.

At first I create a Web Service by using the context menue of an existing rfc-enabled function module. Afterwards the service is visible in SICF. If I try to test the service in WSADMIN by using the test-button I only get an exception in the opening internet browser:

Cannot download WSDL from http://serverurl:8027/sap/bc/srt/rfc/sap/ZSTMA_FUNKTIONSTEST2?sap-client=100&wsdl=1.1: Invalid Response Code: (400) Bad Request. The requested URL was:"http://ciswi.sap.swm.de:8027/sap/bc/srt/rfc/sap/ZSTMA_FUNKTIONSTEST2?sap-client=100&wsdl=1.1"

If I go onto the used url I get the following message:

Your request could not be processed

SRT: ASSERT failed: object reference not bound

What has happened?

A Soap Core Exception was raised in Method CL_SOAP_REGISTRY::generate_wsdl(6)

Technical Details of Soap Core Exception

Message Text: SRT: ASSERT failed: object reference not bound

Class: CL_SOAP_REGISTRY

Method: generate_wsdl

LocationID: 6

Program: CL_SOAP_REGISTRY==============CP

Include: CL_SOAP_REGISTRY==============CM00J

Line: 59

I found out that the exception is raised since CL_SRT_WSDL_GEN_FACTORY=>GET_WSDL_GENERATOR doesn't return an instance of the class referring to the interface IF_SRT_WSDL_GEN.

If I test that method in SE24 using the name of the service definition in SE80 for the parameter WSD, the value '1' fpr the parameters TYPE and STYLE, an instance of the class CL_SRT_WSDL11_GEN is rendered.

Could you give any hints how I could debug that issue to verify the import parameters when the static method CL_SRT_WSDL_GEN_FACTORY=>GET_WSDL_GENERATOR is called in the body of the browser call ?

Or any other hints?

Thank you very much and best regards

Stefan

1 REPLY 1

Former Member
0 Kudos

The issue was due to missing authorizations of the RFC-user (type 'Communication') calling the webservice. The RFC-user itsself has been assigned before to the webservice in the http-service tree (transaction SICF). RFC-User needs (at least) the role SAP_BC_WEBSERVICE.