T-SQL debugger now working, but won't step through 1

[ESquared]

I resolved the initial T-SQL debugger problem in SQL Server 2000 Query Analyzer by going to the server and setting the MSSQLSERVER service to run as a domain user with administrative priviliges instead of as "Local System Account."

The debugger does now run on a stored procedure, displaying the return value from my procedure.

[tt]@RETURN_VALUE = 1[/tt]

But when I insert breakpoints and then click go or F5 again, nothing happens. I am currently talking to the sysadmin about this possibly being a "Incorrect DCOM Permission Settings" problem but given that it is actually running I am skeptical.

Does anyone know what to do? Web searches are turning up fruitless... I could search before on an exact error message but this one is harder.

Note: I am not using Visual anything... just trying to run the debugger in the Query Analyzer.

-E

 

[ESquared]

The sys admin did the Incorrect DCOM Permission Settings instructions in the Help and it didn't do anything.

 

[ESquared]

Anyone? Anything? I have since learned that most of the buttons that are greyed-out in the debugger should be active but are not.

I'd sure love to step through code as it is so useful.

 

[SQLSister]

Debugging Complex Stored Procedures. faq183-4314

This can help you out with other ways of debugging. I find that the debugger doesn't seem to work very well for me, so I don't use it.

 

[Erik70NY]

If you are using SQL 2000 SP3, you must run

EXECUTE sp_sdidebug 'LEGACY_ON'

each time SQL server is started in order for
debugger to work properly.

 

[ESquared]

Thanks for your input, Erik70NY. Nice name, btw.

I am using SQL 2000 SP3

And I did run EXECUTE sp_sdidebug 'LEGACY_ON'

And I am now getting a different, albeit quite wonderful message when I try to start the debugger on even the simplest stored procedure:

[tt]ODBC: Msg 0, Level 19, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler: Process 68 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.[/tt]

I think the next step is to see if I can actually run the debugger on the SQL server itself, as I have been attempting to do it from my workstation and I see from online searches that this may or may get the same results.

 

[philhege]

Run for the hills, and restart your server. Level 19's (specifically the C0000005 variety) are nasty boogers that hose memory.

Phil Hegedusich
Senior Web Developer
IIMAK

http://www.iimak.com

-----------
Boy howdy, my Liberal Studies degree really prepared me for this....
-----------
A skeleton walks into a bar, and says "I'll have a beer and a mop.

 

[ESquared]

I did not know that. Thanks.

Good thing it's one of the non-production servers