I am trying to prove I can use SSIS to connect to a web service.ÃÂ The WS I am trying to connect to was developed by a vendor and covered by a NDA, but I was able to reproduce the issue with a public WS.
Here are the steps to reproduce the issue:
In the Web Services Connection Manager, I entered http://office.microsoft.com/Research/Providers/MoneyCentral.asmx?wsdl in the URL window.ÃÂ I am able to successfully "test" the connection
I pasted the above link into IE and saved the resulting XML as a .wsdl file on my local machine.ÃÂ In the Web Services Task Editor, General Tab, I specify the path to the .wsdl file and click on "Download WSDL" button.ÃÂ No Issues
When I click on "Input" and select "MoneyCentralRemote"ÃÂ from the drop-down for Service, I receive an error message saying "This version of the Web Services Description Language (WSDL) is not supported"
So the questions are:
Did I perform the above steps correctly?
What WSDL versions are supported in SSIS?
How can I tell what WSDL version was used to create the .wsdl I am trying to access?
If the WSDL is an unsupported version, is there a work-around to fix the issue?

More Related Resource Links

I am finding that in order to have the Web Services Task work successfully the location of the WSDL file has to be on a local drive that SSIS is executing upon.ÃÂ Is the current intended behavior?
In my SSIS task I use a URL path toÃÂ store information extracted from the Web Service.ÃÂ The information is stored on a different server than the one that SSIS is running upon.ÃÂ This works properly without error.
IÃÂ have confirmed that SSIS has appropriate permissions to read/write to that directory on that server.ÃÂ When I attempt to reference the WSDL file (located in the same URL directory that I am saving the information) I get a web services error, 'The Web Services Name is empty, Verify that a valid web service name is available."
When I update the Web Service Task attribute to point to the WSDL file located on a local drive it works correctly.ÃÂ I have confirmed that both WSDL documents are exactly the same.
The behaviorÃÂ seems a little strange...so I must be missing something subtle.
...cordell...

I'm trying to use a Web Service for the first time in SSIS.ÃÂ I have the httpConnection specified, and the test succeeded.ÃÂ I have put in a text file the code below, and renamed the file with a .WSDL extension.ÃÂ I'm getting the error below.ÃÂ What is wrong with my WSDL file?ÃÂ Thanks!
ÃÂ
Could not read the Web Services Description Language (WSDL) file.ÃÂ The input WSDL file is not valid.ÃÂ The follwing error occurred while reading the file.ÃÂ There is an error in XML document (3,3)...
ÃÂ
Code Snippet<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><helloworld xmlns="http://lesl.com/" /></soap:Body></soap:Envelope>

The issue is I didn't find out how to specify mandatory parameters in my WSDL, since ASP.NET Web Services are generated on ?WSDL location, I thought I would do that from Web Method Annotations, but I found no issue.

Also I have been on a pose where the developer could hide WSDL Generation by specifying a custom WSDL Binding. But in my case I need to let other system access ?WSDL location with a Customized WSDL.

The very tools that have helped drive the growing adoption of Web services, and the enabling abstractions that they provide, can often prevent developers from peeking behind the curtains at the XML standards that make up the Web services stack. This article will offer a solution that enables type sharing between proxies created for complementary Web services, while at the same time providing an opportunity to examine the Web Services Description Language (WSDL) and its interaction with the Web services tools you know and love.

WS-Security is a recently proposed specification from Microsoft, IBM, and VeriSign. It has been submitted to OASIS for industry standardization. WS-Security builds on the SOAP specification to provide you with a standard mechanism to exchange secure, signed messages in a Web Services environment.

All versions of Windows 2000 have fax services built in, so sending faxes manually is as easy as setting fax options from the control panel. Faxes can also be sent programmatically in Windows 2000 using either COM Automation or the standard C API. The example in this article uses COM Automation with Visual Basic and MFC to programmatically manage faxing. The objects used for fax transmission, such as the FaxServer and FaxDoc objects, as well as their properties and methods, are explained. Because faxing of files you can't print can be problematic, this process is explained. Finally, this article implements a fax routing extension-a plug-in that exports standard functions and implements routing methods for processing received faxes.

