Debugging in VS.NET

I am attempting to debug a few stored procedures I created using the VS.NET
IDE.
After clicking "Run Stored Procedure" the IDE starts debugging, but almost
immediately throws the following 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. Run
SQL Server setup or contact database administrator."
I found this error in conjunction with a bug in Windows XP SP2. I did have
the service pack installed at one point but uninstalled it earlier this week.
A few of the things I have tried include the following:
Debugging as SA
Setting sp_sdidebug to 'legacy_on"
Disabling my firewall
Changing DCOM settings to look like this (suggested in SQL Books)
DCOMCNFG
|
|__ Application Tab
| |
| |_____ SQLDBREG
| |
| |______ Identity Tab
| |
| |_______ The interactive user
|
|__ Default Security Tab
|
|_____ Default Access Permissions
|
|______ Edit Default Button
|
|_______ Everyone (or domain\account and System)
And, beating my head on the desk.
None of these have worked for me. If anyone has any suggestions they would
be greatly appreciated!
Thanks in advance.
Mike
Any ideas?
|||Come on! You've got to provide more information about your problem then
that.
Debugging what?
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:5635E9E3-8009-4C6D-86DF-AFF2C3067128@.microsoft.com...
> Any ideas?
|||In my post I stated that i was debugging stored procedures that I created in
Visual Studio using the server explorer. What additional information do you
need?
"Jim Young" wrote:

> Come on! You've got to provide more information about your problem then
> that.
> Debugging what?
> "Mike" <Mike@.discussions.microsoft.com> wrote in message
> news:5635E9E3-8009-4C6D-86DF-AFF2C3067128@.microsoft.com...
>
>
|||Sorry, I only saw the short reply you made, not the original post.
All I can say is that I'm able to debug sprocs in VS.Net by stepping into
the stored procedure from the Database menu. I can't find your original
post. What kind of problem are you having again?
Jim
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:9363461F-EE37-44D6-A346-93B2DA35894A@.microsoft.com...
> In my post I stated that i was debugging stored procedures that I created
in
> Visual Studio using the server explorer. What additional information do
you[vbcol=seagreen]
> need?
> "Jim Young" wrote:
|||After clicking "Run Stored Procedure" the IDE starts debugging, but almost
immediately throws the following 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. Run
SQL Server setup or contact database administrator."
If anyone has any ideas I would really appreciate them. If not I'm just
going to have to get the developers edition and pray that it works.
"Jim Young" wrote:

> Sorry, I only saw the short reply you made, not the original post.
> All I can say is that I'm able to debug sprocs in VS.Net by stepping into
> the stored procedure from the Database menu. I can't find your original
> post. What kind of problem are you having again?
> Jim
> "Mike" <Mike@.discussions.microsoft.com> wrote in message
> news:9363461F-EE37-44D6-A346-93B2DA35894A@.microsoft.com...
> in
> you
>
>
|||By any chance did you install XP Service Pack 2 on your machine?
http://support.microsoft.com/?id=839280
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:8BBC54B3-45A7-45C7-AFC7-B051B96203ED@.microsoft.com...
> After clicking "Run Stored Procedure" the IDE starts debugging, but almost
> immediately throws the following 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.
Run[vbcol=seagreen]
> SQL Server setup or contact database administrator."
> If anyone has any ideas I would really appreciate them. If not I'm just
> going to have to get the developers edition and pray that it works.
> "Jim Young" wrote:
into[vbcol=seagreen]
created[vbcol=seagreen]
do[vbcol=seagreen]
then[vbcol=seagreen]
|||I did install SP2, but when I found that KB article you mentioned, I
uninstalled it. Is it possible that whatever it does that messes up
debugging in VS is still hanging around? I made a restore point right before
I installed the service pack, so I can restore to it if absolutely necessary.
That was almost 2 weeks ago, so I would like to avoid this solution if
possible.
Thanks for the reply.
Mike
"Jim Young" wrote:

> By any chance did you install XP Service Pack 2 on your machine?
> http://support.microsoft.com/?id=839280
> "Mike" <Mike@.discussions.microsoft.com> wrote in message
> news:8BBC54B3-45A7-45C7-AFC7-B051B96203ED@.microsoft.com...
> setup
> Run
> into
> created
> do
> then
>
>
|||I had the same problem debugging a SP,(not to mention that I have had not
installed WinXP SP2).
I set permissions to the extended SP on master and it did not work also, but
then I went a little bit further.
Now the message is simply:
" Security hasn't been setup correctly for SQL debugging on server xxxxx.
SQL Debugging terminated. See SQL Debugging documentation on how to set it up
correctly"
Any ideas?
LA
"Mike" wrote:
[vbcol=seagreen]
> I did install SP2, but when I found that KB article you mentioned, I
> uninstalled it. Is it possible that whatever it does that messes up
> debugging in VS is still hanging around? I made a restore point right before
> I installed the service pack, so I can restore to it if absolutely necessary.
> That was almost 2 weeks ago, so I would like to avoid this solution if
> possible.
> Thanks for the reply.
> Mike
> "Jim Young" wrote: