By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,266 Members | 1,312 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,266 IT Pros & Developers. It's quick & easy.

Query Analyzer. Error : Unable to connect to debugger

P: n/a
MS SQL Server 2000 SP3
Windows XP SP2

Error when try to debug in Query Analyzer:
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 HORNET (Error = 0x80070005). Ensure that client-side
components, such as SQLDBREG.EXE, are installed and registered on
EUGENE. Debugging disabled for connection 63.

Tried:
- 'Troubleshooting the Transact-SQL Debugger' ( Book on-line )
- EXEC ... 'legacy_on'
- firewall is disabled

What else can be done ?

Thanks , Eugene
Jul 23 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Eugene (yg********@hotmail.com) writes:
MS SQL Server 2000 SP3
Windows XP SP2

Error when try to debug in Query Analyzer:
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 HORNET (Error = 0x80070005). Ensure that client-side
components, such as SQLDBREG.EXE, are installed and registered on
EUGENE. Debugging disabled for connection 63.

Tried:
- 'Troubleshooting the Transact-SQL Debugger' ( Book on-line )
- EXEC ... 'legacy_on'
- firewall is disabled


You need hotfix 944, as per http://support.microsoft.com/kb/839280. You
would need to open a case with Microsoft to get the hotfix.

Once you have the hotfix, there are a few more things to handle:

o You must apply hotfix 944 both on the server you wish to debug and the
client you wish do debug from.
o On the client you must open port 135 in Windows firewall. Beware that
port 135 is not good port to open for general access. Use Change Scope
to restrict the port only to be open for the servers you need to debug.
o The old issues still remain, that is SQL Server must be running on a
domain user and all that.

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
Jul 23 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.