November 12, 2012 at 9:24 am
Hello.
I can't successfully create a web service in SQL Integration Services because the next error message appears when I try to enter the input properties of the Web Service Task:
"Could not read the Web Services Description Language (WSDL) file. The input WSDL file is not valid. The following error occurred while reading the file. There is an error in XML document (0, 0).."
Previously I created the HTTP Connection with the respective URL, user and password, tested the connection and downloaded the wsdl. I think that maybe the wsdl downloaded doesn't have the correct format but I don't know why it could be.
I hope you could help me.
Thanks.
November 16, 2012 at 5:02 am
Hi Javierja,
Did you set up the HTTP connection correctly? You need to have the full address of the web service you wish to download the WSDL for in the URL.
e.g. http://<MyReportServer>/ReportServer/ReportService2010.asmx?WSDL
The WSDLFile property in the webservice task editor is path to save the file locally e.g. c:\rs.wsdl.
February 8, 2013 at 2:25 am
I've had very much the same problem, and it's not about setting up the connection properly. When the wsdl file is downloaded (and I've found this with ALL book/online tutorials) there are tags missing. I found this through attempting to open the file in IE. When edited and all opening tags have corresponding closing tags, the error no longer happens. However, on the next stage of the tutorials when the Input tab is selected, there's nothing to select.
I've spent quite a long time looking into this, but can't find any resolutions that work. Quite disheartening really.
February 8, 2013 at 3:42 am
Hi Richard,
I'd be more inclined to think there is a problem on your end rather then ALL the tutorials being wrong.
My point was that when setting up the connection you are in the HTTP connection manager rather then the Web Service Task and therefore testing the connection will suceed as long as a valid URL is entered. The HTTP connection manager is checking the HTTP connection and not whether you are pointing to is a valid webservice or WSDL file.
When you select "download WSDL" the task just downloads whatever is on the end of that URL into the filename specified, again it does not try to validate the WSDL. It is only when you try to list the webservices it finds the badly formed content and provides the error in the original post.
Check it by trying "http://www.google.co.uk" then try "http://wsf.cdyne.com/WeatherWS/Weather.asmx?WSDL"
It's far more likely you are doing something wrong or possibly the webservice you are connecting to is issuing badly a formed reply. Feel free to link the BOL tutorial if you want me to take a look and try to help.
Cheers.
February 8, 2013 at 3:50 am
Thanks for your reply.
I've just connected to the webservice you mention (http://wsf.cdyne.com/WeatherWS/Weather.asmx?WSDL), clicked download, and still get the same error suggesting the xml is badly formed. I've been following the tutorials word for word, step by step and have tried three already. I agree that it seems unlikely they're all wrong, and the the common denominator is me. However, it's baffling.
I create a connection and successfully test it.
Create a string variable.
Drag the webservice task and so on......then the error.
Cheers,
Rich
February 8, 2013 at 4:16 am
Did you definitely overwrite the existing file or choose a new file name?
I've attached the WSDL file I recieve. Could you attach yours?
February 8, 2013 at 4:27 am
Yours works fine, so thanks for that. The files look completely different, so it may well be down to how the file is originally created?
here's mine:
February 8, 2013 at 4:43 am
I get the same file as you if I dont append the "?WSDL" onto the end of the URL.
Can you confirm you definitely did this as the file you attached looks like the output of the webservice test page.
The URL should be exactly as follows: "http://wsf.cdyne.com/WeatherWS/Weather.asmx?WSDL".
You can visit either through your browser
http://wsf.cdyne.com/WeatherWS/Weather.asmx
then
http://wsf.cdyne.com/WeatherWS/Weather.asmx?WSDL
and you should see a difference, the first is the webservice test page the second should be the WSDL definition which looks like a XML file.
If you are not getting a difference I'm not sure what is going wrong.
February 8, 2013 at 4:52 am
Strange one, indeed.
This is the URL I have in my http connection: http://wsf.cdyne.com/WeatherWS/Weather.asmx?WSDL:8080
The latter is just the proxy port.
Thanks for your help with this.
February 8, 2013 at 4:59 am
Don't know much about how your proxy's work but shouldn't it be more like:
http://wsf.cdyne.com:8080/WeatherWS/Weather.asmx?WSDL
Otherwise I think it would be trying to the pass the ":8080" as part of the query in the URL which is why it defaults to the test screen.
Probably one to check with your network guys how to form the URLs so as to work with the proxy.
February 8, 2013 at 5:01 am
You may well be correct, and I'll investigate. However, I don't think I can currently connect without the proxy suffix.
February 8, 2013 at 5:04 am
You're a genius! Thanks. I've now realised that I DON'T need the proxy suffix after all.
August 29, 2016 at 1:47 pm
HI
CAN ANY ONE HELP PLEASE
TITLE: Web Service Task
------------------------------
Could not read the Web Services Description Language (WSDL) file. The input WSDL file is not valid. The following error occurred while reading the file. There is an error in XML document (1, 1)..
------------------------------
BUTTONS:
OK
------------------------------
August 31, 2016 at 11:46 am
lemmae880 (8/29/2016)
HICAN ANY ONE HELP PLEASE
TITLE: Web Service Task
------------------------------
Could not read the Web Services Description Language (WSDL) file. The input WSDL file is not valid. The following error occurred while reading the file. There is an error in XML document (1, 1)..
------------------------------
BUTTONS:
OK
------------------------------
"The input WSDL file is not valid"
Did the preceding posts give you any ideas of where to investigate? Have you looked at the text to see if there are missing tags? Is the URL as described in the posts? Does the user running the task have access to the folder where the file resides? These are some things you can try that come to mind.
----------------------------------------------------
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply