SSIS 2008 – Cannot Show Visual Studio 2008 Tools for Applications error

Should you come across this error message, “cannot show visual studio 2008 tools for applications”, you may have to clean up your VSTA environment.

You may also have the following additional error message:
The System Cannot Find The File Specified

Here’s how to fix it, thanks to Silviu Guea, Microsoft.

Create a batch file with the following code. Execute it. Ignore any errors. Try again. If it doesn’t work, you may have to contact Microsoft support or try many uninstall/reinstall combinations. For me, this worked the first time I tried it. Finally, the code:


@rem start batch file
@rem delete the VSTA registry cache from the current user
REG DELETE HKCU\Software\Microsoft\VSTA /f
REG DELETE HKCU\Software\Microsoft\VSTAHost\SSIS_ScriptTask /f
REG DELETE HKCU\Software\Microsoft\VSTAHost\SSIS_ScriptComponent /f

@rem delete the VSTA registration cache for SSIS script task and data flow script component
REG DELETE HKLM\Software\Microsoft\VSTAHost\SSIS_ScriptTask /f
REG DELETE HKLM\Software\Microsoft\VSTAHost\SSIS_ScriptComponent /f

@rem delete the cached files from the HDD
rd /s /q "%AppData%\Microsoft\VSTA"
rd /s /q "%AppData%\Microsoft\VSTAHost\SSIS_ScriptTask"
rd /s /q "%AppData%\Microsoft\VSTAHost\SSIS_ScriptComponent"

rd /s /q "%USERPROFILE%\Local Settings\Application Data\VSTA"
rd /s /q "%USERPROFILE%\Local Settings\Application Data\VSTAHost\SSIS_ScriptTask"
rd /s /q "%USERPROFILE%\Local Settings\Application Data\VSTAHost\SSIS_ScriptComponent"

@rem re-generate the VSTA files for SSIS script task and component
"%ProgramFiles%\Microsoft Visual Studio 9.0\Common7\IDE\vsta.exe" /hostid SSIS_ScriptTask /setup
"%ProgramFiles%\Microsoft Visual Studio 9.0\Common7\IDE\vsta.exe" /hostid SSIS_ScriptComponent /setup

@rem end batch file

Download file here: vsta_cleanup.txt

6 thoughts on “SSIS 2008 – Cannot Show Visual Studio 2008 Tools for Applications error

  • Kyle

    You may want to change the program files variable to %PROGRAMFILES(X86)% for those of us using 64 bit OS (I had to anyway).

    I also had to add this line – and none of the other lines were valid for me.

    AND – it didn’t fix my issue.

  • thiết kế website

    Great website. Lots of helpful information here. I’m sending it to several pals ans also sharing in delicious. And certainly, thanks in your sweat!

  • Pingback: SSIS Links Collections « My experiments with SQL Server…!

  • Amit

    Great… It worked for me…

  • Emily

    Great! It saved my life!

  • Karthik

    SSIS Script Editor throws an exception

    up vote
    3
    down vote
    favorite
    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?

    visual-studio-2010 ssis bids vsta
    shareimprove this question
    asked May 3 ’12 at 14:46

    Ray Saltrelli
    1,81721429
    1
    I’ve seen this before in earlier versions. If I remember correctly, I reinstalled .Net to correct it. I haven’t experienced it in 2012, yet. You may want to consult connect.microsoft.com/VisualStudio/feedback/details/564956/… and social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/… – I cannot remember what worked the last time I encountered this message in SSIS 2008… Apologies I cannot be more help. – Andy Leonard May 3 ’12 at 19:21

    Thanks for your help. I uninstalled and reinstalled SQL Server 2012 as recommended by the links you provided. The installation completed without any errors but now nothing SSIS related works. I get a half dozen errors saying “[such and such] is not installed correctly” when I attempt to open my SSIS package project in Visual Studio. What a nightmarish web of dependencies this thing is! – Ray Saltrelli May 4 ’12 at 19:46

    Hi Ray, I am sorry to hear about this experience. A couple questions: 1) Are you installing the RTM version of SQL Server 2012? 2) Is this a “clean” installation (are you installing over a release candidate or other pre-release software)? – Andy Leonard May 4 ’12 at 19:56
    add a comment
    6 Answers
    active oldest votes
    up vote
    5
    down vote
    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.

    shareimprove this answer
    answered Nov 5 ’12 at 21:59

    Klay
    5112
    1
    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 – Raul Vejar Mar 15 ’13 at 21:52
    add a comment
    up vote
    4
    down vote
    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.

    shareimprove this answer
    answered Jan 31 ’13 at 21:14

    Anoop Verma
    1,019714
    1
    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/… – acdcjunior May 25 ’15 at 19:27
    add a comment
    up vote
    1
    down vote
    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.

    shareimprove this answer
    answered Jul 21 ’12 at 15:52

    Bill
    111
    add a comment
    up vote
    0
    down vote
    For me the solution was:

    close bids (I’m on 2008r2)
    reopen
    edit the script (it allowed me to edit it once after restarting bids)
    delete all breakpoints
    make a trivial change, such as adding a blank line
    save
    That solved it for me.

    shareimprove this answer
    answered Dec 30 ’14 at 13:19

    WoundedEgo
    1456
    add a comment
    up vote
    0
    down vote
    This worked for me without doing any kind uninstall.

    My environment: Microsoft Visual Studio 9.0 (2008)

    Solution:

    Go to cd “C:\program files (x86)\microsoft visual studio 9.0\common7\ide\”
    Execute command vsta.exe /setup /hostid SSIS_ScriptTask. This will open VSTA with blank project. Let it open and then close it.
    Execute command vsta.exe /setup /hostid SSIS_ScriptComponent. This will open VSTA with blank project. Let it open and then close it.
    Open your solution/packages that contains the script task.
    Click Edit button in Script task and it should open now. Just in case if it dont, I would suggest to keep the blank vsta of step 2 & 3 open and then click the Edit button in script task.
    Took almost two hours and thankfully it worked for me. I did not have admin right to perform all that nasty uninstall and registry edit solutions.

    Hope it helps someone!!!

    Reference : http://blogs.msdn.com/b/jason_howell/archive/2010/08/18/vsta-setup-and-configuration-troubles-for-ssis-2008-and-r2-installations.aspx

    shareimprove this answer
    edited Dec 4 ’15 at 7:04
    answered Dec 4 ’15 at 6:59

    Sandeep Gaadhe
    112
    add a comment
    up vote
    -1
    down vote
    accepted
    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
    shareimprove this answer
    answered May 7 ’12 at 19:37

    Ray Saltrelli
    1,81721429
    add a comment
    ok
    Your Answer

    Thanks for contributing an answer to Stack Overflow!

    Please be sure to answer the question. Provide details and share your research!
    But avoid …

    Asking for help, clarification, or responding to other answers.
    Making statements based on opinion; back them up with references or personal experience.
    To learn more, see our tips on writing great answers.

    Links Images Styling/Headers Lists Blockquotes Code HTML advanced help »

    Cannot show Visual Studio 2010 Tools for Applications editor.

    Just follow the below solution:

    Go to SQL Server Setup folder.
    Inside that folder “redist”.
    Under that one more folder “VSTA”.
    Under VSTA folder “X86” and “X64”
    Install the VSTA_RT30.
    It works fine.

Comments are closed.