Ayende @ Rahienhttp://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Andreas &#214;hlund commented on SSIS & WCF - Not on best termsDid you also try the tip about removing the <xsd:import schemaLocation="http://localhost:50344/MyWebService/Service.svc?<xsd=xsd2" namespace="http://schemas.datacontract.org/2004/07/"/> Part of the WSDL? http://sjbdeveloper.blogspot.com/2007/03/fixing-wcf-ssis-web-service-task.html http://ayende.com/2358/ssis-wcf-not-on-best-terms#comment3http://ayende.com/2358/ssis-wcf-not-on-best-terms#comment3Thu, 03 May 2007 18:17:29 GMTAyende Rahien commented on SSIS & WCF - Not on best termsNope, tried that, and it didn't work. http://ayende.com/2358/ssis-wcf-not-on-best-terms#comment2http://ayende.com/2358/ssis-wcf-not-on-best-terms#comment2Thu, 03 May 2007 14:02:41 GMTTomas Restrepo commented on SSIS & WCF - Not on best termsSo it would appear the problem would be the imported schemas in the WSDL, right? If so, then SSIS would not be the first tool to get confused by them, unfortunately. I wonder if then using the "Inline XSD" extension I created for WCF a while ago on the WCF service would help at all here.... See http://www.winterdom.com/weblog/2006/10/03/InlineXSDInWSDLWithWCF.aspx) http://ayende.com/2358/ssis-wcf-not-on-best-terms#comment1http://ayende.com/2358/ssis-wcf-not-on-best-terms#comment1Thu, 03 May 2007 11:38:17 GMT