Remote debugging does not stop

Question

Remote debugging does not stop

Serge Matsevilo

Grasshopper

Points: 12
More actions
October 7, 2005 at 6:47 pm

#169137

Hello,

I am trying to debug a stored procedure on remote server. The debugger starts and passes through without stopping.

No error messages are generated on the client.
On the server the following error appears in the Application Log:

Event Type: Error
Event Source: SQLDebugging98
Event Category: None
Event ID: 1
Date:  10/7/2005
Time:  4:41:47 PM
User:  N/A
Computer: <server>
Description:
SQL Server is running as '<domain account>' and cannot connect to the debugger on machine '<my machine>' (error = 0x80070005 Access is denied. ). Use one of the following options to fix this error. 1) Run SQL Server as "Local System", as a domain account, or as a local account with identical usernames and passwords on both machine '<server>' and '<my machine>'. 2) Verify that machine '<server>' can open files on machine '<my machine>'. Debugging disabled for connection 55.

Server is Windows 2003 Standard running SQL 2000 SP4 with .NET remote debugging support.
Client is Windows XP Pro SP2 running SQL 2000 SP4 and .NET 1.1 SP1.

Windows Firewall is disabled on both machines.
All DCOM permissions seems to be set OK on the server. I am a local admin on the server and sys admin on SQL server and I can run sp_sdidebug without any problems.

I can debug SQL on my local machine using Query Analyzer and VS.NET without any problems. I can also debug SQL using Query Analyzer on the server if I log there with my account.

What could prevent SQL debugger from connecting to my workstation? I tried to add that SQL service account to my local admin group, but it did not help. I am not sure what is required to "2) Verify that machine '<server>' can open files on machine '<my machine>'." Does it mean that I have to trust my server machine? How can I do that?

What else could be wrong?

Viewing 2 posts - 1 through 2 (of 2 total)

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

Serge Matsevilo Grasshopper Points: 12 More actions · Answer 1

After speding another 6 hours troubleshooting my local COM+ security I found the settings that make remote SQL debugging work for SQL Analyzer and VS.NET.

All these settings alpply to Default COM Security for Windows XP.

Access Permissions:

Limits:

ANONYMOUS LOGON - Allow All (Required to debug from SQL Analyzer)
Everyone - Allow All (Required to debug from VS.NET)

Launch and Activation Permissions:

Limits (add)

ANONYMOUS LOGON - Allow All (Required to debug from VS.NET)

Default (add)

ANONYMOUS LOGON - Allow All (Required to debug from VS.NET)