Msg 504 - Unable to connect to debugger. Ensure that client-side components, such as SQLDBREG.EXE, are installed and registered...

Question

Post reply

Msg 504 - Unable to connect to debugger. Ensure that client-side components, such as SQLDBREG.EXE, are installed and registered...

Dennis Shiver

SSC Enthusiast

Points: 198
More actions
May 25, 2006 at 6:17 am

#113138

We have 3 SQL 2000 servers. All are the same version. On two of them the debugger works fine. On one, when we try to use the debugger to debug a stoperd procedure, we get:
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 ITDEPTDEV2 (Error = 0x80040154). Ensure that client-side components, such as SQLDBREG.EXE, are installed and registered on ITDEPTDEV2. Debugging disabled for connection 65.
I have searched the Microsoft topics.
The one thing that is different here is that this box had SQL Server installed on it, then deleted, then reinstalled. It was the same version, SQL Server 2000. I am not sure if that is what is causing this issue or not.
I tried uninstalling the debugger, then installing all client side developer's tools, that didn't help.
I have already reviewed:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;328151

I had already tried the legacy switch, just in case, but since the only versions of SQL ever installed have been 2000 w/SP3a, I didn't think that the legacy issue applied.
http://support.microsoft.com/default.aspx?scid=KB;EN-US;318632
I'm a domain admin and I use the same login to each server, and it works on 2 of them but not the 3rd, so this article doesn't apply.
http://support.microsoft.com/kb/839280
The servers are all Server 2003, so this article doesn't apply. I get the error on the one box whether I try it from my workstation or directly on the server.
ANy suggestions will be most appreciated, thanks!

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Kid-266422 SSC Veteran Points: 261 More actions · Answer 1

This article helped in my case...

http://msdn2.microsoft.com/en-us/library/tfyahe0f(VS.80).aspx

Dennis Shiver SSC Enthusiast Points: 198 More actions · Answer 2

Thanks, I took a look at the article, but didn't seem to apply. There is no user "SQLDebugger" on the server. I tried adding rights for that user but it wouldn't take, the user doesn't exist.