August 25, 2004 at 7:26 am
Folks,
Last week, we have been using the Transact-SQL Debugger just fine on a number of PCs. The PCs are configured with the SQL 2K SP3 client tools and we are connecting to a SQL 2K SP3 server. Debugger was working just fine.
This week, we had XP SP2 installed on our desktops. Now it would appear this has caused the Debugger to break. When we try to debug a SP, this is the error that is returned.
Server: Msg 504, Level 16, State 1, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger on DHSSQLD1 (Error = 0x800706ba). Ensure that client-side components, such as SQLDBREG.EXE, are installed and registered on 210094146DLRC. Debugging disabled for connection 90.
Has anyone noticed this or has an explanation as to why the Debugger all the sudden stopped working on several PCs?
Thanks in advance!
August 26, 2004 at 4:32 am
You might try a google search. I got a few hits on "SQL Debugger Problem windows XP". Lots of different reasons for it.
This one:
http://www.winnetmag.com/Article/ArticleID/42729/42729.html]
might be what you mentioned.
August 26, 2004 at 7:46 am
August 26, 2004 at 7:50 am
Debugger can be frustrating. Keep this command around. It doesn't sound like your problem, but it's helped me out before. Not in BOL, but I'm sure the heads here could shed light.
Exec sp_sdidebug 'legacy on'
September 27, 2004 at 4:15 am
September 27, 2004 at 6:27 am
Thanks for the update Diego. Developers will be happy to hear this.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply