I probably did something dumb to cause this, but on the off chance it’s not (just) me I thought I would blog about it.
I’ve been tinkering with SSIS 2016 in SQL Server 2016 CTP3. I set up a VM running Windows Server 2012 and installed the CTP along with SQL Server Data Tools for Visual Studio 2015 (October release).
After installing and configuring, I built an SSIS Catalog and poked around for changes (more on that in another post… or series of posts…). Then I began building SSIS packages to test stuff (see previous parenthetical comment). Except… I couldn’t get the VSTA code editor to open for my Script Tasks. It didn’t matter which language I chose, clicking the Edit Script button produced no code editor.
Durnit!
Someone’s probably found this and fixed it by now. But if they haven’t, and if you run into this issue, here’s how I resolved it:
1. I loaded the CTP3 iso file into the VM’s optical drive:
2. I browsed to the redist\VSTA\14.0 folder on the installation media and executed the vsta_setup.exe file:
3. When prompted, I selected the Repair button:
The application executed for about a minute and VOILA! My VSTA editors stated working:
w00t! Now, back to more testing…
:{>
Thank you – saved me spending the time figuring this out!
— CTP 3 preview created from Azure gallery
Thank you for sharing this.
Ran into the exact same problem with RC2. However, running the VSTA install tells me that it is blocked because there is a more current version. I installed Visual Studio first, then SSDT.
With the April 2016 update, I was able to simply run repair from Programs and Features to resolve the issue. Your tip helped me locate the right entry to repair though! Thanks.
For me reinstalling VSTA did not help. However I had a Resharper Extension installed . Disabling it from the Tools–> Reharper –> suspend , temporarily and again opening VSTA solved the issue .
@Sankalp Pande: Thank you very much for your tip for Suspending the Resharper. Which was the culprit blocking to load Script editor properly. It saved my whole day.
You are a life-saver. Tried a million things before this finally worked.
Thank you! This was a big help.
Have VS2015 Integrated Shell. Repair DID NOT fix the problem.
Thanks for sharing this!! This saved me a lot of time.
Hi Andy, I have tried repair without success. Do you have to use VS as administrator for this feature to work? Thanks!
I have to run VS as administrator for this feature to work in my case.
Thank you so much for this post. Still useful.
I notice that if I close the “ScriptMain.cs” file in the script editor before closing the code editor window itself, then the next time the script editor comes up, there is no code displayed.
If I just close the script editor, but leave “ScriptMain.cs” open, then the next time I click “Edit Script”, then the code still shows up.
I have the same Problem , and Your notice worked with me .
Many Thanks
This didn’t help me but after I updated SQL Data Tools to 14.0.61707.300 (the highest version of available for Visual Studio 2015 available) and applied Visual Studio Update 3 (14.0.25420.01) the code inside the Script Task / VstaProjects now populates correctly. As a side note my SQL/SSIS version is 2016 and Visual Studio Tools for Applications 2015 is at 14.0.23829. Hope this helps
Hi Bart,
A client noticed something similar happening when the Script Task resides in a Foreach Loop Container. I was able to reproduce the error and capture it on video. I sent it to the SSIS Dev Team.
:{>
Hi Rob,
I’m updating now. We shall see. Thank you for the tip!
:{>
Thanks for the post and the comments. A faced the same issue here: SSIS script freezing on a Data Flow. After disabling Resharper it worked!
thanks.. It works
I have been having the same problem for days and yours is the only fix that worked for me.
Hi Sal,
I’m glad to hear this post helped. Thank you for your feedback!
:{>
it’s working