I am using SSIS 2014 and Visual Studio 2013. When I click on Edit Script button of script task no error nothing happens but script editor doesn't open. Nothing happens I have installed on my machine:
Microsoft Visual Studio Tools for Applications 2012
Microsoft Visual Studio Tools for Applications x64 Runtime 3.0
I had the same problem with the following setup:
Visual Studio 2017 Community Edition (15.6.6)
SSDT 2017 (15.5.2)
SQL Server 2017 Developer Edition
I solved repairing the installation of Visual Studio Tools for Application 2017 from the control panel:
I've just had exactly the same problem. I've got both SSDT and SSDT BI installed for VS2012 and VS2013 but still couldn't get the Edit Script to open. I repaired my install of VSTA 2012 and also newly installed VSTA 2013 but still no luck.
Turns out I just had to run VS 2013 as administrator and it worked! Might not be the solution for all but worth a try if you've got all the correct applications installed.
I ran into this same exact issue. Try installing Sql Server Data Tools 2012 here as well as Sql Server Data Tools 2013 here. I am not sure why you would need both but for some reason the script task when only having SSDT 2013 installed still seemed to want to reference 2012 (see screen shot below).
Hopefully this helps.
I have the same setup VS 2013 Professional, with SQL 2014 Data Tools. My VstaProjects window would open, but the ScriptMain.vb window, with the framework, would not open.
Repair was not an option, so the tech removed and reinstalled SSDT 2014. It works now.
Related
Is it possible to open a SSIS solution using Microsoft's free tools (Visual Studio Team Explorer and SQL Server Data Tools) or does it require a full installation of Visual Studio?
I am trying to do so with just the free tools and am getting an error saying that "this versino of Visual Studio is unable to open the following projects" then another one saying the solution I have opened is under source control but not currently configured for integrated source control in visual studio.
We have other users who use the full version of Visual Studio 2017 and it works fine so I am wondering if this is just a limitation of the free products offered by Microsoft.
To edit SQL Server 2005 SSIS packages, you need Visual Studio 2005 and installation of Business Intelligence Designer Studio, BIDS. This required a license, developer edition was sufficient, to access the tooling.
SQL Server 2008 & SQL Server 2008 R2 would install into Visual Studio 2008. This too required a SQL Server license as the media only existed on the server media.
SQL Server 2012 would install into both Visual Studio 2010 and Visual Studio 2012. This was delivered in both physical media installations and downloadable tooling which was rebranded to SQL Server Data Tools- BI Edition, now just SQL Server Data Tools and the components were just licensed via click through agreement.
SQL Server 2014 installs into Visual Studio 2013 and was now only available through the download of SSDT.
SQL Server 2016 added a new twist into the mix. It installed into Visual Studio 2015 but it could now create/edit/target SQL Server 2012, 2014 and 2016 packages. This was huge as until this point, as a consultant I would have required 5 different versions of the "same" program on my machine. Now I'd only need 3.
SQL Server 2017 installs SSDT in both Visual Studio 2015 and Visual Studio 2017.
I assume SQL Server 2019 will similarly target VS 2017 and VS 109.
Across all of these versions, if you didn't have Visual Studio installed, the installer would install the Visual Studio shell on your machine so that the project templates would work.
Last I knew, neither Visual Studio Community Edition nor VS Code will work with the SSDT templates so be sure and open the correct product to work with SSIS projects (.dtproj)
The warning/error about "under source control but not currently configured" smells like something is awry with how you have the TFS hook installed but I can't comment on that.
Download and install SSDT 2017 for Visual Studio
You can verify the status of your SSDT installation for Visual Studio by going to the Help, About Microsoft Visual Studio menu and looking for "SQL Server Integration Services." With ... 2017? you can now do a piecemeal install and only pick SQL Server Data Tools (database projects) or SSAS/SSIS/SSRS. Previously, the SSDT-BI install was trio of SS_S and SSDT (no BI) was the database projects.
Previous answer on where SSDT-BI is
You have at lease two options:
Use Visual Studio Community Edition together with SSDT. Still, you have to check its License terms with your Legal department - it might be not legal to use Community Edition in Enterprise.
Use Visual Studio Isolated Shell together with SSDT. More instructions on how to install it. As far as I know, it is legal to use it for debugging.
The VS Isolated Shell is usually installed with SQL Server 2014/16.
Microsoft SQL Server Management Studio closes in about five seconds after startup. The startup splash screen is displayed, but after that, nothing. No messages are being displayed (even in a console) and no logs occur in a Windows Event Viewer. I have tried to install different SSMS versions , i.e. 16.X, 17.Y, but it have not helped. I have also tried to repair VS 2017 and SSMS.
This problem occurred for the first time, when I uninstalled Visual Studio 2015 and its related components, like SSMS, and installed VS 2017 and newer version of SSMS (16.X).
What can I do to make SSMS not closing immediately after startup?
Step 1: Just delete this file:
C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\CommonExtensions\Platform\Microsoft.VisualStudio.MinShell.Interop.pkgdef
Alternatively, rename the file so it does not have the .pkgdef extension.
Step 2: Optionally, you can remove the following Windows Registry Key (created at SSMS 18 startup using the .pkgdef file mentioned above):
HKEY_CURRENT_USER\SOFTWARE\Microsoft\SQL Server Management Studio\18.0_IsoShell_Config\RuntimeConfiguration\dependentAssembly\bindingRedirection\{8BC7AF31-B6DA-4B97-8B36-F0500DECB147}
I had this same problem running SQL Server 2017 on Windows Server 2012 R2.
• After installing SSMS 18.0 General Availability release (GA), when started, it always closed immediately.
• So I installed Visual Studio 2019 Community Edition with the Data storage and Processing workload and somehow SSMS 18.0 (GA) ran fine without closing, but just once. The next times I tried to start SSMS 18.0 (GA) again, it always closed immediately.
• Having lost my trust on this GA release, I decided to uninstall it and try with a previous release.
• Using the Chocolatey package manager for Windows https://chocolatey.org/packages/sql-server-management-studio I installed SSMS v17.8.1 and everything is working fine now.
Can't believe, that the only solution was to install VS 2015 again. So I use VS 2017 in everyday work, but I must have VS 2015 installed as well, just to make SSMS work...
I took a look at this. Problem seems to be with SMSS installing Microsoft Visual C++ 2017 Redistributable. When that happens, Microsoft Visual C++ 2015 gets uninstalled. However, if you look at the System Requirements at this page:
Microsoft Visual Studio Tools for Applications 2017
you'll see that Microsoft Visual Studio Tools for Applications 2017, which is also installed by SMSS v18.0, requires Microsoft Visual C++ 2015 Redistributable.
So, it seems the crash is caused by Microsoft Visual Studio Tools for Applications 2017 when it tries to find Microsoft Visual C++ 2015 Redistributable and can't since Visual C++ 2017 Redistributable removed it.
Don't bother trying to install Microsoft Visual C++ 2015 Redistributable if 2017 is already there. Installer for 2015 won't do the install if it sees 2017 is already there. Uninstalling 2017 so 2015 will install works, but then, when you reinstall 2017, 2015 is removed.
I guess stay on SMSS v17.9.1 for now.
According to this article SMSS Immediately closes (a load of work....), it should work again:
1) Uninstalled Visual Studio 2015 with VisualStudioUninstaller (thanks Andrea)
2) Uninstalled Visual Studio 2017 (above uninstaller not help a lot for 2017)
3) Uninstalled Visual Studio 2015 Shell
4) Uninstalled all related SQL apps including (SSMSs).
4) Reinstalled Visual Studio 2017 and SSMS 16
SMS Release 18.0 has a repair option if you run the download. Try the repair option. It's new.
In my case, it was SqlServer Management Studio 18. and the solution was to
Copy the Microsoft.VisualStudio.Shell.Interop.8.0 file from
C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\PrivateAssemblies\Interop
and override the file in
C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\PublicAssemblies
"Setup Failed" Recursion too deep; stack overflowed 0x800703E9.
I have windows 10 and newest visual studio version. I have tried rebooting to make sure I have as many resources as possible. I have 4g ram.
If the SSDT installer gives you multiple instances of Visual Studio to choose from, try the "new" option.
I ran into this problem trying to install SSDT 15.8.1 on Windows Server 2012 R2 with the latest version of Visual Studio 2017 (v15.8.6) already installed. The SSDT installer gave me 2 options in a dropdown box.
Install tools to this Visual Studio 2017 instance:
Visual Studio 2017
Install new SQL Server Data Tools for Visual Studio 2017
When I chose the first option: Visual Studio 2017 (presumably the existing instance), I ran into the cryptic "recursion too deep" error. I installed the SSRS extension for VS (as suggested by others on Stack Overflow) and tried running the SSDT installer again for the existing Visual Studio 2017 instance. I got the same "recursion" error.
I tried one more time, but this time chose the 'Install new SQL Server Data Tools for Visual Studio 2017' option. This time the install process completed!
Apparently there is an installer inconsistency between the latest versions of SSDT and Visual Studio. The suggested fix is to start with a previous installation of Visual Studio 2017, install the latest SSDT on top of that, and then upgrade Visual Studio. This is a very time consuming fix. It appears this is only necessary for the SSIS components - the SSAS and SSRS pieces are available as Extensions within VS, and I believe they still install successfully from there.
https://developercommunity.visualstudio.com/content/problem/258117/ssdt-failed-to-install-vs-2017-pro-1572.html
Please re-run the VS community 2017 installer or go to Control Panel-Programs and Features, uninstall the previous SSDT version for VS 2017, then re-install it, you can have a look at this similar issue.
If this issue persists, please use http://aka.ms/vscollect to gather the installation logs and find vslogs.zip under the %temp% folder, then upload the file to Onedrive and share the link here.
You should uninstall the current version of SSDT before install a new version.
If your computer have some pages blocked, you could download the specific version offline installer (Download the header, then use SSDT-Setup.exe /layout [Folder]) for the former version and new version of SSDT.
How I got past it:
Uninstall the Visual Studio extensions for Reporting Services (and Analysis Services) projects in case if you going to select them during SSDT set up. Note: remember to run VS as administrator to do the uninstall.
Reboot VS2017 (just out of general principle.)
Trying to connect my Visual Studio Team Services server in SQL Data Tools 2010, but getting the following error, i have correctly installed the Microsoft Visual Studio Team Explorer 2010 - ISO
Visual Studio online currently only works with VS2013 and above. It's not support for SSDT2010. You may need to use SSDT in VS2013 and try again.
SSDT is available in VS 2013, it's integrated into the box so we do
not have a stand alone install. If you install VS 2013, you will see
the Database Projects, SQL Server Object Explorer, and other tools
that were available in VS 2010 & VS 2012. I have verified that the
Database Projects in VS2013 will work with VS Online source control,
however if you are using the online build process, we are not built
into the online build support yet.
Posted by Jill [MSFT] on 1/13/2014 at 2:36 PM
More detail info please refer this link: SSDT with VIsual Studio Online
I cam across this question here on SE:
Can Visual Studio 2012 be installed side-by-side w/ Visual Studio 2010?
According to one comment with a good amount of upvotes, having 2010 and 2012 installed at the same time can present issues. I then came across this MSDN page about 2013:
http://msdn.microsoft.com/en-us/library/hh266747.aspx
If you use Visual Studio 2013 together with Visual Studio 2012 or Visual Studio 2010 SP1, you can [blah blah]
That suggests that 2013 can be safely installed along with VS2012. Can anyone confirm?
Take a look at Brian Harry´s Blog post announcing Visual Studio 2013.
VS 2013 can be installed side by side with previous versions of Visual Studio or, if you have a VS 2013 pre-release, it can be installed straight over top of the pre-release. TFS 2013 cannot be installed side by side but can also be installed over top of either a previous version (TFS 2012 or TFS 2010) or a pre-release.
Looks like you can, yes.
You can install this version of Visual Studio on a computer that
already has an earlier version installed.
http://msdn.microsoft.com/en-us/library/ms246609%28v=vs.120%29.aspx
Only issue I can see is during uninstallation, where the file associations may get lost.
I was having two installation on my computer. Really no problems.
From personal experience, I've come across multiple issues with using Visual Studio 2012 and prior, while a VS2013 installation exists on a machine.
Some of the issues include built executables failing to launch (double clicking .exe does nothing, but debugging them in VS launches them), and inability to compile solutions that mix C# and C++ projects.
I would avoid 2013 until these issues are resolved, as just having it installed on a machine breaks older code, even if you don't use VS2013.
There are some minor (compatibility) issues between using both VS2010 and VS2012 on the same Solution, but simply having VS2012 installed on your machine won't effect anything in VS2010.
There may be compatibility issues with 2013 Community edition. I had VS 2012 Ultimate and VS 2013 Express installed and working without any issue, but as soon as I installed VS 2013 Community, my VS 2012 Ultimate install has been behaving unusually. When I first open VS 2012 U, there is a really long load time. When I perform some action (open a file, select a menu option, anything actually) I have to minimize and maximize VS 2012 U for the screen to refresh. I am still trying to figure it out myself - so if anyone has a solution, please share.