January 13, 2004 at 4:36 pm
I would imagine this has been answered a dozen times - if so I apologize in advance.
I just moved to a new laptop machine (W-XP) and installed Sql2000. When I first tried to debug, I was unable and had to grant execution rights to sp_sdidebug and move the DLL from my .NET directory into the SQL/binn. Things worked great!
Today - I am getting the error#514...unable to communicate with debugger. I have tried running the DComCfg and granting launch and access rights to "everyone", setting the identity to "interactive user" and everything else I could find on the google groups or in BOL. Still no luck.
Recommendations?
TIA
Guarddata-
January 13, 2004 at 6:32 pm
Hmm... did you set up the service to run under your "Domain" account? If not I would try that.
Gary Johnson
Microsoft Natural Language Group
DBA, Sr. DB Engineer
This posting is provided "AS IS" with no warranties, and confers no rights. The opinions expressed in this post are my own and may not reflect that of my employer.
January 14, 2004 at 8:58 am
I installed SP3a and it seems to work again... Thanks for the brain cycles.
Guarddata-
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply