I am having problem with installation of SSDT 2012. Problem:
VS shell 2012 has failed with exit code -2147205120
There are a few possible causes. See if any of these solutions help.
Install VS 2012 Update 4 first (or the latest update for VS 2012).
If .NET Framework 4.5 is not yet installed then install it manually before SSDT.
Install these before SSDT: Visual Studio Tools for Applications 2012, Visual Studio 2012 Shell Isolated
Check the amount of free space left on the hard drive.
Check the SSDT system requirements.
Related
I have received the following error while installing MSSQL 2017 on Windows 2012 R2.
vs shell installation has failed with exit code 1638
You must install SQL Server first before installing Visual Studio 2017.
If you have already installed Visual Studio 2017, do not worry, just follow the steps below:
Uninstall the Microsoft Visual C++ 2017 Redistributable (x86) and (x64)
Then install SQL Server.
Do not forget to select "Database Engine Services"
Change "Startup Type" of SQL Server Browser from "Disabled" to "Automatic"
The installation will be done without any problems:
Then reinstall the Microsoft Visual C++ 2017 Redistributable (x86) and (x64)
This Error means
1-Another version of this program is already installed
2-Visual Studio 2017 Is In Installing Level And Not Complete
3-Visual Studio 2017 installed (Not For All)
If You Have Other Version . Remove Or Update The SSMS.
If Your Visual Studio In Installing Level. Wait To Complete And Then Try To Setup
Else
To fix the issue, use the following workarounds:
Repair the x64 version of Microsoft Visual C++ 2017 Redistributable from Add or remove programs by using following steps:
Open Add or remove programs.
Find and select Microsoft Visual C++ 2017 Redistributable (x64). Click the Change button.
Click the Repair button.
If you encounter this issue when installing TFS, you can start VC_redist.x64.exe from the TFS installation files, and then select repair.
Hope This Help You To Fix
Microsoft Support Article
Do you have Visual Studio 2017 installed in your computer? If so, try uninstalling it, then install SQL Server, and reinstall Visual Studio. I had the same problem today when installing MSSQL 2017, and solved it like that.
I read in some sites you can also try only uninstalling Microsoft Visual C++ 2017 Redistributable (86x) and (64x), but I didn't try this solution, so I'm not sure if it works. It's still worth a shot though, as it's easier than uninstalling the whole Visual Studio.
What are the differences between SSDT and SSDT- Business Intelligence?
I've installed SQL Server 2017 and then proceeded to download Business Intelligence Development Studio but found out that it was replaced by SSDT/SSDT-BI (don't know the difference if there's any).
Do I need just SSDT or SSDT-BI? I can only find SSDT-BI for Visual Studio 2012 and 2013, not for VS 2017 while SSDT for VS 2017 is available.
Will this create any problems since I'm working with SQL Server 2017?
I'm a complete beginner at all this and this is only for a uni project. Please keep answers as simple as possible. Thank you very much.
There is only SSDT nowadays, which includes support for SQL Server Database, SSRS, SSRS, and SSIS projects. The download links are here. The current SSDT version (15.5.2 as of this writing) allows you to target SQL Azure Database, SQL Server 2017, as well as older versions so you don't need multiple versions of SSDT installed.
SSDT will install a minimal Visual Studio shell if VS is not already installed. If you already have VS installed, those project types will be added to the existing installation.
EDIT:
With Visual Studio 2019, SSDT for SQL Server database projects remains intregrated into the VS 2019 installer. Select the Data Storage and processing workload during install and choose SQL Server Data Tools. However, SAS, SSIS, and SSRS SSDT projects are now moved to separate Visual Studio extensions. These extensions can be manged post install from within Visual Studio under Extensions-->Manage Exentsions.
Yeah, this got a lot of people confused. According to this link (VS2012 & VS2013 timeframe):
SSDT is for building databases ONLY i.e. only base functionality.
SSDT-BI is for building SSIS/SSAS/SSRS solutions
But then it looks like from VS2015 onward they merged the two together into just SSDT, so after VS2013 there is no separate SSDT-BI install. I think.
I am trying to install SQL Server 2017 Express on Windows 10 and it is failing.
Here is the details it shows me after failure:
Action required:
Use the following information to resolve the error, and then try the setup process again.
Feature failure reason:
An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Error details:
§ Error installing Microsoft Visual C++ 2015 Redistributable
VS Shell installation has failed with exit code 1638.
Error code: 1638
Log file: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20171018_083459\VCRuntime140_x64_Cpu64_1.log
Visithttps://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=VCRuntime140_x64%40Install%400x1638 to get help on troubleshooting.
I am Windows 10 and have Visual Studio 2017 installed.
I'm thinking the problem could be I installed SQL Server Management Studio 2017 before I installed SQL Server.
I have the same setup at home but I installed SQL Server first and then SSMS and everything works fine.
The other difference is at home in the installation dialog it says something the affect that C++ Redistribuble is already installed but at work where it is failing it says it is to be installed in hte list of components.
The problem is likely that there's a newer version of the Visual C++ Redistributable than SQL Server is trying to install, e.g., from Visual Studio 2017. So another way to address this, if you don't need the latest C++ redistributable, is to go to Add or Remove Programs and uninstall all references to Visual C++ 2017 Redistributable. After this, the SQL Server installation should proceed without errors.
I had this error before all I did was(using Win10 x64):
Go to control panel-> Select Programs -> Programs and Features -> Search "c++"
-> In the list select Visual C++ 2017(or your version error) Redistributable -> right click select "change" -> select repair.
After that I was able to continue and successfully installed SQL Server Express 2017.
Note:
Some requires uninstall and reinstall again therefore if the above procedure doesn't work just try reinstalling it.
I figured it out for my environment.
If you have Visual Studio 2017, go back into the installer and install the "ATL C++" workload. Now when you go through the SQL Server 2017 install it will say C++ already installed and the installation will be successful.
I got the solution :
remove VC++ 2017.
download VC++ 2015 from here
install VC++ 2015
install SQL Server 2017
install SSMS 2017
I also had this problem. I just repair the program Microsoft Visual C++ 2017 Redistributable (x86) - 14.16.27029 from Add Remove Program and setup run without any error.
I also found running the repair of the Microsoft Visual C++ redistributable corrected the issue and was able to install SQL 2017 RTM Cumulative Update (CU) 23 KB5000685
Uninstalling the following from Programme and Features option fixed my issue.
Microsoft Visual C++ 2015 Redistributable
MSSQL 2017 installation will automatically add it once the installation is completed.
First make sure you haven't installed SSMS before,
First install SQLSERVER then SSMS.
To resolve this error just uninstall MS visual C++ Redistributable v13/v15/v17 as they get installed already when you install SSMS before.
Run the setup again it will continue installation.
I have uninstalled Microsoft Visual Studio 2012 Ultimate and install VS professional 2013
after, i tried to Setup Sql Server 2014 but a message say
"Installation blocked due to detection of version of Visual Studio that install SQL Server 2012 client libraries.."
then i have uninstalled all Microsoft programs figured in this link without uninstalling visual studio 2013 .
and always i get the same problem
any solutions Please
At this point in time, you should be using CTP2, not CTP1.
You should be installing the CTP on a clean machine (preferably a VM), not a system with a bunch of pre-existing software - especially from previous versions of SQL Server / Visual Studio. CTP2 might get around this particular issue for you, but it's still best practice IMHO to run beta software in a clean environment.
Please review the release notes, in full, before proceeding.
I am rebuilding my development machine. This issue is not new to me, but I don't remember the solution.
I started with SQL 2008 Developer, then VS 2008 Pro, then the SQL SP1, then VS SP1. The result is that I cannot open SSIS projects (see the error below). What is the correct order so that I can avoid the installation of SQL Server Express and still have all the features working?
---------------------------
Microsoft Visual Studio
---------------------------
Package Load Failure
Package 'DataWarehouse VSIntegration layer' has failed to load properly ( GUID =
{4A0C6509-BF90-43DA-ABEE-0ABA3A8527F1} ). Please contact package vendor for
assistance. Application restart is recommended, due to possible environment
corruption. Would you like to disable loading this package in the future? You
may use 'devenv /resetskippkgs' to re-enable package loading.
---------------------------
Yes No
---------------------------
You should install SQL 2008 Developer first, this will rule out the need for VS installing SQL which comes with it. Or you could do like others suggested and choose custom VS installation.
My favorite way is this:
SQL 2008 Developer
Visual Studio Professional 2008
Run Windows Updates
Install Resharper :-)
Install RedGate SQL ToolBelt
But it seems that to get some features to work the proper order is:
Visual Studio Professional 2008 (with SQL Unchecked)
SQL 2008 Developer
Run Windows Updates
Install Resharper/Redgate Tools
Resharper and Redgate in my opinion are far the best tools for developing in C#/SQL.
It turns out I was missing 2 important pieces of information in my question that make this installation such a pain:
I was installing the 64 bit version of SQL Server
I was installing to a non-standard location (i.e. the D: drive, because C: is an SSD with not all
that much space)
This was not successful. Here is what I ended up doing in my first (second, and third) attempt:
Install VS 2008 Professional on D:
Install VS 2008 SP 1
Install SQL Server 2008 Developer Edition (instance and shared components on D:)
Install SQL Server SP 1
Apparently VS 2008 Pro does not require a database. I am not sure why I remembered that it does. While the Visual Studio installation was eventless, I encountered the following errors during the SQL Server installation:
The INSTANCESHAREDWOWDIR command line value was not specified.
I was able to resolve that be starting setup from the command line (thanks to this MSDN forum post):
setup.exe /INSTALLSHAREDWOWDIR="D:\Program Files(x86)\Microsoft SQL
Server" /INSTALLSHAREDDIR="D:\Program Files\Microsoft SQL Server"
/ACTION=install
Then towards the end of the installation, I got this error:
Upgrade Failed due to the following Error.The error code is :-2147467259.Message:Unspecified error
There is no solution, but a workaround, described in this post on connect.microsoft.com. It consists of copying a VS config file around before and after the installation, and re-running the installer just for BIDS (which is the one component that failed).
The SQL Server SP1 installation ran without issue. VS Studio, when trying to load a solution with an SSIS project, still threw the error that I posted in my original question.
I had ignored this error that popped up towards the end of the BIDS installation:
Microsoft Visual Studio Tools for Applications 2.0
Cannot find one or more components. Please reinstall the application.
However, there was no error in the install log and it completed "successfully", so I thought it would be ok to ignore the error.
It seems that my configuration is not possible (but I know with certainty that I had the 2005 versions of VS and SQL Server on a D: drive).
I uninstalled everything once again, manually deleted whatever folders were left, and reinstalled on the C: drive, including the SQL Server shared components. I put the instance folder on the D:.
Install VS 2008 Professional on C:
Install VS 2008 SP 1
Install SQL Server 2008 Developer Edition (instance on D:, shared components on C:)
Install SQL Server SP 1
This time everything installed and I can open my SSIS project.
If you are trying to install SQL-2008 and you also have visual studio 2008 installed with service pack one (SP1) and get the error
A previous release of Microsoft Visual Studio 2008 is installed on
this computer. Upgrade Microsoft Visual Studio 2008 to the SP1 before
installing SQL Server 2008”
Then welcome to the Microsoft beta testing program even if you purchased the faulty software.
With XP the most common solution seem to be renaming the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DevDiv\VS\Servicing\9.0
and replacing 9.0 with 9.0Old. However this does not solve the problem if you are using windows 7 and the only solution I managed to find that worked was to uninstall VS2008 and all the components and to then install SQL-2008 and finally reinstall VS2008.
Install Visual Studio Professional 2008.
Install SQL 2008 Developer
Apply SQL SP1
Apply VS SP1
Then all should be good.