Select the product you need help with
FIX: Some data rows are missing when you call the ReadXML method to read data from separate DiffGrams for the same DataSet object in the .NET Framework 2.0Article ID: 919532 - View products that this article applies to. Bug #: 782 (SQL Hotfix) On This PageSYMPTOMSIn
the Microsoft .NET Framework 2.0, when you call the ReadXML method to read data from separate DiffGrams for the same DataSet object, you may notice that some data rows are
missing. CAUSEThis problem occurs because a data structure from the
previous DiffGram is not cleared when you call the Clear method of the DataSet object. When you call the ReadXml method for the DataSet object next time, the leftover data structure in the DataSet object causes the DataSet object not to load the deleted rows. RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support Note In special cases, charges that are ordinarily incurred for
support calls may be canceled if a Microsoft Support Professional determines
that a specific update will resolve your problem. The usual support costs will
apply to additional support questions and issues that do not qualify for the
specific update in question.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix, the Microsoft support files that are described in the following Microsoft Knowledge Base article must be installed on the computer:916002
(http://support.microsoft.com/kb/916002/
)
FIX: Error message when you try to use the SqlClient class in an ADO.NET 2.0-based application to connect to an instance of SQL Server 2005: "New request is not allowed to start because it should come with valid transaction descriptor"
Restart requirementYou do not have to restart the computer after you apply this hotfix.Registry informationYou do not have to change the registry.Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel. The .NET Framework 2.0, 32-bit versionCollapse this table
The .NET Framework 2.0, x64-based versionCollapse this table
The .NET Framework 2.0, Itanium architecture versionCollapse this table
WORKAROUNDTo work around this issue, use a different DataSet object for the separate DiffGram instead of reusing the same DataSet object. STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. MORE INFORMATION For more information, click the
following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe
Microsoft software updates
REFERENCESFor more information about the DiffGrams format, visit the
following Microsoft Web site: http://msdn2.microsoft.com/en-us/library/ms172088.aspx
(http://msdn2.microsoft.com/en-us/library/ms172088.aspx)
PropertiesArticle ID: 919532 - Last Review: July 26, 2006 - Revision: 1.1
|
Back to the top
