FIX: Second SQLExecute on Prepared Statement with SQL_NOSCAN_ON Causes Client-Side AV

This article was previously published under Q295757
This article has been archived. It is offered "as is" and will no longer be updated.
On an ODBC connection to a SQL Server 2000 server, the second call to the SQLExecute function on a prepared statement may cause a client-side access violation (AV) if the statement attribute SQL_ATTR_NOSCAN is set to SQL_NOSCAN_ON prior to execution.
To 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 theMicrosoft Knowledge Base:
300635 INFO: How to Obtain the Latest MDAC 2.6 Service Pack


The English version of this fix should have the following file attributes or later:

   Date         Version         Size      File name      Platform   --------------------------------------------------------------   11/13/2000   2000.80.221.0   471,119   Sqlsrv32.dll   x86    11/13/2000   2000.80.221.0    28,742   Odbcbcp.dll    x86 				

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Data Access Components 2.6 Service Pack 1.

Article ID: 295757 - Last Review: 02/28/2014 04:27:24 - Revision: 3.2

Microsoft Data Access Components 2.6, Microsoft SQL Server 2000 Standard Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbmdac260sp1fix kbqfe KB295757
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)