Cannot Debug Stored Procs from VS.NET

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Alex Clark (alex_at_theclarkhome.SPAMTIN.net)
Date: 11/18/04 

Date: Thu, 18 Nov 2004 14:53:23 -0000

Hi All,

After installing a hotfix for SQL Server on my Win2K3 Server, I've been
unable to debug any stored procedures running on it from my XP Pro machine
running VS.NET 2003 EA.

To clarify, I can step into Stored Procedures from my workstation on a
database running on the server. However, if I set a breakpoint in the SP
and run my VB.NET App, it never hits the breakpoint.

I've done a repair of VS.NET on my XP workstation, and run a
remote-debugging-components install of VS.NET on my server, but to no avail.
I've ensured that SQL Debugging is enabled for my project, and I've called
EXEC SP_SDIDEBUG 'legacy_on' after each time I've restarted to SQL service,
but this hasn't helped.

I've also tried giving Domain Users and Everyone full access to the sqldbreg
DCOM component on both machines, running SQL Server as a Domain Admin
account instead of LocalSystem, and restarting the service. It simply will
not hit breakpoints in my stored procs.

After checking the event log on the server, I found this each time a
connection is opened from my VB.NET app:

>>
SQL Server is running as 'NT AUTHORITY\SYSTEM' and cannot connect to the
debugger on machine 'DEFIANT' (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 'HONSERVER' and 'DEFIANT'. 2) Verify that
machine 'HONSERVER' can open files on machine 'DEFIANT'. Debugging disabled
for connection 51.
>>

Can anyone offer any advice on this? I'm at my wits end!

TIA,
Alex Clark

Relevant Pages

  • Re: MSDE Service permissions
    ... remove it from the users group and use it for the service ... LocalSystem account, created just for this purpose and never use an actual ... You can create this account before you begin installing SQL ... or you can change the account under which SQL Server runs at a later ...
    (microsoft.public.sqlserver.msde)
  • Re: Change SQL Service Account
    ... I finally downloaded from Microsoft the eval version of SQL Server ... When installing it I only installed the client tools which installed ... I used EM to change the Service Account to my new ... I can't find Configuration Manager for SQL 2000 MSDE. ...
    (microsoft.public.sqlserver.setup)
  • Extreme performance issues (SQL Server 2000/ADO.NET/C#)
    ... This process runs very quickly if run through Query ... same exact stored procedures and views, run in the same exact order, through ... system that runs SQL Server (a 4-cpu Xeons system with 2gigs of physical ... When I execute these steps manually through query analyser,, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Securing Stored Procedures from being seen
    ... username, but in SQL Server, there are too many users to map an individuals ... granting the group execute permissions. ... but I would have to know what groups the user belongs ... see the names of any stored procedures to which he has no rights. ...
    (microsoft.public.sqlserver.security)
  • Re: Querying on dates in dd/mm/yyyy hh/mm/ss format using Access2002 And SQL Server 7
    ... For parsing a string to a date/time, the 103 format doesn't limits the user ... > which is used as the row source for the results form). ... > other solutions assuming I have to use SQL Server 7? ... > I don't understand how I can use parameterized stored procedures to solve ...
    (microsoft.public.access.adp.sqlserver)