Run dynamic SQL in debugger, get sql dump

Hi,
One of our developer runs a stored procedure containing dynamic SQL in
T-SQL Debugger. She consistently gets error ( see below ):
SqlDumpExceptionHandler: Process 73 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
If she runs it without debugger, it runs fine. She checks the code many
times and can't find anything wrong in the code. We have no idea what's
wrong.
The server is a SQL Server 2000 (SP3) on a Window 2000 with service pack
4.
Thank you.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!If memory serves there was a bug with the debugger where
if you run it from the client machine it would either not
work, or result in an error (sorry can't find the
Microsoft Page).
How I solved this is to run the debugger on the server.
One of the Great Ones, Uri, Narayana, Wayne, Dejan, Tibor,
Dan, Andrew or Adam could probably tell you the reason and
the fix.
Peter
"I favor the Civil Rights Act of 1964 and it must be
enforced at gunpoint if necessary."
Ronald Reagan
>--Original Message--
>
>Hi,
>One of our developer runs a stored procedure containing
dynamic SQL in
>T-SQL Debugger. She consistently gets error ( see below ):
>SqlDumpExceptionHandler: Process 73 generated fatal
exception c0000005
>EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating
this process.
>If she runs it without debugger, it runs fine. She checks
the code many
>times and can't find anything wrong in the code. We have
no idea what's
>wrong.
>The server is a SQL Server 2000 (SP3) on a Window 2000
with service pack
>4.
>Thank you.
>
>*** Sent via Developersdex http://www.developersdex.com
***
>Don't just participate in USENET...get rewarded for it!
>.
>|||and Jacco, certinly must not forget Jacco...
Peter
>--Original Message--
>If memory serves there was a bug with the debugger where
>if you run it from the client machine it would either not
>work, or result in an error (sorry can't find the
>Microsoft Page).
>How I solved this is to run the debugger on the server.
>One of the Great Ones, Uri, Narayana, Wayne, Dejan,
Tibor,
>Dan, Andrew or Adam could probably tell you the reason
and
>the fix.
>Peter
>"I favor the Civil Rights Act of 1964 and it must be
>enforced at gunpoint if necessary."
>Ronald Reagan
>
>
>
>>--Original Message--
>>
>>Hi,
>>One of our developer runs a stored procedure containing
>dynamic SQL in
>>T-SQL Debugger. She consistently gets error ( see
below ):
>>SqlDumpExceptionHandler: Process 73 generated fatal
>exception c0000005
>>EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating
>this process.
>>If she runs it without debugger, it runs fine. She
checks
>the code many
>>times and can't find anything wrong in the code. We have
>no idea what's
>>wrong.
>>The server is a SQL Server 2000 (SP3) on a Window 2000
>with service pack
>>4.
>>Thank you.
>>
>>*** Sent via Developersdex http://www.developersdex.com
>***
>>Don't just participate in USENET...get rewarded for it!
>>.
>.
>|||Did you Google for an answer? I searched for below keywords:
c0000005 EXCEPTION_ACCESS_VIOLATION debug
And got some 100 matches. One plausible is http://support.microsoft.com/default.aspx?scid=kb;EN-US;270061.
If you can't find a KB that applies to you, and you are current on service pack, you need to open a case with
MS, since access violations (etc) are most often bugs in SQL Server.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Yanjie Ren" <yren@.cc3.com> wrote in message news:%23lZEgg3iEHA.396@.TK2MSFTNGP12.phx.gbl...
>
> Hi,
> One of our developer runs a stored procedure containing dynamic SQL in
> T-SQL Debugger. She consistently gets error ( see below ):
> SqlDumpExceptionHandler: Process 73 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> If she runs it without debugger, it runs fine. She checks the code many
> times and can't find anything wrong in the code. We have no idea what's
> wrong.
> The server is a SQL Server 2000 (SP3) on a Window 2000 with service pack
> 4.
> Thank you.
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!