Groups | Blog | Home
all groups > sql server programming > september 2004 >

sql server programming : SQLDebugger in a Workgroup Environment


David Pendleton
9/15/2004 9:40:58 PM

Hello all.

I have several machines participating in a small Workgroup. These are all
Win2K/Win2KAS/XP/SQL Server 2000. A domain is overkill for my home office.

I have successfully debugged a stored procedure on the server. However, when
I attempt the same on a workstation, I am not able to step through code,
etc. The Application log on the server indicates that the SQLDebugger could
not communicate with the debugger on whatever workstation I happen to be
using.

I have configured the SQL Debugger via DCOMCNFG per MSDN/Books Online to
allow 'Everyone' access to the SQL Debugger, and to log in as the
interactive user, all to no avail.

Does anyone have this working? Any ideas?

Thanks.
--
ROT-13 my email address to reply directly

Gert E.R. Drapers
9/16/2004 11:37:00 AM
Do you have a firewall active? If so you need to enable RPC communication to
go over your firewall.
Otherwise try establishing a IPC session first from the client to the server
like:

net use \\sqlserver\ipc$ /u:sqlserver\adminonsqlserver *

GertD@SQLDev.Net

Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2004 All rights reserved.

[quoted text, click to view]

David Pendleton
9/16/2004 7:17:28 PM
No, no firewall.

No luck with the ipc$ approach either. Error text is as follows:

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 PROLIANT-3000 (Error = 0x800706ba). Ensure that client-side components,
such as SQLDBREG.EXE, are installed and registered on COMPAQ-SP750.
Debugging disabled for connection 56.

Thanks again.


[quoted text, click to view]

AddThis Social Bookmark Button