SSIS Script Editor throws an exception

Question

I have SQL Server 2012, SSIS, SSDT and Visual Studio 2010. I can create a new SSIS package and add a Script Task, but if I attempt to open the Script Editor for that Script Task I get the following error:

TITLE: Microsoft Visual Studio
------------------------------

Cannot show Visual Studio 2010 Tools for Applications editor.

------------------------------
ADDITIONAL INFORMATION:

Could not load file or assembly 'Microsoft.VisualStudio.Tools.Applications.Core, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. (mscorlib)

------------------------------
BUTTONS:

OK
------------------------------

From my own investigation into this error, I found that Visual Studio Tools for Applications appears to be a part of MS Office 2007 and higher. This seemed like an odd dependency for to have, but I installed MS Office 2010 just for grins. It didn't change anything. What else should I try?

Solution 1

I figured out my problem this morning. When I uninstalled SQL Server 2012 (and the remnants of 2008 left behind when I upgraded last month) I also uninstalled 3 packages that were actually part of Visual Studio 2010. Had I not done this, a reinstallation of SQL Server 2012 would probably have done the trick, but instead I found new errors. When I reinstalled these 3 packages from the Visual Studio 2010 distribution media, everything started working.

The 3 packages in question were:

• Microsoft SQL Server 2008 R2 Data-tier Application Project
• Microsoft SQL Server 2008 R2 Data-tier Application Framework
• Microsoft SQL Server 2008 R2 Transact-SQL Language Service

Solution 2

You will also get this error, if you are trying to debug a script task in VS 2010 and Run64BitRuntime is set to true. In order to debug, set it to false.

Solution 3

I was getting this error and nothing I came across corrected the problem until I logged off as my normal user and logged in as my local admin user. Once I logged in as an admin I could edit the script in my package. Once I logged back in as my regular user the edit script button worked for it too.

I assume it needed to register the assembly on the first launch and couldn't with my regular domain user.

Solution 4

I also got this same error when trying to open the Script Editor, but for a different reason. Not sure how it happened, but I had 3 copies of VSTA (different versions) installed. Once I removed all of them and re-installed SQL Server 2012, problem solved. Hope that helps.

View more solutions

Comments

[Raul Vejar]

Running VS 2010 as an admin worked for me as well. Then after it loaded fine for the 1st time it worked in non-admin mode from then on

[acdcjunior]

This worked for me. For those who don't know how to find that variable, follow this: Right Click on your PROJECTNAME under Solution Explorer then Properties -> Configuration Properties -> Debugging -> Debug Options -> Run64BitRuntime -> Should be True, set it to False. Also helps: help.pragmaticworks.com/dtsxchange/scr/…

[J Weezy]

Changing the runtime fixed it for me. Thank you, sirs!