T-SQL Debugger Doesn't Allow Stepping Through Stored Procedures
And there is no other procedure with the same name owned by dbo or any
other users.
There is no error messages also, it just completes procedure and
returns result
server:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build
2195: Service Pack 4) and I don't know how do determine Client's
version.
What should be done (on client site or server site )to fix this
problem.
Thank you

(mednyk@hotmail.com) writes:
> T-SQL Debugger Doesn't Allow Stepping Through Stored Procedures
> And there is no other procedure with the same name owned by dbo or any
> other users.
> There is no error messages also, it just completes procedure and
> returns result
> server:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build
> 2195: Service Pack 4) and I don't know how do determine Client's
> version.

You can determine the client version from Help->About in Query Analyzer.

I believe that SP2 or earlier of Query Analyzer does not work with
SQL Server SP3. SP3 is 8.00.760. 8.00.818 is a hotfix to SP3 with a
security fix. 818 should work with 760 on the client.

Unless you have the server on the local machine, it is difficult to get
the debugger to work. There are so many things that have to be aligned.
Personally I have given up.

If you are running Windows XP SP2 on the client, you should upgrade to
SQL 2000 SP4, particularly if you are using the XP firewall. But it
does not sound like that - in that case you get an error message.

I believe that the problem when single-step does not work is that
SQL Server does not have privilege to write to your machine from
some port. This is usually due to that SQL Server runs under local
system, or it runs under a domain account with insuffcient privileges.
These days, DBAs perfer to run SQL Server under an account with a
small set or permissions to decrease the surface area in case of an
intrusion.

In Books Online, you can look under Troubleshooting->SQL Server Tools
Troubleshooting -> Troubleshooting the Transact-SQL Debugger and see if
you find any useful tips.

I've found that debuggin with PRINT and SELECT takes me a long way.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Thank you for your reply. The client version :8.00.194
You where saying that my local account is missing some privileges.
Which ones are missing? It's important for me to use debugger, so I am
desperate to get it to work.
Thank you for all your help.
Inna

(mednyk@hotmail.com) writes:
> Thank you for your reply. The client version :8.00.194

That's the RTM version of Query Analyzer. Install SP3 of SQL 2000 on
your machine.

> You where saying that my local account is missing some privileges.
> Which ones are missing? It's important for me to use debugger, so I am
> desperate to get it to work.

No, I said that the service account for SQL Server might be missing some
privs. But we don't know that yet. First roadblock is the incorrect
version of QA on your machine. It may not be the last.

By the way, what cliet OS do you have?


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Hello ,
Sorry for delay, had to get the install of SP3 match the server.
As you asked , I have Windows 2000 5.00.2195 Service Pack 4.
I installed SP3 of SQL 2000 on my machine.
I tried to debug now, and I got new error:
ODBC: Msg 0, Level 19, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
Process 107 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
It's even worst then before, because error is too general and can mean
anything.
I hope you can help me.
Thank you very much
Inna

Hello ,
Sorry for delay, had to get the install of SP3 match the server.
As you asked , I have Windows 2000 5.00.2195 Service Pack 4.
I installed SP3 of SQL 2000 on my machine.
I tried to debug now, and I got new error:
ODBC: Msg 0, Level 19, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
Process 107 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
It's even worst then before, because error is too general and can mean
anything.
I hope you can help me.
Thank you very much
Inna

Hello ,
Sorry for delay, had to get the install of SP3 match the server.
As you asked , I have Windows 2000 5.00.2195 Service Pack 4.
I installed SP3 of SQL 2000 on my machine.
I tried to debug now, and I got new error:
ODBC: Msg 0, Level 19, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
Process 107 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
It's even worst then before, because error is too general and can mean
anything.
I hope you can help me.
Thank you very much
Inna

Hello ,
Sorry for delay, had to get the install of SP3 match the server.
As you asked , I have Windows 2000 5.00.2195 Service Pack 4.
I installed SP3 of SQL 2000 on my machine.
I tried to debug now, and I got new error:
ODBC: Msg 0, Level 19, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
Process 107 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
It's even worst then before, because error is too general and can mean
anything.
I hope you can help me.
Thank you very much
Inna

Hello ,
Sorry for delay, had to get the install of SP3 match the server.
As you asked , I have Windows 2000 5.00.2195 Service Pack 4.
I installed SP3 of SQL 2000 on my machine.
I tried to debug now, and I got new error:
ODBC: Msg 0, Level 19, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:

Process 107 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
It's even worst then before, because error is too general and can mean
anything.
I hope you can help me.
Thank you very much
Inna
P.S. I have no idea what is happening with this post, it doesn't
confirm, that it was saved.
I am sorry if it will show several times, or maybe not.

(mednyk@hotmail.com) writes:
> Hello ,
> Sorry for delay, had to get the install of SP3 match the server.
> As you asked , I have Windows 2000 5.00.2195 Service Pack 4.
> I installed SP3 of SQL 2000 on my machine.
> I tried to debug now, and I got new error:
> ODBC: Msg 0, Level 19, State 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
> Process 107 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> It's even worst then before, because error is too general and can mean
> anything.
> I hope you can help me.
> Thank you very much

There are probably more the one possible reason, but in a rush I found
this KB article: http://support.microsoft.com/default.aspx/kb/270061,
which says that you get this error if @@servername is NULL. The article
describes how to fix this condition.



--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx