This article has been archived. It is offered "as is" and will no longer be updated.
Your application uses Microsoft OLE DB Provider for SQL Server (SQLOLEDB). When the SQLOLEDB provider uses the Sqlxmlx.dll file for doing transformation between Transact-SQL commands and XML commands, you may receive an access violation error message.
The access violation occurs in the SQLOLEDB provider because the SQLOLEDB provider tries to dereference an unloaded Sqlxmlx.dll file. The Sqlxmlx.dll file unloads unexpectedly because the Sqlxmlx.dll file contains an incorrect global object count.
To resolve this problem, obtain the latest service pack for Microsoft Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
322389 How to obtain the latest Windows XP service pack
To resolve this problem, you can also obtain the hotfix that is mentioned in the following Microsoft Knowledge Base article:
838976 FIX: SQLOLEDB stops responding when the sqlxmlx.dll file unloads unexpectedly
Note The hotfix that is mentioned in this article can be used to resolve this problem even if this problem occurs on a computer that is not running Microsoft Windows XP.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
When you access the data from a browser and the URL contains XML commands, the Sqlxmlx.dll file translates the XML commands of the URL to Transact-SQL commands. SQL Server 2000I uses the Transact-SQL commands to retrieve the database records, and the Sqlxmlx.dll file formats the database records into an XML document.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information, visit the following Microsoft Developer Network (MSDN) Web sites: