Article ID	2082
Article Title	INFO: No WSDL information returned when using the ?WSDL parameter
Article URL	http://www.dataaccess.com/kbasepublic/KBPrint.asp?ArticleID=2082
KBase Category	Visual DataFlex
Date Created	01/25/2005
Last Edit Date	10/02/2013

Article Text
QUESTION:
When I enter "http://localhost/daw.examples.Order_Entry_17/testservice.wso?WSDL" the result in the browser does not look like a WSDL document. It looks like an INI file. It looks like:

[WebService]
Application=DAW.Examples.Order_Entry_17
Object=oTestService
ServicePageGenerator=DefaultWebServiceHomePage.xslt
TestPageGenerator=DefaultWebServiceMethodPage.xslt
WSDLGenerator=DefaultWebServiceDescription.xslt
SoapBodyStyle=document

What is happening?

This issue can also manifest itself as "Error 503 Status 405 Text: Method Not Found"

ANSWER:
What you see is the contents of the testservice.wso file on disk. The browser just displays the file and does not call an application to return the WSDL document. The reason why it does this is most likely a missing .WSO definition inside the IIS application information. Another reason might be an incorrect path to that service.

To check this:
- Start | Programs | Administrative tools
- Select Internet Information Services
- Wait till it is opened
- Browse to your webapplication by expanding the tree. When looking at above example find the entry labeled "Order_Entry_17".
- Double-click the Handler Mappings icon
- Verify that there is a mapping for the .WSO extension (it is probably called something like "AboMapperCustom-44559")

If the .wso extension is missing, click the Add Managed Handler button. If it is there click the Edit... button.

For the value of the executable browse (via the button) to the waswsvc.dll file in the right directory. If you installed Visual DataFlex in the default directory it will be "C:\Program Files\Visual DataFlex 17.0\bin\waswsvc.dll". If you installed VDF somewhere else, find the appropriate DLL name.

NOTE: The path to the location of waswsvc.dll MUST BE entered using its short name. You can obtain the short name for any directory via "dir /x". For example:

On Windows Server 2012, you will have to add a Module Mapping instead of a Managed Handler, choose IsapiModule as the module type and give it a useful name, like "WSO Handler".

dir /x "c:\program files"

If you are adding a new handler, you need to enter the filename extension too. While capitalization is not a problem the extensions are usually listed in lowercase so you will enter ".wso". The DOT is important but you can see this clearly because the OK button stays disabled.




This article is recommended reading for the following keywords and/or categories:
5120
Contributed By:
Vincent Oorsprong
Company: Data Access Worldwide
email: vincent.oorsprong@dataaccess.eu
Web Site: http://www.dataaccess.eu


Email this Article
Email this Article to a Colleague
Send Feedback on this Article to Data Access Worldwide
Copyright ©2024 Data Access Corporation. All rights reserved.

The information provided in the Data Access Technical Knowledge Base is provided "as is" without warranty of any kind. Data Access Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Access Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Access Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.