cannot show Visual Studio Tools for Application editor in SSIS 2012

ssis sql-server-2012 vsta
Ananda Krishna picture Ananda Krishna · Oct 3, 2012 · Viewed 22.9k times · Source

When I click on EDIT SCRIPT button for Script Task in SSIS 2012 package,

It does not open the Script editor rather it shows:

"cannot show Visual Studio Tools for Application editor"

Couls not load file or assembly "Microsoft.visualstudio.tools.applications.core version=10.0.0.0 ...." system can not find the file assembly specified.

I tried the solutions provided in the following links:

http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/e5337b0c-7f70-4603-859e-fbc7d0cf1c37

SSIS Script Editor throws an exception

Answer

Haris Iltifat picture Haris Iltifat · Apr 22, 2013

First of all go to Program and Features and check whether you have "Microsoft Visual Studio Tools for Applications x86 Runtime 3.0" installed. Most probably you will see this below "Microsoft Visual Studio Tools for Applications x64 Runtime 3.0"

If it is not installed then you have the same issue that i have. To resolved this error, I put in my SQL Server installation disk. Then go to redist->VSTA->runtime->x86 and then run VSTA_RT30.msi

Related questions

SSIS Excel Connection Manager failed to Connect to the Source

I have a server that is capable of creating and running an Excel Import task using the Import Wizard. I am trying to automate that process by using a visual Studio 2010 Integration Services package, that I am developing on that …

Read More
SSIS: I don't see the package configuration wizard

Using SQLServer 2012 Enterprise, I don't see "Package Configuration Wizard" in SSIS when I do a right click in Control Flow tab. I can see all the other items (Log, Digital Signing...). Here are info about my install: Microsoft Visual Studio 2010 …

Read More
Which user credentials does Integration Services Catalog use to execute packages?

We have an SSIS package which reads text files from a shared network directory. When I execute this package in SSDT it works fine. When we however deploy the project to the Integration Services Catalog and attempt to run the …

Read More