Article ID: 285006 - Last Review: September 26, 2005 - Revision: 5.5 FIX: You receive error message 6603 or text data may be truncated when you select a text data type through the OPENXML provider in SQL Server 2000This article was previously published under Q285006 BUG #: 236142 (Shiloh_bug) On This PageSYMPTOMS When you select character data that is a Text data type through the OPENXML rowset provider, the text data may be truncated or you may receive the following error message: Server: Msg 6603, Level 16, State 1 XML parsing error: System error: 265926. RESOLUTIONSQL Server 2000To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:290211
(http://support.microsoft.com/kb/290211/
)
INF: How to obtain the latest SQL Server 2000 service pack
MDACTo resolve this problem, obtain the latest service pack for Microsoft Data Access Components 2.6. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:300635
(http://support.microsoft.com/kb/300635/
)
INFO: How to obtain the latest MDAC 2.6 service pack
HotfixNote The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 1.The English version of this fix should have the following file attributes or later: Date Version Size File name --------------------------------------------------- 01/23/2001 8.1.7123.0 688,912 Msxml2.dll 01/23/2001 8.1.7123.0 21,776 Msxml2a.dll 01/23/2001 8.1.7123.0 37,648 Msxml2r.dll 01/23/2001 8.1.7123.0 26,384 Xmlinst.exe 318202
(http://support.microsoft.com/kb/318202/
)
MS02-008: XMLHTTP control in MSXML 2.6 can allow access to local files
The security update that is discussed in Microsoft Security Bulletin MS02-008 has the required files (version 8.2.8307.0).STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article. SQL Server 2000This problem was first corrected in SQL Server 2000 Service Pack 1.MDACThis problem was first corrected in Microsoft Data Access Components 2.6 Service Pack 1.MORE INFORMATIONSteps to reproduce the problem
| Article Translations
|
Back to the top
