Not sure where EXACTLY this post belongs because I'm not sure about the cause of the error - Visual Studio, or SSIS or underlying framework or an XML document. I'm starting here because I believe VS shell might be the culprit.
I'm trying to add a web service task via [[Visual Studio 2010 Shell for SQL Server 2012 SSIS]].
I have the wsdl file and the xsd file in the same folder. When I try to reference the wsdl file below, I get the error from Visual Studio:
The root element of a W3C XML Schema should be
<schema>
and its namespace should be 'http://www.w3.org/2001/XMLSchema'.
Also - the same xml/xsd produce perfect .cs proxy code when used with the wsdl.exe tool. And the service gives expected results when called via that code. It's just the Visual Studio 2010 shell for SSIS that is giving the above error.
Here are the first few lines of the 13,000 line wsdl file:
I'm almost positive my error might be related to the bug, because even if I change the location property in <import> element of wsdl to a random filename, I get the same error. Any ideas anyone??
HOLY CR*P! turned out to be that the <import> element in XSD expects a fully qualified (http or https, cannot be c:\ d:\ etc) location property.
Glad that you've solved your problem by yourself, and I come here to confirm and close the issue. If you have anything urgent, please feedback by creating another issue.
Kind regards
Please mark the replies as answers if they help or unmark if not.
Feedback to us
greatbear
Member
160 Points
189 Posts
Visual Studio Shell for SQL Server 2012 Integration Services
Jan 21, 2013 03:09 PM|LINK
Not sure where EXACTLY this post belongs because I'm not sure about the cause of the error - Visual Studio, or SSIS or underlying framework or an XML document. I'm starting here because I believe VS shell might be the culprit.
I'm trying to add a web service task via [[Visual Studio 2010 Shell for SQL Server 2012 SSIS]].
I have the wsdl file and the xsd file in the same folder. When I try to reference the wsdl file below, I get the error from Visual Studio:
The root element of a W3C XML Schema should be and its namespace should be 'http://www.w3.org/2001/XMLSchema'.
Also - the same xml/xsd produce perfect .cs proxy code when used with the wsdl.exe tool. And the service gives expected results when called via that code. It's just the Visual Studio 2010 shell for SSIS that is giving the above error.
Here are the first few lines of the 13,000 line wsdl file:
First few lines of AXLSoap.xsd:
greatbear
Member
160 Points
189 Posts
Re: Visual Studio Shell for SQL Server 2012 Integration Services
Jan 21, 2013 10:35 PM|LINK
I found this documented bug, but the example provided is too complex for me.
http://support.microsoft.com/kb/820122?wa=wsignin1.0
I'm almost positive my error might be related to the bug, because even if I change the location property in <import> element of wsdl to a random filename, I get the same error. Any ideas anyone??
greatbear
Member
160 Points
189 Posts
Re: Visual Studio Shell for SQL Server 2012 Integration Services
Jan 21, 2013 11:51 PM|LINK
HOLY CR*P! turned out to be that the <import> element in XSD expects a fully qualified (http or https, cannot be c:\ d:\ etc) location property.
Angie xu - M...
All-Star
18649 Points
1588 Posts
Microsoft
Re: Visual Studio Shell for SQL Server 2012 Integration Services
Jan 22, 2013 10:34 AM|LINK
Hi greatbear
Glad that you've solved your problem by yourself, and I come here to confirm and close the issue. If you have anything urgent, please feedback by creating another issue.
Kind regards
Feedback to us
Develop and promote your apps in Windows Store