Remote SQL Debug: Server cannot connect to the debugger on my mach

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 ope
n
files on machine '<my machine>'." Does it mean that I have to trust my serve
r
machine? How can I do that?
What else could be wrong?Hello Serge,
You wrote in conference microsoft.public.sqlserver.programming on Fri, 7
Oct 2005 17:25:03 -0700:
SM> I am trying to debug a stored procedure on remote server. The debugger
SM> starts and passes through without stopping.
http://support.microsoft.com/defaul...kb;en-us;841249
and especially
http://support.microsoft.com/defaul...kb;en-us;839280
Vadm Rapp|||After spending few hours troubleshooting my local COM+ security and killing
my registry :) I found the settings that make remote SQL debugging work for
SQL Analyzer and VS.NET.
All these settings apply to the Default COM Security for Windows XP
Workstation from which debugging is initiated.
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)
Huh!
Of course all settings on the server must be done first as described in
several knowlege articles. If firewall is anabled, then it should be adresse
d
as well.
"Serge Matsevilo" wrote:

> 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 a
ny
> problems.
> I can debug SQL on my local machine using Query Analyzer and VS.NET withou
t
> 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 he
lp.
> I am not sure what is required to "2) Verify that machine '<server>' can o
pen
> files on machine '<my machine>'." Does it mean that I have to trust my ser
ver
> machine? How can I do that?
> What else could be wrong?

Remote SP debugging from VS 2003: error

I 'm still getting the error:
"Cannot debug stored procedures because the SQL Server database is not setup
correctly or user does not have permission to execute master.sp_sdidebug."
I have configured DCOM on the remote sql server according tothe MSDN
article.
I have added SQLDebugger account to default permissions in dcom.
I have also given full access to Master DB for the user
SQLDebugger and all stored procedures full access.
Does anybody have any idea why is it still giving the above error.
TIA
TSHi
Did you check out
http://support.microsoft.com/default.aspx?scid=kb;en-us;817178
John
"test" wrote:
> I 'm still getting the error:
> "Cannot debug stored procedures because the SQL Server database is not setup
> correctly or user does not have permission to execute master.sp_sdidebug."
> I have configured DCOM on the remote sql server according tothe MSDN
> article.
> I have added SQLDebugger account to default permissions in dcom.
> I have also given full access to Master DB for the user
> SQLDebugger and all stored procedures full access.
> Does anybody have any idea why is it still giving the above error.
> TIA
> TS
>
>|||Hi John,
Thanks for the reply.
According to the support article
I ran EXECUTE sp_sdidebug 'LEGACY_ON'
on the remote DB server on QA.
I am afraid it still gives me the same error.
In the system log file and the Application log file of the remote server
following errors were recorded respectively.
DCOM was unable to communicate with the computer WS06 using any of the
configured protocols.
Error: 504, Severity: 16, State: 1
Unable to connect to debugger on MELB (Error = 0x800706ba). Ensure that
client-side components, such as SQLDBREG.EXE, are installed and registered
on WS06. Debugging disabled for connection 58.
JFI: SQLDBREG.EXE is found on client machine and executed too.
thanks
TS
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8A208FDB-FBC4-43C0-A94F-BC2792FCE9EB@.microsoft.com...
> Hi
> Did you check out
> http://support.microsoft.com/default.aspx?scid=kb;en-us;817178
> John
> "test" wrote:
>> I 'm still getting the error:
>> "Cannot debug stored procedures because the SQL Server database is not
>> setup
>> correctly or user does not have permission to execute
>> master.sp_sdidebug."
>> I have configured DCOM on the remote sql server according tothe MSDN
>> article.
>> I have added SQLDebugger account to default permissions in dcom.
>> I have also given full access to Master DB for the user
>> SQLDebugger and all stored procedures full access.
>> Does anybody have any idea why is it still giving the above error.
>> TIA
>> TS
>>
>>|||Hi
This looks like:
http://support.microsoft.com/default.aspx?scid=kb;en-us;839280
Failing that you may want to check RPC is running
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_servtools_5cfm.asp
and if you can use Query Analyser for debugging from this machine and others
as well as on the server.
John
"test" wrote:
> Hi John,
> Thanks for the reply.
> According to the support article
> I ran EXECUTE sp_sdidebug 'LEGACY_ON'
> on the remote DB server on QA.
> I am afraid it still gives me the same error.
>
> In the system log file and the Application log file of the remote server
> following errors were recorded respectively.
> DCOM was unable to communicate with the computer WS06 using any of the
> configured protocols.
> Error: 504, Severity: 16, State: 1
> Unable to connect to debugger on MELB (Error = 0x800706ba). Ensure that
> client-side components, such as SQLDBREG.EXE, are installed and registered
> on WS06. Debugging disabled for connection 58.
> JFI: SQLDBREG.EXE is found on client machine and executed too.
>
> thanks
> TS
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:8A208FDB-FBC4-43C0-A94F-BC2792FCE9EB@.microsoft.com...
> > Hi
> >
> > Did you check out
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;817178
> >
> > John
> >
> > "test" wrote:
> >
> >> I 'm still getting the error:
> >>
> >> "Cannot debug stored procedures because the SQL Server database is not
> >> setup
> >> correctly or user does not have permission to execute
> >> master.sp_sdidebug."
> >>
> >> I have configured DCOM on the remote sql server according tothe MSDN
> >> article.
> >> I have added SQLDebugger account to default permissions in dcom.
> >>
> >> I have also given full access to Master DB for the user
> >> SQLDebugger and all stored procedures full access.
> >>
> >> Does anybody have any idea why is it still giving the above error.
> >>
> >> TIA
> >> TS
> >>
> >>
> >>
> >>
>
>|||John,
By any chance can the problem that I am getting is due to the fact that we
are on two different domains, i.e. sql server and my working machine?
thanks
TS
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:58CD11E4-5320-4107-9384-15ECECC78C3D@.microsoft.com...
> Hi
> This looks like:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;839280
> Failing that you may want to check RPC is running
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_servtools_5cfm.asp
> and if you can use Query Analyser for debugging from this machine and
> others
> as well as on the server.
> John
> "test" wrote:
>> Hi John,
>> Thanks for the reply.
>> According to the support article
>> I ran EXECUTE sp_sdidebug 'LEGACY_ON'
>> on the remote DB server on QA.
>> I am afraid it still gives me the same error.
>>
>> In the system log file and the Application log file of the remote server
>> following errors were recorded respectively.
>> DCOM was unable to communicate with the computer WS06 using any of the
>> configured protocols.
>> Error: 504, Severity: 16, State: 1
>> Unable to connect to debugger on MELB (Error = 0x800706ba). Ensure that
>> client-side components, such as SQLDBREG.EXE, are installed and
>> registered
>> on WS06. Debugging disabled for connection 58.
>> JFI: SQLDBREG.EXE is found on client machine and executed too.
>>
>> thanks
>> TS
>>
>> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
>> news:8A208FDB-FBC4-43C0-A94F-BC2792FCE9EB@.microsoft.com...
>> > Hi
>> >
>> > Did you check out
>> >
>> > http://support.microsoft.com/default.aspx?scid=kb;en-us;817178
>> >
>> > John
>> >
>> > "test" wrote:
>> >
>> >> I 'm still getting the error:
>> >>
>> >> "Cannot debug stored procedures because the SQL Server database is not
>> >> setup
>> >> correctly or user does not have permission to execute
>> >> master.sp_sdidebug."
>> >>
>> >> I have configured DCOM on the remote sql server according tothe MSDN
>> >> article.
>> >> I have added SQLDebugger account to default permissions in dcom.
>> >>
>> >> I have also given full access to Master DB for the user
>> >> SQLDebugger and all stored procedures full access.
>> >>
>> >> Does anybody have any idea why is it still giving the above error.
>> >>
>> >> TIA
>> >> TS
>> >>
>> >>
>> >>
>> >>
>>|||Hi
I don't think that should be a problem expecially if you have a trusted
relationship between the two domains (which I assume you have!). The second
article points to a post SP3a hotfix. As you don't give you version numbe I
assume that you are still on SP3a, so you could try loading service pack 4 on
both client and server.
Did you try debugging from Query Analyser?
John
"test" wrote:
> John,
> By any chance can the problem that I am getting is due to the fact that we
> are on two different domains, i.e. sql server and my working machine?
> thanks
> TS
>
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:58CD11E4-5320-4107-9384-15ECECC78C3D@.microsoft.com...
> > Hi
> >
> > This looks like:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;839280
> >
> > Failing that you may want to check RPC is running
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_servtools_5cfm.asp
> >
> > and if you can use Query Analyser for debugging from this machine and
> > others
> > as well as on the server.
> >
> > John
> >
> > "test" wrote:
> >
> >> Hi John,
> >>
> >> Thanks for the reply.
> >>
> >> According to the support article
> >> I ran EXECUTE sp_sdidebug 'LEGACY_ON'
> >> on the remote DB server on QA.
> >> I am afraid it still gives me the same error.
> >>
> >>
> >> In the system log file and the Application log file of the remote server
> >> following errors were recorded respectively.
> >>
> >> DCOM was unable to communicate with the computer WS06 using any of the
> >> configured protocols.
> >>
> >> Error: 504, Severity: 16, State: 1
> >> Unable to connect to debugger on MELB (Error = 0x800706ba). Ensure that
> >> client-side components, such as SQLDBREG.EXE, are installed and
> >> registered
> >> on WS06. Debugging disabled for connection 58.
> >>
> >> JFI: SQLDBREG.EXE is found on client machine and executed too.
> >>
> >>
> >> thanks
> >> TS
> >>
> >>
> >> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> >> news:8A208FDB-FBC4-43C0-A94F-BC2792FCE9EB@.microsoft.com...
> >> > Hi
> >> >
> >> > Did you check out
> >> >
> >> > http://support.microsoft.com/default.aspx?scid=kb;en-us;817178
> >> >
> >> > John
> >> >
> >> > "test" wrote:
> >> >
> >> >> I 'm still getting the error:
> >> >>
> >> >> "Cannot debug stored procedures because the SQL Server database is not
> >> >> setup
> >> >> correctly or user does not have permission to execute
> >> >> master.sp_sdidebug."
> >> >>
> >> >> I have configured DCOM on the remote sql server according tothe MSDN
> >> >> article.
> >> >> I have added SQLDebugger account to default permissions in dcom.
> >> >>
> >> >> I have also given full access to Master DB for the user
> >> >> SQLDebugger and all stored procedures full access.
> >> >>
> >> >> Does anybody have any idea why is it still giving the above error.
> >> >>
> >> >> TIA
> >> >> TS
> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>

