March 6, 2002 at 6:54 pm
I was running the T-debugger successfully in the morning. But I guess I messed up somethings, now whenever I try to run debug, I will get the following error after I fill in all the parameters. Any ideas? Solutions?
Server: Msg 229, Level 14, State 5, Procedure sp_sdidebug, Line 1
EXECUTE permission denied on object 'sp_sdidebug', database 'master', owner 'dbo'.
March 6, 2002 at 7:16 pm
Are you logged in as SA or with admistrator rights, or did you make changes to your login or the procedur itself?
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
March 7, 2002 at 10:05 am
March 7, 2002 at 10:15 am
It is an internal stored procedure. It's what the Transact-SQL Debugger uses in SQL 2K to allow for debugging.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
March 7, 2002 at 10:16 am
Some things I found:
From Neil Pike:
Q. What does sp_sdidebug do?
A. It is used to turn on or off TSQL debugging. There is no user interface for it and no documentation.
----------
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q179023
FIX: T-SQL Debugger Hangs When User Has No Execute Permission (Q179023)
------
Interesting thread here:
http://dbforums.com/archive/72/2001/07/4/111299
----
http://www.sqlsecurity.com/checklist.asp
--
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q303324
Bug sql 2000
Steve Jones
March 21, 2002 at 8:50 am
I'm having a similar problem with the debugger in the SQL Query Analyser of SQL2000 and it's got my network guys and myself stumped.
I can debug successfully on the personal engine on my machine, and from the console of the server, but when I try to debug a stored procedure on the server from my machine, I get:
Server: Msg 514, Level 16, State 1, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to communicate with debugger on SQLSERVER (Error = 0x80070005). Debugging disabled for connection 68.
We have 3 SQL Servers and this happens on each.
My SQL login has full server administrator rights on all of them, and has the same password and login across all machines (including local).
I can administer any part of any server without fault locally and at the server.
I can run the debugger on my local server, or any server direct from it's console as myself of 'sa' with no problems.
However, the error appears whenever I try to debug a stored procedure remotely, whether logged in as myself or 'sa'.
I have run EXEC master..sp_sdidebug from the analyser and that runs.
Doe anyone have any idea what might be going wrong?
---------------------------------------
It is by caffeine alone I set my mind in motion.
It is by the Beans of Java that thoughts acquire speed,
the hands acquire shaking, the shaking becomes a warning.
It is by caffeine alone I set my mind in motion.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply