Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Problem with Web Service Task Expand / Collapse
Author
Message
Posted Monday, November 12, 2012 9:24 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, November 12, 2012 10:05 AM
Points: 2, Visits: 9


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.
Post #1383737
Posted Friday, November 16, 2012 5:02 AM


SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Thursday, August 28, 2014 2:49 AM
Points: 83, Visits: 690
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.



Post #1385610
Posted Friday, February 8, 2013 2:25 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, February 8, 2013 4:49 AM
Points: 14, Visits: 73
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.
Post #1417531
Posted Friday, February 8, 2013 3:42 AM


SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Thursday, August 28, 2014 2:49 AM
Points: 83, Visits: 690
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.





Post #1417572
Posted Friday, February 8, 2013 3:50 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, February 8, 2013 4:49 AM
Points: 14, Visits: 73
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
Post #1417575
Posted Friday, February 8, 2013 4:16 AM


SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Thursday, August 28, 2014 2:49 AM
Points: 83, Visits: 690
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?


  Post Attachments 
weath.zip (4 views, 1.79 KB)
Post #1417588
Posted Friday, February 8, 2013 4:27 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, February 8, 2013 4:49 AM
Points: 14, Visits: 73
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:



  Post Attachments 
weather.rar (5 views, 1.14 KB)
Post #1417591
Posted Friday, February 8, 2013 4:43 AM


SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Thursday, August 28, 2014 2:49 AM
Points: 83, Visits: 690
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.
Post #1417598
Posted Friday, February 8, 2013 4:52 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, February 8, 2013 4:49 AM
Points: 14, Visits: 73
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.
Post #1417602
Posted Friday, February 8, 2013 4:59 AM


SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Thursday, August 28, 2014 2:49 AM
Points: 83, Visits: 690
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.
Post #1417605
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse