I am learning the debugger using IBuySpy. I make small changes to the code and use the debugger to see the effects of my changes. WindowsXP crashed and now when I try to debug IBuySpy, I get the following errors while the programs is starting, and these errors have nothing to do with the areas I have changed. IBuySpy wirks flawslessly if I run it without debugging. I would appear that the problem lies in the debugger itself. Can anyone help?
"Bill Thames" <b...@eritter.net> wrote in message news:uZ1za2KbDHA.424@TK2MSFTNGP10.phx.gbl... > I am learning the debugger using IBuySpy. I make small changes to the code > and use the debugger to see the effects of my changes. WindowsXP crashed and > now when I try to debug IBuySpy, I get the following errors while the > programs is starting, and these errors have nothing to do with the areas I > have changed. IBuySpy wirks flawslessly if I run it without debugging. I > would appear that the problem lies in the debugger itself. Can anyone help?
> I am learning the debugger using IBuySpy. I make small changes to the code > and use the debugger to see the effects of my changes. WindowsXP crashed and > now when I try to debug IBuySpy, I get the following errors while the > programs is starting, and these errors have nothing to do with the areas I > have changed. IBuySpy wirks flawslessly if I run it without debugging. I > would appear that the problem lies in the debugger itself. Can anyone help?
As your message explained, sp_sdidebug has no EXECUTE permission. You can set database permission in the database management tool. Did you do it already?
> I am learning the debugger using IBuySpy. I make small changes to the code > and use the debugger to see the effects of my changes. WindowsXP crashed and > now when I try to debug IBuySpy, I get the following errors while the > programs is starting, and these errors have nothing to do with the areas I > have changed. IBuySpy wirks flawslessly if I run it without debugging. I > would appear that the problem lies in the debugger itself. Can anyone help?
When you try to debug your application the TSQL debug engine is trying to attach. According to the error message, you do not have permission to debug TSQL code on the server. So a failure occurs.
But when you just RUN the app, it will work because none of the debug engines are attempting to attach.
Here is how to resolove your problem:
First of all try [MVP]SmileSeo's suggestion and setup the permissions for TSQL debugging, if that is what you are trying to do. Also if you are running SQL2K SP3 then you will also need to run the following TSQL code once
exec sp_sdidebug 'legacy_on'
Or if you do not want to debug TSQL code, simply go to the Project Properties->Debug->Enable SQL Debugging and uncheck it.
> Did I forget to take a bath or something??? Must be some reason for being > ignored. Perhaps there are no Gurus out there. Oh well! I tried!
> "Bill Thames" <b...@eritter.net> wrote in message > news:uZ1za2KbDHA.424@TK2MSFTNGP10.phx.gbl... > > I am learning the debugger using IBuySpy. I make small changes to the code > > and use the debugger to see the effects of my changes. WindowsXP crashed > and > > now when I try to debug IBuySpy, I get the following errors while the > > programs is starting, and these errors have nothing to do with the areas I > > have changed. IBuySpy wirks flawslessly if I run it without debugging. I > > would appear that the problem lies in the debugger itself. Can anyone > help?
I sure do appreciate all the response to my problem. Thanks to all.
Now then, I am using MSDE and can't find any kind of database management tools. I can't even find reasonable documentation. How do I manage the server without installing the full (expensive) SQL-2000?
> When you try to debug your application the TSQL debug engine is trying to > attach. According to the error message, you do not have permission to debug > TSQL code on the server. So a failure occurs.
> But when you just RUN the app, it will work because none of the debug > engines are attempting to attach.
> Here is how to resolove your problem:
> First of all try [MVP]SmileSeo's suggestion and setup the permissions for > TSQL debugging, if that is what you are trying to do. Also if you are > running SQL2K SP3 then you will also need to run the following TSQL code > once
> exec sp_sdidebug 'legacy_on'
> Or if you do not want to debug TSQL code, simply go to the Project > Properties->Debug->Enable SQL Debugging and uncheck it.
> Hope this helps.
> Regards
> Richard
> "Bill Thames" <b...@eritter.net> wrote in message > news:uqJpir0bDHA.2684@TK2MSFTNGP11.phx.gbl... > > Did I forget to take a bath or something??? Must be some reason for being > > ignored. Perhaps there are no Gurus out there. Oh well! I tried!
> > "Bill Thames" <b...@eritter.net> wrote in message > > news:uZ1za2KbDHA.424@TK2MSFTNGP10.phx.gbl... > > > I am learning the debugger using IBuySpy. I make small changes to the > code > > > and use the debugger to see the effects of my changes. WindowsXP crashed > > and > > > now when I try to debug IBuySpy, I get the following errors while the > > > programs is starting, and these errors have nothing to do with the areas > I > > > have changed. IBuySpy wirks flawslessly if I run it without debugging. I > > > would appear that the problem lies in the debugger itself. Can anyone > > help?
|
