September 4, 2016 at 8:11 am
Hi Folks,
I have an installation of SQL Server 2016 CTP3 on my laptop, a Windows 10 machine, as a test environment. I have tried to install Integration Services but receive the following error:
Error installing Microsoft Visual C++ 2015 Redistributable
VS Shell installation has failed with exit code 1638.
When I view the error log I see the following lines:
[0270:1ED0][2016-09-04T15:57:27]i052: Condition 'VersionNT64 >= v6.0 OR (VersionNT64 = v5.2 AND ServicePackLevel >= 1)' evaluates to true.
[0270:1ED0][2016-09-04T15:57:27]i199: Detect complete, result: 0x0
[0270:1BB8][2016-09-04T15:57:27]e000: Error 0x80070666: Cannot install a product when a newer version is installed.
[0270:1ED0][2016-09-04T15:57:27]i500: Shutting down, exit code: 0x666
I have Visual Studio 2015 installed and SSDT 2015 and wonder if that could be the problem but if so, how can I resolve the issue.
The one thing I can think of is removing the C++ Redistributable but I can only imagine something will break......
Looking forward to your answers!
Regards
Kev
September 4, 2016 at 8:26 am
Quick suggestion, update the VS to the latest release before the installation, had similar/same problem on one of my workstations and after updating the VS with all the things applicable everything went fine.
😎
September 4, 2016 at 10:49 pm
Is there is reason that you need to be using CTP3? SQL Server 2016 Develop Edition is available and is free (and fully supported by MS)
April 25, 2017 at 12:55 pm
I find it a bit odd that the error occurs when the version is higher than the one being installed. Namely "VS Shell installation has failed with exit code 1638." Does the Microsoft SQL Server bug team handle this or is it a precaution? The long and short of it is that there is a message at the end of the installation that indicates Client Tools, SDK, Client Tools Backwards Compatibility, and Integration Services "Failed" to install. I did not see this error on machines where I installed SQL Server 2016 BEFORE the SSMS 2016 tool was installed. My guess would be this is a bug in SSMS 2016. The primary tool, SSMS installs without any issue. But the Integration Services (version 13) cannot install. In some way, this is actually a good thing because our DEV team is still using Visual Studio 2013 and Visual Studio 2015 is required for Integration Services compatibility with an upgraded Integration Services (version 13). I find the failure a bit unnerving. I'm still wondering how it can effect tools from the future that may be required. For example, can I install Integration Services 13 once our DEV team upgrades to VS 2015.
Jamie
April 26, 2017 at 8:17 am
NOTE: 7 MONTH OLD THREAD!
If anyone tried to install SQL2016 CTP3 today they will not get a working system due to the CTP expiration date
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply