13

I am using SSIS 2014 and Visual Studio 2013. When I click on Edit Script button of script task no error nothing happens but script editor doesn't open. Nothing happens I have installed on my machine:

  • Microsoft Visual Studio Tools for Applications 2012
  • Microsoft Visual Studio Tools for Applications x64 Runtime 3.0
Andrea
  • 11,801
  • 17
  • 65
  • 72
user228777
  • 3,082
  • 9
  • 33
  • 50

4 Answers4

14

I had the same problem with the following setup:

  • Visual Studio 2017 Community Edition (15.6.6)
  • SSDT 2017 (15.5.2)
  • SQL Server 2017 Developer Edition

I solved repairing the installation of Visual Studio Tools for Application 2017 from the control panel:

enter image description here

Andrea
  • 11,801
  • 17
  • 65
  • 72
8

I've just had exactly the same problem. I've got both SSDT and SSDT BI installed for VS2012 and VS2013 but still couldn't get the Edit Script to open. I repaired my install of VSTA 2012 and also newly installed VSTA 2013 but still no luck.
Turns out I just had to run VS 2013 as administrator and it worked! Might not be the solution for all but worth a try if you've got all the correct applications installed.

Simon Peacock
  • 79
  • 1
  • 2
  • 1
    what if I dont have admin privileges? Will it be enough to ask the admin to give me full privileges on the application? – elvainch Aug 24 '17 at 07:48
7

I ran into this same exact issue. Try installing Sql Server Data Tools 2012 here as well as Sql Server Data Tools 2013 here. I am not sure why you would need both but for some reason the script task when only having SSDT 2013 installed still seemed to want to reference 2012 (see screen shot below).

Hopefully this helps.

enter image description here

Al Belmondo
  • 764
  • 10
  • 26
  • After installing the SQL Server Data Tools my VS 2013 tries to open VS2012 after pressing "Edit Script". Here I get the message "This program has known compatibility issues. "Check for solutions online" gives me nothing and "Run Program" starts VS2012. – ruedi Aug 14 '15 at 09:27
  • One reason that someone might need both SSDT 2012 and 2013 is because using SSDT 2013 you cannot work with SSIS packages for SQL Server 2012 and lower. http://blogs.msdn.com/b/analysisservices/archive/2014/04/03/sql-server-data-tools-business-intelligence-for-visual-studio-2013-ssdt-bi.aspx This is a serious PITA. – David Tansey Dec 09 '15 at 00:54
  • Have a VS 2019 install with the latest SSDT, still had to install SSDT 2012 to edit the script. – Bill Clyde Apr 22 '21 at 18:47
0

I have the same setup VS 2013 Professional, with SQL 2014 Data Tools. My VstaProjects window would open, but the ScriptMain.vb window, with the framework, would not open. Repair was not an option, so the tech removed and reinstalled SSDT 2014. It works now.

Al__H
  • 196
  • 4
  • 16