Discussion:
The custom tool 'MSDataSetGenerator' failed. Unable to convert input xml file content to a DataSet.
(too old to reply)
George Jordanov Ivanov
2006-07-13 12:43:01 UTC
Permalink
Hi there,

I experience the following problem. I'm using Visual Studio 2005 Team System
For Software Developers. When I try to add a new DataSet to any kind of
project, I cannot get to the visual DataSet designer. Rather, I get the
following error (all the time no matter what the type project actually is -
Windows app, Web site, etc.):

The custom tool 'MSDataSetGenerator' failed. Unable to convert input xml
file content to a DataSet. Data at the root level is invalid. Line 1,
position 1.

Has anyone experienced the same problem? Any solutions?
Thanks in advance!
George Jordanov Ivanov
Gary Chang[MSFT]
2006-07-14 06:46:06 UTC
Permalink
Hi Geogre,

Thank you posting!
Post by George Jordanov Ivanov
I experience the following problem. I'm using Visual Studio 2005
Team System For Software Developers. When I try to add a
new DataSet to any kind of project, I cannot get to the visual
...
The custom tool 'MSDataSetGenerator' failed. Unable to convert
input xml file content to a DataSet. Data at the root level is invalid.
Line 1,
...
Do you mean whenever you add a new dataset (via 'Add | New Item...'') to
your VS2005 project, you cannot double click it to open it in the visual
DataSet designer; instead, you get the above error message? Please correct
me if misunderstood anything.

Based on the error message, the problem seems to be the new added dataset's
xml data already corrupted. In order to isolate it, I suggest you verify
its corresponding .xsd file's code. You can right click the target .xsd
file in the solution explorer, then in its context menu select the 'Open
With...' option. In the upcoming "Open With" dialog window, choose the
"Source Code (Text) Editor" to open it and review its code.

By the way, the following is an unmodified dataset's .xsd file code for
your reference:

<?xml version="1.0" encoding="utf-8" ?>
<xs:schema id="DataSet1"
targetNamespace="http://tempuri.org/DataSet1.xsd"
elementFormDefault="qualified"
attributeFormDefault="qualified"
xmlns="http://tempuri.org/DataSet1.xsd"
xmlns:mstns="http://tempuri.org/DataSet1.xsd"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
<xs:element name="DataSet1" msdata:IsDataSet="true"
msdata:UseCurrentLocale="true">
<xs:complexType>
<xs:choice maxOccurs="unbounded"></xs:choice>
</xs:complexType>
</xs:element>
</xs:schema>


Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
George Jordanov Ivanov
2006-07-14 12:04:45 UTC
Permalink
Hey Gary,

Thanks so much! I wish I saw your post earlier before I had reinstalled my
VS2005 twice :-) ! I eventually did the same thing you recommend (by chance
and lost any hope) and surprisingly it worked! I actually made a post
yesterday, where I decribe the issue and its solution so if anyone
experience this once again, feel free to read it. The post can be found
here:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=554552&SiteID=1

To summerize, I've recently installed BizTalk 2006 and it has obviously took
over the default DataSet editor so that now all XSD files are firstly opened
with it. However, obviously the BizTalk editor expects another schema and
that is the reason it reports the error on line 1. Nonetheless, no sign that
this error has been generated by BizTalk editor. Anyhow, when right clicked
on the XSD file and chose "Open with..." I fix this issue - now XSD files
are on default opened with "DataSet editor" (not "BizTalk editor").

Cheers,
George Jordanov Ivanov
MCP, MCAD.NET, MCSD.NET
blog.givanov.net
Post by Gary Chang[MSFT]
Hi Geogre,
Thank you posting!
Post by George Jordanov Ivanov
I experience the following problem. I'm using Visual Studio 2005
Team System For Software Developers. When I try to add a
new DataSet to any kind of project, I cannot get to the visual
...
The custom tool 'MSDataSetGenerator' failed. Unable to convert
input xml file content to a DataSet. Data at the root level is invalid.
Line 1,
...
Do you mean whenever you add a new dataset (via 'Add | New Item...'') to
your VS2005 project, you cannot double click it to open it in the visual
DataSet designer; instead, you get the above error message? Please correct
me if misunderstood anything.
Based on the error message, the problem seems to be the new added dataset's
xml data already corrupted. In order to isolate it, I suggest you verify
its corresponding .xsd file's code. You can right click the target .xsd
file in the solution explorer, then in its context menu select the 'Open
With...' option. In the upcoming "Open With" dialog window, choose the
"Source Code (Text) Editor" to open it and review its code.
By the way, the following is an unmodified dataset's .xsd file code for
<?xml version="1.0" encoding="utf-8" ?>
<xs:schema id="DataSet1"
targetNamespace="http://tempuri.org/DataSet1.xsd"
elementFormDefault="qualified"
attributeFormDefault="qualified"
xmlns="http://tempuri.org/DataSet1.xsd"
xmlns:mstns="http://tempuri.org/DataSet1.xsd"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
<xs:element name="DataSet1" msdata:IsDataSet="true"
msdata:UseCurrentLocale="true">
<xs:complexType>
<xs:choice maxOccurs="unbounded"></xs:choice>
</xs:complexType>
</xs:element>
</xs:schema>
Thanks!
Best regards,
Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Gary Chang[MSFT]
2006-07-17 06:48:43 UTC
Permalink
You are welcome, George!

I am glad to know you have already found the root cause of this issue and
fixed. Thanks for sharing this useful experience with us. :)

Have a nice day!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Loading...