> I am connecting to a SQL 2k Server SP3 on a different machine on the
> network using SQL Query Analyzer 8.00.760.  I do not have SQL Server
> installed on my machine, only the Query Analyzer.  When I try to debug a
> stored procedure I 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 CLAM (Error = 0x80070005). Ensure that client-side components, such as
> SQLDBREG.EXE, are installed and registered on SLANGDANG. Debugging
> disabled for connection 60.
>
> I've tried both
> Exec sp_sdidebug 'legacy_off'
> and
> Exec sp_sdidebug 'legacy_on'
> and the same message is given.
>
> Any ideas why this is not working?

"Erland Sommarskog" <esq***@sommarskog.se> wrote in message
news:Xns975CF31FB66D7Yazorman@127.0.0.1...
> Microsoft (die_spambot@hatespam.com) writes:
>> I am connecting to a SQL 2k Server SP3 on a different machine on the
>> network using SQL Query Analyzer 8.00.760.  I do not have SQL Server
>> installed on my machine, only the Query Analyzer.  When I try to debug a
>> stored procedure I 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 CLAM (Error = 0x80070005). Ensure that client-side components, such as
>> SQLDBREG.EXE, are installed and registered on SLANGDANG. Debugging
>> disabled for connection 60.
>>
>> I've tried both
>> Exec sp_sdidebug 'legacy_off'
>> and
>> Exec sp_sdidebug 'legacy_on'
>> and the same message is given.
>>
>> Any ideas why this is not working?
>
> Generally, I have given on remote debugging. There is so many things
> that has to be aligned for it to work.
>
> What OS do you have? If you have Windows XP SP2, you need to install SP4
> both on SQL Server and on the workstation. If you run with Windows
> firewall,
> then you also need to open port 135, which you should do only for
> the SQL Server machine. (This is possible in the Add Port dialog for
> the firewall.) Port 135 is RPC, and you don't want it to be open for
> anyone.
>
> There may be more issues that this that you need to address for it to
> work.
>
> Debug SELECTs and PRINTs may take you to your goal much faster.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

"Microsoft" <die_spambot@hatespam.com> wrote in message
news:uB0du22JGHA.2828@TK2MSFTNGP12.phx.gbl...
>I have the firewall off but there is a lot of "red tape" to getting the
>server upgraded from SQL SP3 to SQL SP4: its almost impossible.  If it
>happens this year I will let you know how it all turned out.
>
> Thanks
>
>
> "Erland Sommarskog" <esq***@sommarskog.se> wrote in message
> news:Xns975CF31FB66D7Yazorman@127.0.0.1...
>> Microsoft (die_spambot@hatespam.com) writes:
>>> I am connecting to a SQL 2k Server SP3 on a different machine on the
>>> network using SQL Query Analyzer 8.00.760.  I do not have SQL Server
>>> installed on my machine, only the Query Analyzer.  When I try to debug a
>>> stored procedure I 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 CLAM (Error = 0x80070005). Ensure that client-side components, such
>>> as
>>> SQLDBREG.EXE, are installed and registered on SLANGDANG. Debugging
>>> disabled for connection 60.
>>>
>>> I've tried both
>>> Exec sp_sdidebug 'legacy_off'
>>> and
>>> Exec sp_sdidebug 'legacy_on'
>>> and the same message is given.
>>>
>>> Any ideas why this is not working?
>>
>> Generally, I have given on remote debugging. There is so many things
>> that has to be aligned for it to work.
>>
>> What OS do you have? If you have Windows XP SP2, you need to install SP4
>> both on SQL Server and on the workstation. If you run with Windows
>> firewall,
>> then you also need to open port 135, which you should do only for
>> the SQL Server machine. (This is possible in the Add Port dialog for
>> the firewall.) Port 135 is RPC, and you don't want it to be open for
>> anyone.
>>
>> There may be more issues that this that you need to address for it to
>> work.
>>
>> Debug SELECTs and PRINTs may take you to your goal much faster.
>>
>>
>> --
>> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>>
>> Books Online for SQL Server 2005 at
>> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
>> Books Online for SQL Server 2000 at
>> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>
>