Access Violation in SQLSRV32.DLL

I have run into an issue with attempting to process a large result set
returned by SQL Server 2000. This issue disappears when we reduce the amount
of data in the database that is available to the query by deleting records
and reappears when we add the data back. I've been able to narrow down the
cause of the issue to be the driver SQLSVR32.dll by using windows debugging
tools. Even running this query in Query Analyzer causes it to hang.
Actually, the timer at the bottom of the window continues to increment the
time but when you try to cancel or stop the query, it says "Attempting to
cancel". Closing the window will cause Query Analyzer to hang. It does not
do this every time. Sometimes it almost immediately fails and the execution
of the query terminates. The number of records in the table is over 188,000
records. Can anyone shed some light as to what may be going on here? Is
there a limit to the amount of data that SQL Server driver can handle? This
is happening at one of our customer sites and we've been able to reproduce
this in house.
The following is the output from the windows debugger:
The output is from executing the query on the one particular table from
within Query Analyzer.
(720.888): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=000000af ebx=0166c6a0 ecx=ffffe0a8 edx=00002020 esi=01668050 edi=00002020
eip=1f9ddfca esp=0188fafc ebp=0188fb64 iopl=0 nv up ei ng nz na pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00010283
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINNT\System32\SQLSRV32.dll -
SQLSRV32!SQLSetEnvAttr+76b5:
1f9ddfca 83250000000000 and dword ptr [00000000],0x0 ds:0023:00000000=??
The following is the output from windows debugger after attempting to run
this query through our application
(7d8.888): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=000000af ebx=02007c98 ecx=ffffe0a8 edx=00002020 esi=02008780 edi=00002020
eip=1f9ddfca esp=000e5594 ebp=000e55fc iopl=0 nv up ei ng nz na pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010283
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINNT\System32\SQLSRV32.dll -
SQLSRV32!SQLSetEnvAttr+76b5:
1f9ddfca 83250000000000 and dword ptr [00000000],0x0 ds:0023:00000000=??
Any insight into this issue will be greatly appreciated!
Hi Bennie,
Have you already found the solution? I have exactly the same problem. I have
a structure size of 512 bytes and SQLFetchScroll can fetch without AV only
71 rows (set with SQLSetStmtAttr(hstmt, SQL_ATTR_ROW_ARRAY_SIZE, (void *)71,
0)). I have W2K Server with MS SQL Server 2K on server side and W2KPro SP4
on client side; both have MDAC 2.8 and MS SQL SP3a updates, KB815495 and
Q832483 patches applied.
Isaiass
"Bennie" <Bennie@.discussions.microsoft.com> wrote in message
news:2AB71598-C001-4E4E-96C6-38E47CD37577@.microsoft.com...
> I have run into an issue with attempting to process a large result set
> returned by SQL Server 2000. This issue disappears when we reduce the
amount
> of data in the database that is available to the query by deleting records
> and reappears when we add the data back. I've been able to narrow down
the
> cause of the issue to be the driver SQLSVR32.dll by using windows
debugging
> tools. Even running this query in Query Analyzer causes it to hang.
> Actually, the timer at the bottom of the window continues to increment the
> time but when you try to cancel or stop the query, it says "Attempting to
> cancel". Closing the window will cause Query Analyzer to hang. It does
not
> do this every time. Sometimes it almost immediately fails and the
execution
> of the query terminates. The number of records in the table is over
188,000
> records. Can anyone shed some light as to what may be going on here? Is
> there a limit to the amount of data that SQL Server driver can handle?
This
> is happening at one of our customer sites and we've been able to reproduce
> this in house.
> The following is the output from the windows debugger:
> The output is from executing the query on the one particular table from
> within Query Analyzer.
> (720.888): Access violation - code c0000005 (first chance)
> First chance exceptions are reported before any exception handling.
> This exception may be expected and handled.
> eax=000000af ebx=0166c6a0 ecx=ffffe0a8 edx=00002020 esi=01668050
edi=00002020
> eip=1f9ddfca esp=0188fafc ebp=0188fb64 iopl=0 nv up ei ng nz na pe
cy
> cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000
efl=00010283
> *** ERROR: Symbol file could not be found. Defaulted to export symbols
for
> C:\WINNT\System32\SQLSRV32.dll -
> SQLSRV32!SQLSetEnvAttr+76b5:
> 1f9ddfca 83250000000000 and dword ptr [00000000],0x0
ds:0023:00000000=??
>
> The following is the output from windows debugger after attempting to run
> this query through our application
> (7d8.888): Access violation - code c0000005 (first chance)
> First chance exceptions are reported before any exception handling.
> This exception may be expected and handled.
> eax=000000af ebx=02007c98 ecx=ffffe0a8 edx=00002020 esi=02008780
edi=00002020
> eip=1f9ddfca esp=000e5594 ebp=000e55fc iopl=0 nv up ei ng nz na pe
cy
> cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000
efl=00010283
> *** ERROR: Symbol file could not be found. Defaulted to export symbols
for
> C:\WINNT\System32\SQLSRV32.dll -
> SQLSRV32!SQLSetEnvAttr+76b5:
> 1f9ddfca 83250000000000 and dword ptr [00000000],0x0
ds:0023:00000000=??
> Any insight into this issue will be greatly appreciated!