I am working on an SSIS package in VS 2017 targeting SQL Server 2016. Sometimes when I go to run it (hit the Debug button), it doesn't run any tasks, it just goes through the validation steps and stops, showing the message in my screenshot. None of the tasks have green checkmarks or red x's. No errors or warnings in the Progress tab. I have to close and reopen the package for it to run, and then a few hours later, I'm usually back to this problem. Anyone know what could be causing this? Not sure if it will cause any issues when it runs from a server later, as it is similar to this question that went unanswered.
If it matters, the package archives some files, runs some Execute SQL tasks to run stored procedures in Oracle or SQL Server, then pulls data from the database and exports to csv files.
I had the same problem with SSDT 2017 targeting SQL Server 2016. Never found out what caused it as it happened intermittently. Uninstalled and reinstalled SSDT and never had any problems again.
I've been doing some self directed learning in SSDT 2013 and for some reason the Edit Script button won't work.
I've read through some threads, the closest being this one and also took up some advice about opening the software as Administrator but still it won't work.
Moreover, I tried to install SSDT 2012 but apparently I have that already loaded but can't find it in my apps bar.
Does anyone have any further ideas or suggestions?
I recently created a new SSIS project from within VS2015. I added a script task and when I click on the "Edit Script" button. Visual Studio opens; however, there's no solution
I'm running VS as administrator. I've tried re-installing Microsoft Visual Studio Tools for Applications 2015. With no luck. I did once get the solution to pull up after I re-installed Microsoft Visual Studio Tools for Applications 2015; however, the next time I clicked "Edit Script" there was nothing.
Is this a bug withing VSTA or has anyone else came across this issue?
"Edit Script" buttion from within the Script Component:
No solution when clicking "Edit Script":
Ok, for me this problem was due to Resharper - if I go under Tools | Options | Resharper and Suspend Now it allows the VSTA editor to display each time. Hope this helps
I've solved the exact same problem today. In my case it was most likely caused by installing and removing several versions of VS/SSDT without some proper clean-up.
Go to Control Panel -> Uninstall or change a program -> "Microsft SQL Server Data Tools for Visual Studio 2015" -> Change -> Repair.
Repeat the steps for "Visual Studio Tools for Applications 2015".
This should only fix your installation and not affect any of your projects.
After restarting my Windows the problem was fixed!
I have VS 2013 (with VSTA 2012) and VS 2015 (with VSTA 2015). I had the same problem: If I tried to edit a Script Task (both in VS 2013 SSIS or VS 2015 SSIS project), the VS 2015 shell opened, but was empty.
I tried the solution described by Rae: Uninstalling "Visual Studio Tools for Applications 2015" and subsequently repairing "Visual Studio Tools for Applications 2012". This solution worked for VS 2013, after that, all scripts are opened in VS 2012. But after that, in VS 2015 SSIS Projects, I could no longer edit Script Tasks. (Error message "Could not load file or assembly 'Microsoft.VisualStudio.Tools.Applications, Version=14.0.0.0,...")
The solution was:
- Repair "Microsoft SQL Server Data Tools - Visual Studio 2015" (which re-installed VSTA 2015). After that I had the same problems like at the beginning, VS 2015 Shell opened empty, without source code file.
- Install VS 2015 Update 3 (like recommended by Rob Nicholson). This was the fix...
After that, I can edit Script Tasks both in VS 2013 SSIS and VS 2015 SSIS projects, both open the VS 2015 shell.
I was experiencing this issue with an SSIS 2012 project.
Uninstalling "Visual Studio Tools for Applications 2015" and subsequently repairing "Visual Studio Tools for Applications 2012" got it for me.
My SSIS project in VS2012 would try opening scripts in a VS2015 instance. After uninstalling VSTA 2015, VS2012 now successfully opens the scripts in a VS2012 instance.
For reference, I have both Visual Studio 2012 and Visual Studio 2015 installed. I also have SQL Server Data Tools v11.1 and v14.0 installed.
I'm guessing this issue comes down to clashing versions of Visual Studio Tools for Applications.
I tried many of the proposed solution but could not get this working. 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
I've encounted the same problem as well.
Since no solution to repair VisualStudio until now, I began to do the job by writting my own code directly in the DTSX file.
If your logic business was not very complex, this solution maybe suitable:
Firstly, add a "Scritp Task" in your package of SSIS project. It will generate lots of code in the DTSX file, and save our work.
Open DTSX file of the package in Notepad++/SublimeText, as your wish, and look for "// TODO: Add your code here", which was in a public void Main().
Fun Coding!
I've uploaded a project of TestScriptTask, in case of making coding easier in visual studio. It needs SQL Server Developer edition installed at least (Express edition probably would not work, didn't test).
Restart VS 2015, then it will load the next time you try.
Every time it fails, restart VS.
Yes simple/tedious... but works. Just write everything correctly the first/1 time you edit the script ;) easy
I came across this issue and it was driving me crazy. GIT is definitely what is causing this. When you take the solution out of the source control directory, the problem disappears.
After deploying my reports to the reporting server, I tried to add a subscription on one of my reports. It was not possible, and I got the error as described in this link.
http://www.kodyaz.com/reporting-services/subscriptions-cannot-be-created.aspx
All my reports use the same shared data source.
I applied the solution proposed in this link and it worked.
BUT Each time I deploy my reports (from SQL Server Data tools for Visual Studio 2013); the error comes back.
I tried to modify the properties of the shared datasource with SQL Server Data tools for Visual Studio 2013 before deploying;similarly to what is shown in the hyperlink, but in this case I am not able to access my reports anymore.
So, it seems that I could only modify the credentials "online" with my web browser; and not "offline" with SQL Server Data tools for Visual Studio 2013.
I remarked one difference between the "offline" and "online" properties of the shared data source : online, it is possible to check the box "Use as Windows credentials when connecting to the data source". This checkbox does not exist in SQL Server Data tools for Visual Studio 2013.
This means : each time I redeploy the reports from SQL Server Data tools for Visual Studio 2013, I have to do the online manipulation on my web browser to get the subscriptions working; which is of course really annoying...
Does someone know how to fix it?
Thanks in advance and sorry for my poor English.
I had a similar problem. I solved it by simply deploying the whole project and not only the shared data source.
I've got a solution with a 2012 SSIS project included. I've also got a 2010 SSIS project included. Both was working well I was duplicating functionality from one project to another. After going offline from TFS i got the following error:
Cannot show the editor for this task. (Microsoft Visual Studio)
Value does not fall within the expected range. (mscorlib)
In EventViewer I got the following error this morning:
Microsoft SSIS Service:
Registry setting specifying configuration file does not exist.
My research showed me it could be a permissions problem and I changed my Integration Services instance to use the NetworkService account.
I've also edited my registry key to reflect the correct path to the MsDtsSrvr.ini.xml file.
The error did not appear again however the problem still persists.
I've done a repair. Deleted SSDT 2012 along with the Data Tools enu and Build Utilities. Nothing helped.
PLEASE HELP!