Debugging throws error, but deployment works CTP4

Question

Hello,

i have difficulties in debugging a simple StoredProcedure in a SQL CLR Project with the latest version of SSDT.

The build assembly gets deployed to the SQL Server, but the debugging is not starting in VS2010. I get the error:

"The SDTInternaRunManager service could not be found".

Can't find anything in the web by this service name. I tried repairs, reinstalling VS2010, SQL Server and SSDT - but no change!

 

Please find attached a screen shot of the error. I work on Win7 64b

Any ideas?

 

All the best
Pat

 

Answer 1

Hi Pat,

In SSDT, SQL CLR projects are integrated directly into the database project.  If you want to debug in SSDT, make sure that your SQL CLR project has been upgraded to a database project.  The relationship between SQL CLR projects and SSDT projects, as well as instructions on how to upgrade a SQL CLR project are detailed in this forum post:  http://social.msdn.microsoft.com/Forums/en/ssdt/thread/8de3cbfd-e327-49f2-bdcf-d7a0783a4b47

Let me know if this solves your problem.

-Janet

Answer 2

Hi Pat,

 

First of all sorry for the inconvenience. Could you help us understand the problem by providing the repro steps? Also, you are using SSDT database project right? As you know, with Juneau, we only have one database project template. There used to be SQLCLR project template that comes with VS2010.

 

• Which SKU of VS2010 are you using? (Ultimate, Pro..)
• Do you have Dev10 SP1 installed also?
• Did you deploy the build assembly to remote server or localdb?
• Is the regular debugging working?

 

Also, please let us know the repro steps.

 

Thanks

Ilker

---

ilker Acar

Answer 3

Hi guys,

sorry for late answer...

Yes the project type has been already changed to database project! I am using vs2010 PRO and Sp1 is installed of course.

The deployment is running towards the remote sql server, debugging is working.

 

All the best

Pat

Answer 4

To double check, your issue has been resolved?

---

-GertD @ www.sqlproj.com

Answer 5

no it didn't

Answer 6

Hi Pat,

Could you please send us a log file so that we can see what's going on?

To do that;

1 )Start Logging: Open CMD prompt. In C:\ type, logman create trace -n SSDTDebug -p "Microsoft-SQLServerDataTools" 0x800 -o "%LOCALAPPDATA%\SSDTDebug.etl" -ets

2) Repro your scenario

3) Stop Logging : Type logman stop SSDTDebug -ets

4) Email me (mailto:[e-mail])  the log file , C:\Users\yourUserName\AppData\Local\SSDTDebug.etl

 

Let me know If you have questions

Thank you

---

ilker Acar

Answer 7

Hi Ilker,

sorry for not answering for a long time - i was working on other things in that time.

Can i still send you the etl file for checking what is going wrong with my installation?

All the best

Pat

Answer 8

Hi Pat,

 

Sure, please send me the etl file. Thank you.

 

Best

Ilker

---

ilker Acar

Answer 9

Pat,

Since the beginning date of this thread, we have released a new version of SSDT (updated version of the CTP4 bits). It is available here - http://msdn.microsoft.com/en-us/data/hh297027.

Please try and install/use this most recent release and let us know if you are still experiencing these problems.

Thanks,

Adam

---

Adam Mahood - Program Manager - SQL Server Data Tools