SQL CLR Assembly fails to debug
-
Wednesday, February 01, 2012 4:44 PM
I have a _running_ CLR assembly built against .NET 2.0. It _runs_, but I still want to be able to debug it. This assembly is debuggable on at least 3 other dev computers; on one after I hit F5 I get a message box from Visual Studio that says "The SDTInternalRunManager service could not be found" (see below).
Environment (in all cases, whether F5 works ok or displays a message box): Win7 or Win2008ServerR2, Visual Studio 2010 Pro + MSSQL 2008R2 Express or Enterprise, all SPs and updates to OS, VS and SQL Server installed.
Googling on SDTInternalRunManager brings _nothing_.
- Moved by Barry WangMicrosoft Contingent Staff Wednesday, February 08, 2012 2:41 AM (From:Visual Studio Setup and Installation)
All Replies
-
Friday, February 03, 2012 6:20 AM
Hi alexms_2001,
Welcome to the MSDN forum.
May I ask one question to narrow down the error? Does this kind of error occur on all of your projects? I need to know whether your installation of VS is perfect.
Best regards,
Barry Wang [MSFT]
MSDN Community Support | Feedback to us
-
Friday, February 03, 2012 1:57 PM
Hi Barry,
> Does this kind of error occur on all of your projects?
Not at all, all the rest (console, service, web, silverlight, you name it) works perfectly
> I need to know whether your installation of VS is perfect.
That was my first thought - to repair or deinstall/install VS. But not only this is a pretty lengthy process (incude SP in a mix), it is hard to be sure that it will change anything.
Do you happen to know, what that SDTInternalRunManager service is? What exe/dlls to look for? What to re-regsvr32? I do not see this puppy on other computers where this same solution can be debugged just fine...
Just one more thing: I am an admin on the box, and VS runs with elevated priviliges.
Any (any!) advice will be appreciated.
Alexms_2001@yahoo.com -
Wednesday, February 08, 2012 2:40 AM
Hi Alexms_2001,
From your description, your post here are off-topic for this "Visual Studio Setup and Installation" forum. I'll move your thread off-topic. Maybe you should repair your OS or do something about your project.
Thank you for understanding.
Best regards,
Barry Wang [MSFT]
MSDN Community Support | Feedback to us
-
Wednesday, February 29, 2012 8:26 AMI'm having the same problem, it's obviously an installation problem, so not much help moving the post. Barry - did you get anywhere with it?