Can't run SSIS package in Visual Studio. The directory name is invalid

0
votes

I am attempting to run a simple SSIS package in Visual Studio (15.9.0). This is the first time I've used SSIS. My error message is at the bottom, because it's quite lengthy. Directly below is my attempt to fix the error.

I followed the directions of this link: https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-2017

1.) I selected the checkboxes for "Data Storage and Processing" in Visual Studio Installer 2.) I uninstalled SSDT 3.) I downloaded SSDT for Visual Studio (15.8.2) 4.) I selected the "SSIS" checkbox on the installation of SSDT.

I am continuing to get the error message below. Thanks for any help in advance!

>

Failed to start project (Microsoft Visual Studio)

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

The directory name is invalid (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) >

3
c#sql-servervisual-studiossissql-server-data-tools
Is this a new project? it seems that VS is complaining about a directory in the .sqlproj file. It's just text so it's easy to read and fix if need be – user1443098
First make sure SQL Server is installed properly. Use SQL Server Management Studio (which comes with SQL Server) and make sure you can log into the Server. Did you download and install the full version of SQL Server? The SQL Service may not be set to start automatically so check Service and make sure the service is running. – jdweng
To user 1443098. Yes. This is the first time I've ever created an "Integration Services Project". I'm able to connect to the SQL Server database. Inside of my "Connection Manager", I can test the database connection and it succeeds. – Cooler
Yes, SQL Server is setup. I'm at work, so I don't have permissions to check if the SQL Service is running. I assume it is running, since I'm able to connect to the database. – Cooler

3 Answers

2
votes

Answer 2

See the response from Microsoft.

https://social.msdn.microsoft.com/Forums/Windowsserver/en-US/aa3a46fb-2f09-4808-b6db-baa1553f6401/failed-to-start-project-microsoft-visual-studio?forum=sqlintegrationservices

Answer 1 Based on the question and user comments, I think you may have installed SSDT incorrectly. When installing SSDT, you need to select Install SSDT for 2017 with a new instance of VS 2017. Then, Select Integration services (kind of mandatory here b/c thats what you are installing), Reporting Services and/or Analysis Services.

https://developercommunity.visualstudio.com/comments/345539/view.html

Update 1

SSIS has a long and tortuous history with Visual Studio integration - it used to just install as a new set of Business Intelligence projects (i.e., SSIS, SSRS, and SSAS) within Visual Studio itself, without requiring a new standalone installation (at least up through VS 2013, I never used VS 2015). Even the product's name has gone through a circus show: it went from DTS, to SSDT-BI, to SSDT - stay tuned for more changes from the marketing department folks!

As of VS 2017, SSDT has to be installed as a new instance of Visual Studio. This means that you will effectively have two instances of Visual Studio installed on your machine:

  1. For all SSDT related projects (i.e., Integration Services [IS], Reporting Services [RS], and Analysis Services [AS]).
  2. For all other non-SSDT related projects.

Note: I do not fully understand why Microsoft chose to split the development of SSDT into a standalone instance of VS 2017, but personally (and this is my own 2 cents) I hate it. The new Preview release cadence model has led to more problems than solutions and has made the relationship between VS2017 and VS2017 SSDT so unstable that I only install new preview releases on test boxes before installing them on my own. Microsoft has released some really bone-headed bugs (i.e., unable to deploy package from project, unable to open VSTA for script tasks/components due to regression issue with VS2017). It is enough to drive one bonkers. I currently use the following:

  1. Visual Studio 2017 (SSDT): 15.8.2
  2. Visual Studio 2017: 15.7.6
1
votes

I finally got my SSIS package to run successfully! I was previously running Windows 7 64 bit OS and the version of SQL Server was 32 bit. I installed Windows 10 64 bit OS and now my SSIS package ran successfully. It seems that the OS and SQL Server must both be 64 bit.

Below are the different versions of technology I'm running

Windows 10 64-bit Operating System - SQL Server Standard 2012 (64-bit) - Visual Studio Professional 2017 (Version 15.9.4) - SQL Server Data Tools for VS 2017 (Version 15.8.2) - SQL Server Management Studio (Version 17.9.1) - The Project Template inside of VS was named "Integration Services Project" under the "Business Intelligence" tab.

Links

0
votes

Script editor in VS 2017:::::::::::::::
enter image description here