Error in Visual Studio 2017 Integration Services project: Unable to start debugging. The debugger is not properly installed.

Article
2017-12-11

Question

_{Monday, December 11, 2017 6:08 PM | 3 votes}

I just installed Visual Studio 2017 preview and then ran the brand new SSDT installer. I'm able to create an Integration Services Project, but when I click the Start button, I get the following error. I've tried everything I can find to do about this error but nothing is working. I do have Windows Communications Foundation (I think it is) installed. I've registered the msdbg2.dll file. I don't know what else to do. No one has addressed this issue with an Integration Project. Any suggestions?

TITLE: Microsoft Visual Studio

Failed to start project

ADDITIONAL INFORMATION:

Unable to start debugging.
The debugger is not properly installed.
Run setup to install or repair the debugger. (Microsoft.DataTransformationServices.VsIntegration)

Unable to start program 'DTS'.

The debugger is not properly installed. Cannot debug the requested type of code. Run setup to install or repair the debugger. (Microsoft Visual Studio Debugger)

All replies (29)

_{Tuesday, December 12, 2017 3:18 AM | 1 vote}

Hi Karen,

Thank you for posting in MSDN forum.

Please try with following steps:

1. Navigate to path: C:\Program Files (x86)\Microsoft Visual Studio\Installer

2. Run the vs_installer> Continue>More>Modify>Individual Components>Development activities

check and install: Windows Communication Foundation

3. Restart your VS, to build your project again.

If any problem persists, please feel free to contact us, we will continue to help you troubleshoot..

Best Regards,

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

_{Tuesday, December 12, 2017 4:02 AM}

It's already installed. At least, it shows up when I run the VS Installer for Individual Components. Karen

_{Tuesday, December 12, 2017 4:24 AM}

I don't know what to say. I've followed all the instructions I'm aware of. I hope there's something more to try.

Karen

_{Tuesday, December 12, 2017 5:31 AM}

Hi Karen,

Thank you for your update.

You could also check if the installer is updated to the latest version. currently it's 15.5.1

I suggest you re-download the newest installer from https://www.visualstudio.com/downloads/ , run the latest installer to upgrade to repair/install the WCF again.

If the error persists after tryin above, please use http://aka.ms/vscollect to gather the installation logs. find vslogs.zip from %temp% folder. Please upload the file to Onedrive and share the link here. I will help you check the log and find the reason.

Best Regards,

_{Tuesday, December 12, 2017 7:12 AM}

Thank you. I'll do that in the morning. I'm pretty sure I have the latest installer, but I'll check.

I don't think you can just 'repair' an individual component, but I can repair the installation of VS 2017 preview, hopefully with the new installer. I've done that at least five times over the last several days, but a new installer may make a difference. I don't think I should remove Windows Communications Foundation and then reinstall it. I would be skeptical of doing that.

I'll be in touch tomorrow.

Karen

_{Tuesday, December 12, 2017 7:24 AM}

Hi Karen,

I'm still investigating this issue, please see a similar case:

The debugger is not properly installed. Cannot debug the requested type of code. Run Setup to install or repair the debugger.

You could refer to Peter's solution:

1. Clean folders: C:\Program Files (x86)\Common Files\Microsoft Shared\VS7Debug C:\Program Files\Common Files\microsoft shared\VS7Debug

2. Then recover Visual Studio

Or you could upload the log to us, I will check the log for detailed information.

Best Regards

_{Tuesday, December 12, 2017 7:33 AM}

I'm not sure what's meant by "cleaning" the folders mentioned. I did actually try deleting everything that looked as though it could be deleted. There were some files that didn't look as though they should be deleted. If what I have to do is delete EVERYTHING in those folders before I download the new installer and do the repair, you'll have to let me know. I can check those folders again, but now I'm uncertain about what to delete and what to leave.

And I don't know what's meant by "recovering" VS. I know how to repair. I hope that's what that means.

There are also comments about unchecking the "Enable Javascript debugging for ASP.NET" checkbox, but that doesn't relate to an Integration Services project. I'm wondering if the brand new version of SSDT that I installed may have left something out or done something. All I really know is that I can't debug a new Integration Services project.

Thank you again so much.

Karen

_{Tuesday, December 12, 2017 7:38 AM}

Hi Karen,

Clean is deleting everything under this location.(You could back up them all before doing clean) .

Recovering is to repair the whole VS.

Best Regards,

_{Friday, December 15, 2017 8:10 PM}

I followed those instructions and no luck. I still get the same error with the debugger.

And it looks as though my Visual Studio monthly subscription through Azure doesn't come with any technical support incidents and Microsoft think it's acceptable to try to charge me $500 to fix their installation issue!!!! I am furious!

_{Monday, February 5, 2018 8:34 PM}

I have exactly the same issue...

_{Sunday, May 13, 2018 5:49 PM}

I have exactly the same issue...

_{Wednesday, May 16, 2018 10:06 AM}

I've also posted the same problem, with no replies, here.

_{Friday, May 18, 2018 8:33 AM}

Me too!

_{Wednesday, May 23, 2018 3:13 PM}

SAME PROBLEM WITH ME. I TRIED ALMOST EVERY THING. NOTHING IS WORKING.I AM STRUGGLING FOR THE LAST ONE WEEK...

===================================

Failed to start project (Microsoft Visual Studio)

===================================

Unable to start debugging.
The debugger is not properly installed.
Run setup to install or repair the debugger. (Microsoft.DataTransformationServices.VsIntegration)

Program Location:

at Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.LaunchVsDebugger(IVsDebugger iVsDebugger, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.ValidateAndRunDebugger(Int32 flags, IOutputWindow outputWindow, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32 launchOptions, ProjectItem startupProjItem, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchActivePackage(Int32 launchOptions)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32 launchOptions, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.Launch(Int32 launchOptions, DataTransformationsProjectConfigurationOptions options)

===================================

Unable to start program 'DTS'.

The debugger is not properly installed. Cannot debug the requested type of code. Run setup to install or repair the debugger. (Microsoft Visual Studio Debugger)

Program Location:

at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.LaunchVsDebugger(IVsDebugger iVsDebugger, DataTransformationsProjectConfigurationOptions options)

_{Wednesday, May 23, 2018 3:13 PM}

===================================

Failed to start project (Microsoft Visual Studio)

===================================

Unable to start debugging.
The debugger is not properly installed.
Run setup to install or repair the debugger. (Microsoft.DataTransformationServices.VsIntegration)

Program Location:

===================================

Unable to start program 'DTS'.

The debugger is not properly installed. Cannot debug the requested type of code. Run setup to install or repair the debugger. (Microsoft Visual Studio Debugger)

Program Location:

_{Thursday, May 24, 2018 4:01 PM}

My VS 2017 was fine this morning (Thu 24/05/2018) - only installed for the first time 2 days ago on a brand new PC.

Around 10:00 was informed there was an upgrade, so upgraded -> 15.7.2.

After the upgrade - "The debugger is not properly installed etc.". I have tried:

uninstalling and re-installing. no good
Windows Communication Foundation ticked - no good.
delete all files in the VS7Debug folder, and repair, still no good.

Reinstall Windows 10 is my next option.

Edit to Add: 29/05/2018

Re-installed Windows 10 on Friday. Everything working fine now. Can Build and run in debug.

Until this morning (Tuesday) (didn't use it on Monday) - and the damn error is back. This is getting really really stupid.

I have now unboxed a brand new Leveno machine, and am going to try a trial Professional version with no anti-virus installed. No SQL Server or Management Studio,

Further: 29/05/2018

Have installed VS2015 on both the new Leveno and my original machine - which I had to rebuild again. I don't trust VS2017 and have currently wasted so much time with this fault.

_{Monday, May 28, 2018 7:15 AM}

I am having the same issue with Visual Studio Community 2017 15.7.2 and 15.7.1

Can someone please advise when / if this will be addressed?

I have done all the steps proposed in the answer above, none of these work.

It is probably better to use VS 2015 until this is sorted out i reckon

_{Monday, May 28, 2018 11:24 AM}

Same over here, seems to be on Azure only, local and other remote installs (with same versions, but different host) work just fine.

Quite freaking annoying MS. Especially the lack of responses.

_{Monday, June 4, 2018 10:32 AM}

Exact same problem here...

_{Tuesday, June 5, 2018 12:34 PM}

Same error with VS 2017 Professional version 15.7.3 and SSDT updated to release 15.6.0...

_{Monday, June 11, 2018 3:40 AM}

Hi all,

This is Bo Fan from SSIS team. Could you give detailed reproduce steps on this issue so that I can reproduce it in my machine and investigate it. Thanks!

_{Monday, June 11, 2018 4:27 AM}

Hi Bo,

I've outlined the steps here in the link below.

https://stackoverflow.com/questions/50563004/sql-server-data-tools-2017-for-visual-studio-2017-unable-to-start-debugger-err

Basically, I was trying to import a CSV file into SQL Server 2017 and I get the debugging error.
I tried everything outlined in S.O. post before giving up and using VS2015 + SSDT for 2015.

Here's the link to the CSV
http://www.superdatascience.com/wp-content/uploads/2015/08/Bank-Customers-Demo.csv

_{Tuesday, June 12, 2018 4:31 PM}

I get exactly the same issue when trying to execute an SSIS package from within VS 2017 (15.7.3).

I had problems installing SSDT (particularly SSIS), so that may have had something to do with it.

I've tried all the solutions mentioned above, with no luck.

_{Tuesday, June 12, 2018 11:32 PM}

Any updates on the resolution for this issue? I'm getting the same error in SSSI trying do a Run Task on a SQL Task object. Thanks!

_{Saturday, June 16, 2018 3:17 PM | 1 vote}

I have the same problem, using VS 2017 15.7.3.
None of the proposed solutions worked for me, but I was able to workaround the problem by installing a standalone instance of SSDT and opening the SSIS project from there.

Both instances have the same version of the "Microsoft Integration Service Project"- 1.5.

_{Wednesday, July 25, 2018 9:55 AM | 2 votes}

If it helps anyone, I was able to get this resolved by re-running the SSDT standalone installer (15.7.1) as found in this link:

https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-2017

I originally did not have Analysis Services selected, so I was able to select it so it would actually install something and it must have installed enough to correct the "debugger" issue as well. My SSIS packages now run without this error.

I would assume if you've had all of the components installed, that you could remove one through the installer then re-install it and it may correct this issue. Hope this helps.

_{Thursday, August 9, 2018 1:29 PM}

Hi, thanks for the tip, that solved it for me. And thanks to Microsoft for keeping me busy by putting semi-defunctionalised products on the market. <- Obs irony.

_{Monday, April 1, 2019 9:35 PM}

Hi, Waff8 thanks for the tip it worked :)

_{Tuesday, June 30, 2020 11:57 PM}

Just installed VS 2017 Enterprise and SSDT june 2020 and in debug mode everything works perfectly. When I "Start without Debugging" get a "cannot execute the package. the ssis runtime for "sqlserver2017 is not properly installed" very quickly. Nothing wrong with the infrastructure because debug runs perfectly, counts rows, reads teradata, runs script task like a champ. Also can move the .dtsx package to Azure and it runs, guess it's just an execution on the client problem. Interesting, when I run my two packages from the laptop command line the script task fails on some version problem but the Teradata read runs perfectly. So no infrastructure problem with dtexec on the laptop other than when Visual Studio tries to "Start without Debugging". VS 2017 is 15.9.4, sql server data tools is: 15.1.61810.11040, ssis doesn't show version unless I "copy" the version and it's 15.0.1100.123. This is a big company and we installed what the company gave us for ssdt. we don't get admin so we can't download and reinstall. I'm pretty sure that debugging didn't work until I got "SQL Server Integration Services 12.0" set to "Automatic" in the Services utility. Before that I think it said it couldn't count rows when debugging.

Share via

Error in Visual Studio 2017 Integration Services project: Unable to start debugging. The debugger is not properly installed.

Question

All replies (29)

Edit to Add: 29/05/2018

Further: 29/05/2018

Additional resources