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:
Showing posts with label ide. Show all posts
Showing posts with label ide. Show all posts
Sunday, February 19, 2012
Friday, February 17, 2012
Debug Stored Procedure - Visual Studio 2003 - Possible?
I can not step into stored procedures that I have created using the VS IDE.
This is the error message that I receive when attempting to debug the stored
procedure:
"Cannot debug stored procedures because the SQL Sserver database is not
setup correctly or user does not have permission to execute
master.sp_sdidebug. Run SQL Server setup or contact database admininstrator."
I am the database administrator! I have sp_sdidebug set to legacy_on. Not
sure what else to try. My boss does not want to pay for SQL Server Dev
edition, so I would really like to get this working.
Any suggestions will be greatly appreciated.
Thank you,
Michael Garcia
If your boss doesn't want to shell out $49 for the Developer Edition,
perhaps you could helpfully point out that many experienced people
have spent countless hours attempting to get debugging working from
the VS IDE, and have failed to do so. To obtain actual evidence, do a
google groups search on the topic and read threads from other
frustrated users. Ask him to consider how much he is paying you by the
hour, counting benefits, and then ask him to do the math. Caveat --
you can't use the Developer edition as a production server, but it's
indispensable if you care anything about creating a secure and robust
database app.
--Mary
On Tue, 19 Oct 2004 09:19:03 -0700, "Mike"
<Mike@.discussions.microsoft.com> wrote:
>I can not step into stored procedures that I have created using the VS IDE.
>This is the error message that I receive when attempting to debug the stored
>procedure:
>"Cannot debug stored procedures because the SQL Sserver database is not
>setup correctly or user does not have permission to execute
>master.sp_sdidebug. Run SQL Server setup or contact database admininstrator."
>I am the database administrator! I have sp_sdidebug set to legacy_on. Not
>sure what else to try. My boss does not want to pay for SQL Server Dev
>edition, so I would really like to get this working.
>Any suggestions will be greatly appreciated.
>Thank you,
>Michael Garcia
|||Your point is noted; however, I got it working yesterday.
For all those that are having problems getting debugging working in VS for
MSDE try this!
First find the file mssdi98.dll in C:\Program Files\Microsoft Visual Studio
..NET 2003\sqlserver
Copy it to the binn directory of your MSDE instance.
Second run dcomcnfg.
Component Services -> Computers -> My Computer
Select properties for My Computer. Go to the Default COM Security tab.
Edit the default settings for access permissions. Add yourself and system
if it is not there and make sure allow is checked.
This got it working on both my systems.
Good luck!
Michael Garcia
"Mary Chipman" wrote:
> If your boss doesn't want to shell out $49 for the Developer Edition,
> perhaps you could helpfully point out that many experienced people
> have spent countless hours attempting to get debugging working from
> the VS IDE, and have failed to do so. To obtain actual evidence, do a
> google groups search on the topic and read threads from other
> frustrated users. Ask him to consider how much he is paying you by the
> hour, counting benefits, and then ask him to do the math. Caveat --
> you can't use the Developer edition as a production server, but it's
> indispensable if you care anything about creating a secure and robust
> database app.
> --Mary
|||You're lucky -- others have hit the wall configuring DCOM and dealing
with SP2 issues. Please have your boss get you the Dev edition anyway
-- there are many things you simply cannot do from the VS IDE unless
you want to write a lot of script.
--Mary
On Wed, 20 Oct 2004 09:39:02 -0700, "Mike"
<Mike@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Your point is noted; however, I got it working yesterday.
>For all those that are having problems getting debugging working in VS for
>MSDE try this!
>First find the file mssdi98.dll in C:\Program Files\Microsoft Visual Studio
>.NET 2003\sqlserver
>Copy it to the binn directory of your MSDE instance.
>Second run dcomcnfg.
>Component Services -> Computers -> My Computer
>Select properties for My Computer. Go to the Default COM Security tab.
>Edit the default settings for access permissions. Add yourself and system
>if it is not there and make sure allow is checked.
>This got it working on both my systems.
>Good luck!
>Michael Garcia
>"Mary Chipman" wrote:
This is the error message that I receive when attempting to debug the stored
procedure:
"Cannot debug stored procedures because the SQL Sserver database is not
setup correctly or user does not have permission to execute
master.sp_sdidebug. Run SQL Server setup or contact database admininstrator."
I am the database administrator! I have sp_sdidebug set to legacy_on. Not
sure what else to try. My boss does not want to pay for SQL Server Dev
edition, so I would really like to get this working.
Any suggestions will be greatly appreciated.
Thank you,
Michael Garcia
If your boss doesn't want to shell out $49 for the Developer Edition,
perhaps you could helpfully point out that many experienced people
have spent countless hours attempting to get debugging working from
the VS IDE, and have failed to do so. To obtain actual evidence, do a
google groups search on the topic and read threads from other
frustrated users. Ask him to consider how much he is paying you by the
hour, counting benefits, and then ask him to do the math. Caveat --
you can't use the Developer edition as a production server, but it's
indispensable if you care anything about creating a secure and robust
database app.
--Mary
On Tue, 19 Oct 2004 09:19:03 -0700, "Mike"
<Mike@.discussions.microsoft.com> wrote:
>I can not step into stored procedures that I have created using the VS IDE.
>This is the error message that I receive when attempting to debug the stored
>procedure:
>"Cannot debug stored procedures because the SQL Sserver database is not
>setup correctly or user does not have permission to execute
>master.sp_sdidebug. Run SQL Server setup or contact database admininstrator."
>I am the database administrator! I have sp_sdidebug set to legacy_on. Not
>sure what else to try. My boss does not want to pay for SQL Server Dev
>edition, so I would really like to get this working.
>Any suggestions will be greatly appreciated.
>Thank you,
>Michael Garcia
|||Your point is noted; however, I got it working yesterday.
For all those that are having problems getting debugging working in VS for
MSDE try this!
First find the file mssdi98.dll in C:\Program Files\Microsoft Visual Studio
..NET 2003\sqlserver
Copy it to the binn directory of your MSDE instance.
Second run dcomcnfg.
Component Services -> Computers -> My Computer
Select properties for My Computer. Go to the Default COM Security tab.
Edit the default settings for access permissions. Add yourself and system
if it is not there and make sure allow is checked.
This got it working on both my systems.
Good luck!
Michael Garcia
"Mary Chipman" wrote:
> If your boss doesn't want to shell out $49 for the Developer Edition,
> perhaps you could helpfully point out that many experienced people
> have spent countless hours attempting to get debugging working from
> the VS IDE, and have failed to do so. To obtain actual evidence, do a
> google groups search on the topic and read threads from other
> frustrated users. Ask him to consider how much he is paying you by the
> hour, counting benefits, and then ask him to do the math. Caveat --
> you can't use the Developer edition as a production server, but it's
> indispensable if you care anything about creating a secure and robust
> database app.
> --Mary
|||You're lucky -- others have hit the wall configuring DCOM and dealing
with SP2 issues. Please have your boss get you the Dev edition anyway
-- there are many things you simply cannot do from the VS IDE unless
you want to write a lot of script.
--Mary
On Wed, 20 Oct 2004 09:39:02 -0700, "Mike"
<Mike@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Your point is noted; however, I got it working yesterday.
>For all those that are having problems getting debugging working in VS for
>MSDE try this!
>First find the file mssdi98.dll in C:\Program Files\Microsoft Visual Studio
>.NET 2003\sqlserver
>Copy it to the binn directory of your MSDE instance.
>Second run dcomcnfg.
>Component Services -> Computers -> My Computer
>Select properties for My Computer. Go to the Default COM Security tab.
>Edit the default settings for access permissions. Add yourself and system
>if it is not there and make sure allow is checked.
>This got it working on both my systems.
>Good luck!
>Michael Garcia
>"Mary Chipman" wrote:
Subscribe to:
Posts (Atom)