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
> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>