remote debug problem

I am trying to do remote debugging and doesn't seem to be working....I brin
g up query analyzer, select the datbase, select the sp, right click debug, e
nter a value and ok...when I do this it doesn't pass/break...it completes
the query and grays out the
buttons at the top....
steps I have done:got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right
click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permiss
ion
b. under applications tab - I went to properties ont he sqldbreg edited the
use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local us
er I setup with admin rights
what else can I try?|||got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right
click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permiss
ion
b. under applications tab - I went to properties ont he sqldbreg edited the
use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local us
er I setup with admin rights
what else can I try?|||got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right
click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permiss
ion
b. under applications tab - I went to properties ont he sqldbreg edited the
use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local us
er I setup with admin rights
what else can I try?|||Make sure the version of client tools is the same as the server. In Query
Analyzer look in Help/About.
That fixed the problem for me.
"Jamie Elliott" wrote:

> got click happy
> things I have tried...
> 1. i put in a local admin account under properties/security after you righ
t click on the sql instance
> 2. run dcomcnfg
> a. edited the default access permission - gave everyone allow acces
s permission
> b. under applications tab - I went to properties ont he sqldbreg ed
ited the use custom access permission under security to allow everyone permi
ssion
> c. on that same com(sqldbreg) - I changed the identity to use a the
local user I setup with admin rights
> what else can I try?

remote debug problem

I am trying to do remote debugging and doesn't seem to be working....I bring up query analyzer, select the datbase, select the sp, right click debug, enter a value and ok...when I do this it doesn't pass/break...it completes the query and grays out the
buttons at the top....
steps I have done:
got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permission
b. under applications tab - I went to properties ont he sqldbreg edited the use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local user I setup with admin rights
what else can I try?
|||got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permission
b. under applications tab - I went to properties ont he sqldbreg edited the use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local user I setup with admin rights
what else can I try?
|||got click happy
things I have tried...
1. i put in a local admin account under properties/security after you right click on the sql instance
2. run dcomcnfg
a. edited the default access permission - gave everyone allow access permission
b. under applications tab - I went to properties ont he sqldbreg edited the use custom access permission under security to allow everyone permission
c. on that same com(sqldbreg) - I changed the identity to use a the local user I setup with admin rights
what else can I try?
|||Make sure the version of client tools is the same as the server. In Query
Analyzer look in Help/About.
That fixed the problem for me.
"Jamie Elliott" wrote:

> got click happy
> things I have tried...
> 1. i put in a local admin account under properties/security after you right click on the sql instance
> 2. run dcomcnfg
> a. edited the default access permission - gave everyone allow access permission
> b. under applications tab - I went to properties ont he sqldbreg edited the use custom access permission under security to allow everyone permission
> c. on that same com(sqldbreg) - I changed the identity to use a the local user I setup with admin rights
> what else can I try?