debugger

Hello,
I got the following error message when I was trying to debug a stored
procedure sitting on a remote sql database server. I have no problem
running the debugger on the local server. It just don't work if I try to
debug a stored procedure on a different server. Here is the error message I
got from 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 QAIMGSQL01 (Error = 0x80070005). Ensure that client-side components, such
as SQLDBREG.EXE, are installed and registered on DVO-D1. Debugging disabled
for connection 74.
Any input is highly appreciated.
Thanks,
LianneLianne Kwock (LianneKwock@.discussions.microsoft.com) writes:
> I got the following error message when I was trying to debug a stored
> procedure sitting on a remote sql database server. I have no problem
> running the debugger on the local server. It just don't work if I try
> to debug a stored procedure on a different server. Here is the error
> message I got from 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 QAIMGSQL01 (Error = 0x80070005). Ensure that client-side
> components, such as SQLDBREG.EXE, are installed and registered on
> DVO-D1. Debugging disabled for connection 74.
Which version do you have of the client tools? (Visible under Help->About)
Which version is the remote SQL Server? (SELECT @.@.version)
Are you running Windows XP SP2, and have the firewall enabled?
If you XP SP2 with the firewall, both the client tools and the server
needs to be on Service Pack4 for SQL 2000. Futhermore, you need to
configure the firewall, so that SQL Server can access port 135 (RPC) on
your machine. Click the Windows Firewall applet in the Control Panel,
and go the Exceptions tab and select Add Port. In this dialog, be sure
to use Change Scope to open the port only for the SQL Server machine.
And when you've done all this, you may find that it still does not
work. I had i working at the office for a while when we had gotten
hotfix 8.00.944, a pre-SP4 fix. Then our symin changed something;
I think the priveleges of the service account for SQL Server. I have
since then given up on SQL debugging. It is just too much hassle.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||I too had similar problems, and essentially, like Erland mentioned, gave up
on remote debugging. Debugging can be handy, so when I really need it, I
actually copy the database locally, so I can debug.
Jef
"Lianne Kwock" <LianneKwock@.discussions.microsoft.com> wrote in message
news:2909E993-E2FA-4F4E-863F-39F95A97F987@.microsoft.com...
> Hello,
> I got the following error message when I was trying to debug a stored
> procedure sitting on a remote sql database server. I have no problem
> running the debugger on the local server. It just don't work if I try to
> debug a stored procedure on a different server. Here is the error message
> I
> got from 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 QAIMGSQL01 (Error = 0x80070005). Ensure that client-side components,
> such
> as SQLDBREG.EXE, are installed and registered on DVO-D1. Debugging
> disabled
> for connection 74.
>
> Any input is highly appreciated.
>
> Thanks,
> Lianne
>