Hi there,
Well, there should be at least the “Details >>” button on the “Unable to read WSDL file” error dialog (see attached screenshot err.png).
err.png
There you could hopefully see more descriptive message. This is from Clover version 3.3.M1, maybe you have older one? (By the way, the error message on the picture is caused by entering misspelled WSDL URL, therefore the server replied with something which is not an XML (WSDL), therefore this error message.)
There should be another way how to get to the error message – redirection of standard and error output of the Clover Designer into a file. You can do this (on Windows) with command like this one:
CloverETLDesigner.exe > clover.log 2>&1
executed in directory where you have the Clover Designer installed. Once the Designer is started, try to edit the Operation name of your WebServiceClient as usual. This action should add new line into the clover.log file like this:
Retrieving document at 'http://wsf.cdyne.com/WeatherWS/Weather.asmx?WSDLa'.
and possibly also an error message, e.g.:
[Fatal Error] Weather.asmx?WSDLa:59:19: The element type "br" must be terminated by the matching end-tag "</br>".
Since you write your WS is behind firewall, maybe you need to access the WSDL using a proxy server. This would normally be done by entering WSDL URL in special format into the WebServiceClient, e.g.:
http:(proxy://10.10.10.10:3128)//bwq.moen.com:8020/sap/bc/srt/wsdl/bndg_4FD8D8B8D2015CE9E10000000A0D1C01/wsdl11/allinone/ws_policy/document?sap-client=010
where 10.10.10.10 and 3128 are IP address and port, respectively, of the proxy server. But unfortunately this does not work in current release, it will be fixed in version 3.3.M3. But this isn’t probably your case, because this bug doesn’t result in the “Unable to read WSDL file” error dialog; it just silently fails.
Regards,
Tom