February 13, 2003 at 4:48 pm
when we try to debug a stored proc, the debugger comes up and executes but it will not stop at any of the breakpoints. This worked previously but has recently appeared. The only thing we have changed is the install of SP3.
Any ideas on how to fix this?
Thanks
SJ
February 13, 2003 at 5:35 pm
Maybe permissions or a change to sp_idedebug, or whatever it is?
Andy
February 14, 2003 at 9:19 am
I've done some experimenting and noticed that the debugger correctly works if you are on the local machine and debug a sp. However, if you try and debug it from another machine from QAnalyzer it will not stop. We also have a combination of .Net and VS6. The SQL Server and Agent services are started under a domain account and not the Local Service account.
I also checked the sp_sdidedebug extended stored proc and there are only two account listed with permission but neither of them have anything granted (green checkmark). What would be the proper permissions. I have nothing to check against.
Any thoughts?
Thanks
SJ
February 26, 2003 at 4:19 pm
I have the same problem. The Debug used to work, then I installed the SP3 and the .NET framework and it does not work anymore.
Please post here if you find anything.
I will do the same.
Thanks,
Jakub
February 26, 2003 at 4:53 pm
got it:
check out
http://support.microsoft.com/default.aspx?scid=kb;en-us;328173
and
http://support.microsoft.com/default.aspx?scid=kb;en-us;328151
I guess this is a side effect of "Trustworthy Computing"
What is the command to run an SP on server startup, again 🙂
Jakub
February 26, 2003 at 10:14 pm
The second article fixed it for me. I ran SP3 on my local machine that only has the client tools and it works now.
Thanks
SJ
February 27, 2003 at 10:24 am
Be careful with the sp_sdidebug. It seems to have some side effects. Some of my tempdb objects had denied access to them after running this.
Flipping back (legacy_off) does not fix that.
I am still investigating.
Jakub.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply