SSIS Web Service Task cannot call Services with a space in the name - by Andy Hinchcliffe

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 368606 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 9/19/2008 4:23:05 AM
Access Restriction Public


If the Web Service is create with the Service name has a space in the name, in the WSDL file the service. The WSDL create in Visual Studio will contain a service name that has the spaces changed to _x0020_. So "My Web Service" will be "My_x0020_Web_x0020_Service". If the Web Service is called from C# then this is not a problem.

However in the SSIS package Web Service Task the service name is shown as "My_x0020_Web_x0020_Service".  You then get a list of the methods, selecting one brings up the list of parameters. Setting all these correctly and clicking OK.

Running the package gives an error saying 'The given service is not currently available.'

If the service name is changed to have no spaces, the SSIS package runs fine.

Checking the IIS logs and the SSIS Package isn't calling the Web Method.

If I download the WSDL to a file and then search and replace all the _x0020_ with empty string and save the WSDL file. Then edit the SSIS package, then the SSIS will call the Web Service correctly. It will correctly call web service which don't have spaces in the name.
Sign in to post a comment.
Posted by Microsoft on 9/17/2009 at 4:06 PM
Spaces are not currently supported in the web service name per WSDL documentation. Visual Studio works around this limitation by replacing the spaces with _x0020_ but the IS task does not have this functionality. We will display an error for this scenario in the next release of SQL Server.

Thank you for reporting it.
Posted by Microsoft on 10/22/2008 at 3:50 PM
Thanks for your feedback, we appreciate it.

We have placed this issue in our next major release planning items. Please expect an update on our progress in a few months.

SSIS Team.