Hi all,
I have an issue that requires me to upgrade to a later SP (currently on RTM), but when I try to install SP3 Database Services cannot be ticked.
Upon inspection I see that its reporting "This update requires language ENU. The language for this product instance MSSQLSERVER is . Download the upadte for langage .", when I check teh Language field to the right it is blank, other parts
however are fine and can be upgraded.
Can you advise please as I don't know how to manually set the language (which is reported inside SQL itself as English (United Kingdom)) and I cannot un/reinstall.
Thanks,
John

I have seutp reporting services successfully, but now i want to generate a proxy to be able to interact progromatically with the reporting services 2008 like I did in 2000 and 2005.ÃÂ I have tried viewing the WSDL from a command like this:
ÃÂ
http://localhost/reportserver/reportservice.asmx?WSDL and I get an error like this:
ÃÂ
The path of the item 'WSDL' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. (rsInvalidItemPath) Get Online Help
Any thoughts?ÃÂ I also tried from WSDL.exe, no dice.
Thanksl
Ben

Hi, everyone!
One company is planning to migrate from File share, where they are storing all company documents, to sharepoint services 3.0, and begin to use document versioning, is it possible to migrate mass of documents to sharepoint services 3.0 ?
Now I have no opportunity to test it, that's the reason why I'm asking.

Hi there,
I have developed some reports using Visual Studio and everything worked fine in the office. Now I'm trying to deploy them on my customer PCs but this process keeps failing.
These reports can be built and even previewed within Visual Studio but they cannot be deployed. Here is the error message I get:
-----------------------------------------
The feature: "The Database Engine instance you selected is not valid for this edition of Reporting Services. The Database Engine does not meet edition requirements for report data sources or the report server database." is not supported in this edition of reporting
services.
----------------------------------------
The versions of the software on my customer machines are:
SQL Server Enterprise 9.0.3282
SQL Server 2005 Management Studio 9.00.4035
SQL Server 2005 Reporting Services Designers 9.00.4035.00
Visual Studio 2005 8.0.50727.42
I believe that changing the edition of the Reporting Services from Designers to Enterprise should fix the deployment error but I did not find a way or setup files to do so.
Many thanks in advance for your help!

Hi,I am new to WCF. I have just gone through sample calculator service examples and have very hazy understanding of WCF. I have one requirement where i need to develop WCF services. I have been provided with WSDL and SCHEMAS and has been asked to develop WCF services part.The client part is ready and they need us to write webservices so they can consume it. Can anyone please xplain how could i begin with and from where ? Also what are schemas (XSD's) used for ? Also how would I make sure that after building webservices I have hosted the webservices in such a way that other people in our network could access them ?I have read forums where you have webservices but need to write clients which can consume it, but not sure how to approach the above requirement. Any help would be greatly appreciated. Please explain it considering I AM NOVICE/BEGINNER. Thanks

Hi
I have some code within a .Net 3.5 library which call a web service.
The web proxy class was created using WSDL command line tool.
Also the library is wrapped within .Net console, for testing the library works, and SQL Server Integration Services custom task, which is intended to use so that it will be part of the ETL process.
If I run the SSIS custom task and console application on a Windows XP everything works as expected.
However I am currently facing a problem where the response from the web service is not being interpreted correctly when running
within the SSIS custom task on windows server 2008 R2, whereas the response from the web service is correctly understood when running the library within console application on the same server.
Has anyone come across this problem before or know any issues with SSIS and .Net libraries which call web services?

I installed an english version of SQL Server 2008 R2 on a German version of WIndows 2008. All the SQL Server programs etc. work in English, except when using the Report Manager (http://localhost/Reports) and the Report Generator, which for some reason are
both in German. I tried to change this via the Report Manager and configuration tools, but to no avail - I can find no setting which affects which language is displayed. Can anyone suggest a solution to this problem?