on 09-07-2006 2:40 AM
Hi,
In transaction wsconfig I get the error below after transporting the (client dependent transport) release of a Web Service to our QA system. I have transported the client independent transport of the Web Service definition and Virtual Interface in an earlier transport. Can somebody please help me, or let me know where I can find more documentation about transporting Web Services.
=========================================
Original interface does not match Web Service definition
Message no. SRT_REG031
Diagnosis
The information about the original interface stored in the configuration
does not match the definition of the Web Service. This can be the case
if the definition of the Web Service or virtual interface is changed
after the Web Service is released.
Procedure
Change the current settings. If you access the settings in change mode,
the information about the original interface is adjusted automatically.
Save the settings.
=========================================
The Diagnosis in the message suggests that definition of the Web Service or virtual interface has changed, this is not the case.
The procedure recommended in the message to fix the error requires the authorization object S_DEVELOP. Enabling a developer authorization object in a QA or production environment seems inappropriate to me.
Thanks, Murray.
Hello Murray,
Web Services are a new area for SAP. I think you should open a OSS Message in the component BC-DWB-WS-ABA on this topic.
Regards
Gregor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My Issue was caused by missing authorisation.
1) "Check results" in wsconfig is affected by authorisation. ie not having auth object S_DEVELOP in the test system. Perhaps the error message in wsconfig could have been better, I had incorrectly assumed there was an issue with the Web Service rather than my access.
2) When trying to generate the WSDL in the test system (via transaction wsadmin). I was getting the error "SRT: ASSERT failed: object reference not bound". This was also caused by authorisation. Again the error message could have been better, I had incorrectly assumed this was caused by an issue with the Web Service, rather than my access.
Consumption of the Web Service is working correctly.
Hi Murry,
I have exposed RFC as web services.
I can fetch or view WSDL of RFC in the browser with my ID.
But when I tried same thing using service ID, I got following error:
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
What authorizations am I missing?
the type of my User ID is: Dialog User
and type of service Id is: Communication User
Is this a problem?
Please let me know.
It is very urgent for me.
Thanks in advance,
Bhavik
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.