Unable to open .dtsx file in Design View

Question

Unable to open .dtsx file in Design View

Viewing 15 posts - 1 through 15 (of 18 total)

You must be logged in to reply to this topic. Login to reply

Phil Parkin SSC Guru Points: 247183 More actions · Answer 1

Is the package part of an SSIS project? It needs to be. Open the project in SSDT and then open the package.

DaveBriCam SSCarpal Tunnel Points: 4302 More actions · Answer 2

I have SSDT open but I don't know from there what to open. I see a solution .sln file but when I open it here's what I see: Capture

Phil Parkin SSC Guru Points: 247183 More actions · Answer 3

Try right-clicking on the Payroll.dtsx package. You should see the option 'View Designer' – select that.

DaveBriCam SSCarpal Tunnel Points: 4302 More actions · Answer 4

Right clicking does not give me an option of View Designer

Phil Parkin SSC Guru Points: 247183 More actions · Answer 5

DaveBriCam wrote:

Right clicking does not give me an option of View Designer

Which version of VS are you using?

Did you install the SSIS extensions after installing SSDT? Take a look here for 2019.

DaveBriCam SSCarpal Tunnel Points: 4302 More actions · Answer 6

Visual Studio 17 Microsoft SQL Server Data Tools for Visual Studio 2017 SSDT Version 15.9.30

I don't remember installing any extensions, but I may have, all I know is it was working fine for building a rather involved package that was working well, and suddenly I can't do anything with the SSIS product.

This reply was modified 4 years, 5 months ago by DaveBriCam.
This reply was modified 4 years, 5 months ago by DaveBriCam.

Phil Parkin SSC Guru Points: 247183 More actions · Answer 7

I suggest you run this: https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-ver15#ssdt-for-vs-2017-standalone-installer

making sure you select 'SQL Server Integration Services' during installation. I'm not sure whether you have to uninstall your existing SSDT first.

Jonathan AC Roberts SSCoach Points: 18407 More actions · Answer 8

Try this.

In VS create a new SSIS project/solution.
Add the existing .dtsx to the new solution
Then try opening the package by double clicking it in Solution Explorer.

You also have to make sure the SSIS package version and the version of VS are compatible. For example, I have to use VS10 to open SQL Server 2012 SSIS packages.

DaveBriCam SSCarpal Tunnel Points: 4302 More actions · Answer 9

I had to uninstall everything to clean things up. Should I install VS before the link you posted?

Phil Parkin SSC Guru Points: 247183 More actions · Answer 10

DaveBriCam wrote:

I had to uninstall everything to clean things up. Should I install VS before the link you posted?

Assuming you have full VS Pro, yes.

DaveBriCam SSCarpal Tunnel Points: 4302 More actions · Answer 11

The link you supplied worked with no problems.... thanks!

DaveBriCam SSCarpal Tunnel Points: 4302 More actions · Answer 12

One more issue arose. I cannot edit my C# Scripts... I hit the button and C# won't launch... I ran the repair on VS 17 and restarted my machine and the problem persists. Any ideas?

Phil Parkin SSC Guru Points: 247183 More actions · Answer 13

DaveBriCam wrote:

One more issue arose. I cannot edit my C# Scripts... I hit the button and C# won't launch... I ran the repair on VS 17 and restarted my machine and the problem persists. Any ideas?

I've had this happen to me several times. It's a real showstopper and (you're not going to like this one bit!) the only way I was able to resolve it was to do a full uninstall/reinstall of SSDT. As far as I remember, I did not have to reinstall VS as well, which saves a few hours.

DaveBriCam SSCarpal Tunnel Points: 4302 More actions · Answer 14

Did an uninstall/reinstall of SSDT. Still can't see or edit my C# script. I uninstalled VS. What is the best link to reinstall VS & SSDT?

Phil Parkin SSC Guru Points: 247183 More actions · Answer 15

I have no link for VS Pro, you need to buy it or create a VS subscription.

Before you do that, can you try creating a brand new package and adding a script task to that, then see whether you can open the C# editor from there. Just to make sure that this issue is machine related, rather than package related.