Ошибка установки sql server 1638

SQL Server 2017 Developer on Windows SQL Server 2017 Enterprise on Windows SQL Server 2017 Enterprise Core on Windows SQL Server 2017 Standard on Windows SQL Server 2016 Еще…Меньше

Проблемы

Предположим, Microsoft Visual C++ 2015 redistributable установлен на сервере. При попытке установить на сервере более раннюю версию выводится следующее сообщение об ошибке:

Компонент: ядро СУБД Services
Состояние: сбой
Причина сбоя: произошла ошибка зависимости компонента, которая приводила к сбою процесса установки компонента.
Следующий шаг. Используйте следующие сведения, чтобы устранить ошибку, а затем повторите попытку установки.
Имя компонента: Microsoft Visual C++ 2015
Код ошибки компонента: 1638
Файл журнала компонентов: FilePathVCRuntime140_x64_Cpu64_1.log
Описание ошибки: сбой установки VS Shell с кодом выхода 1638.
Ссылка на справку по ошибке: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=VCRuntime140_x64%40Install%400×1638

Решение

Эта проблема устранена в следующих накопительных обновлениях для SQL Server:

Накопительный пакет обновления 13 для SQL Server 2017

Накопительный пакет обновления 16 для SQL Server 2016 с пакетом обновления 2 (SP2)

Обходное решение

Чтобы устранить эту проблему, воспользуйтесь следующими обходными путями:

  • Исправьте 64-разрядную версию распространяемого компонента Microsoft Visual C++ 2015 с помощью функции Установка и удаление программ, выполнив следующие шаги:

    1. Откройте компонент Установка и удаление программ.

    2. Найдите Распространяемый пакет Microsoft Visual C++ 2015 (x64) и выберите его. Нажмите кнопку Изменить.

    3. Нажмите кнопку Исправить.

  • Если данная проблема возникнет при установке TFS, можно запустить файл VC_redist.x64.exe из файлов установки TFS, а затем выбрать Исправить.

  • Воспользуйтесь обходными путями в следующих документах:

    • SQL SERVER — исправление: ошибка — сбой установки оболочки VS с кодом выхода 1638

    • Справка по установке SQL Server 2017 — сбой установки VS Shell с кодом выхода 1638

Нужна дополнительная помощь?

Нужны дополнительные параметры?

Изучите преимущества подписки, просмотрите учебные курсы, узнайте, как защитить свое устройство и т. д.

В сообществах можно задавать вопросы и отвечать на них, отправлять отзывы и консультироваться с экспертами разных профилей.

Источник

I have received the following error while installing MSSQL 2017 on Windows 2012 R2.

vs shell installation has failed with exit code 1638

enter image description here

asked May 25, 2018 at 8:59

Hiren Parghi's user avatar

Hiren ParghiHiren Parghi

1,7951 gold badge20 silver badges30 bronze badges

2

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)

enter image description here

Then install SQL Server.

Do not forget to select «Database Engine Services«

enter image description here

Change «Startup Type» of SQL Server Browser from «Disabled» to «Automatic«

enter image description here

The installation will be done without any problems:

enter image description here

Then reinstall the Microsoft Visual C++ 2017 Redistributable (x86) and (x64)

answered Aug 7, 2018 at 17:52

Husam Ebish's user avatar

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

answered Nov 28, 2018 at 8:21

Mahmoud Valizadeh's user avatar

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.

answered Jul 2, 2018 at 3:23

Jaqueline's user avatar

1

Источник
  • Remove From My Forums

  • Question

  • Detail:

    (01) 2017-10-19 02:14:41 Slp: Log provider ‘Microsoft.SqlServer.Chainer.Infrastructure.LogProviderFile’ has been registered
    (01) 2017-10-19 02:14:41 Slp: Log provider ‘Microsoft.SqlServer.Chainer.Infrastructure.LogProviderConsole’ has been registered
    (01) 2017-10-19 02:14:41 Slp: Log provider ‘Microsoft.SqlServer.Chainer.Infrastructure.LogProviderStatus’ has been registered
    (01) 2017-10-19 02:14:41 Slp: Reading XML resource ‘Microsoft.SQL.Chainer.PackageData.Package.xml’
    (01) 2017-10-19 02:14:41 Slp: Reading schema resource ‘Microsoft.SQL.Chainer.Package.Package.xsd’
    (01) 2017-10-19 02:14:41 Slp: Document ‘Microsoft.SQL.Chainer.PackageData.Package.xml’ validated with schema ‘Microsoft.SQL.Chainer.Package.Package.xsd’ has been successfuly loaded into datastore path ‘/Datastore/Package’
    (01) 2017-10-19 02:14:41 Slp: ———————————————————————-
    (01) 2017-10-19 02:14:41 Slp: Running Action: ReadProductXML
    (01) 2017-10-19 02:14:41 Slp: Reading XML resource ‘Microsoft.SQL.Chainer.Product.Product.xml’
    (01) 2017-10-19 02:14:41 Slp: Document ‘Microsoft.SQL.Chainer.Product.Product.xml’ validated with schema ‘Microsoft.SQL.Chainer.Product.Product.xsd’ has been successfuly loaded into datastore path ‘/Datastore/Product’
    (01) 2017-10-19 02:14:41 Slp: Completed Action: ReadProductXML, returned True
    (01) 2017-10-19 02:14:41 Slp: ———————————————————————-
    (01) 2017-10-19 02:14:41 Slp: Running Action: LoadExtensions
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘MSI’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.MsiExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘MSI’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘Config’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.ConfigExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘Config’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘Common’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Chainer.ExtensionCommon.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘Common’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘SqlConfigBase’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.SqlConfigBase.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘SqlConfigBase’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘Slp’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.SetupExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘Slp’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘RulesEngine’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.RulesEngineExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘RulesEngine’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘WorkflowData’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Chainer.WorkflowData.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘WorkflowData’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘SlpConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.SlpExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘SlpConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘Clst’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.Cluster.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘Clst’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘AgentConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.AgentExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘AgentConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘SqlPowershellConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.PowershellExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘SqlPowershellConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘SSISConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.SSISExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘SSISConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘ISMasterConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.ISMasterExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘ISMasterConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘ISWorkerConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.ISWorkerExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘ISWorkerConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘DReplayConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.DistributedReplayExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘DReplayConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘ASConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.ASExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘ASConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘ReplConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.Repl_ConfigExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘ReplConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘ManagementToolsConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.ManagementToolsExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘ManagementToolsConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘ManagementToolsAdvancedConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.ManagementToolsExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘ManagementToolsAdvancedConfig’ version ‘14.0.1000.169’ loaded

    • Moved by

      Thursday, October 19, 2017 2:31 AM

Источник

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 FilesMicrosoft SQL Server140Setup BootstrapLog20171018_083459VCRuntime140_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.

asked Oct 18, 2017 at 12:46

Sam's user avatar

1

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.

answered Oct 25, 2017 at 17:42

Luc Reid's user avatar

Luc ReidLuc Reid

2912 silver badges3 bronze badges

2

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.

answered Mar 24, 2018 at 5:57

babidi's user avatar

babidibabidi

5065 silver badges6 bronze badges

2

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.

answered Oct 18, 2017 at 13:54

Sam's user avatar

SamSam

4,63111 gold badges47 silver badges76 bronze badges

1

I got the solution :

  1. remove VC++ 2017.
  2. download VC++ 2015 from here
  3. install VC++ 2015
  4. install SQL Server 2017
  5. install SSMS 2017

Karsten Koop's user avatar

Karsten Koop

2,4751 gold badge17 silver badges23 bronze badges

answered Dec 7, 2018 at 11:36

G A's user avatar

1

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.

answered Jun 26, 2019 at 8:30

Shaiwal Tripathi's user avatar

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

answered Mar 17, 2021 at 10:52

Shaun Bell's user avatar

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.

answered Mar 7, 2018 at 0:39

Hiren Parghi's user avatar

Hiren ParghiHiren Parghi

1,7951 gold badge20 silver badges30 bronze badges

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.

answered Jun 28, 2018 at 4:50

Waqas Tahir's user avatar

Источник

SQL Server 2017 Developer on Windows SQL Server 2017 Enterprise on Windows SQL Server 2017 Enterprise Core on Windows SQL Server 2017 Standard on Windows SQL Server 2016 Еще…Меньше

Проблемы

Предположим, Microsoft Visual C++ 2015 redistributable установлен на сервере. При попытке установить на сервере более раннюю версию выводится следующее сообщение об ошибке:

Компонент: ядро СУБД Services
Состояние: сбой
Причина сбоя: произошла ошибка зависимости компонента, которая приводила к сбою процесса установки компонента.
Следующий шаг. Используйте следующие сведения, чтобы устранить ошибку, а затем повторите попытку установки.
Имя компонента: Microsoft Visual C++ 2015
Код ошибки компонента: 1638
Файл журнала компонентов: FilePathVCRuntime140_x64_Cpu64_1.log
Описание ошибки: сбой установки VS Shell с кодом выхода 1638.
Ссылка на справку по ошибке: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=VCRuntime140_x64%40Install%400×1638

Решение

Эта проблема устранена в следующих накопительных обновлениях для SQL Server:

Накопительный пакет обновления 13 для SQL Server 2017

Накопительный пакет обновления 16 для SQL Server 2016 с пакетом обновления 2 (SP2)

Обходное решение

Чтобы устранить эту проблему, воспользуйтесь следующими обходными путями:

  • Исправьте 64-разрядную версию распространяемого компонента Microsoft Visual C++ 2015 с помощью функции Установка и удаление программ, выполнив следующие шаги:

    1. Откройте компонент Установка и удаление программ.

    2. Найдите Распространяемый пакет Microsoft Visual C++ 2015 (x64) и выберите его. Нажмите кнопку Изменить.

    3. Нажмите кнопку Исправить.

  • Если данная проблема возникнет при установке TFS, можно запустить файл VC_redist.x64.exe из файлов установки TFS, а затем выбрать Исправить.

  • Воспользуйтесь обходными путями в следующих документах:

    • SQL SERVER — исправление: ошибка — сбой установки оболочки VS с кодом выхода 1638

    • Справка по установке SQL Server 2017 — сбой установки VS Shell с кодом выхода 1638

Нужна дополнительная помощь?

Any suggestions on how to deal with this error:

TITLE: Microsoft SQL Server 2017 Setup
------------------------------

The following error has occurred:

VS Shell installation has failed with exit code 1638.

For help, click: https://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0x5B39C8B9%25401434%25403

------------------------------
BUTTONS:

OK
------------------------------

This is a new laptop running

  • SQL Server 2016 express
  • Visual Studio 2017
  • SSMS 2017

I tried uninstalling anything related to SQL Server or Visual Studio.

Log: [3500:3970][2017-11-03T16:25:20]e000: Error 0x80070666: Cannot install a product when a newer version is installed.

Detailed results:
  Feature:                       Full-Text and Semantic Extractions for Search
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                Microsoft Visual C++ 2015 Redistributable
  Component error code:          1638
  Component log file:            C:Program FilesMicrosoft SQL Server140Setup BootstrapLog20171103_162358VCRuntime140_x64_Cpu64_1.log
  Error description:             VS Shell installation has failed with exit code 1638.
  Error help link:               https://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

  Feature:                       Database Engine Services
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                Microsoft Visual C++ 2015 Redistributable
  Component error code:          1638
  Component log file:            C:Program FilesMicrosoft SQL Server140Setup BootstrapLog20171103_162358VCRuntime140_x64_Cpu64_1.log
  Error description:             VS Shell installation has failed with exit code 1638.
  Error help link:               https://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

Any suggestions on how to deal with this error:

TITLE: Microsoft SQL Server 2017 Setup
------------------------------

The following error has occurred:

VS Shell installation has failed with exit code 1638.

For help, click: https://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0x5B39C8B9%25401434%25403

------------------------------
BUTTONS:

OK
------------------------------

This is a new laptop running

  • SQL Server 2016 express
  • Visual Studio 2017
  • SSMS 2017

I tried uninstalling anything related to SQL Server or Visual Studio.

Log: [3500:3970][2017-11-03T16:25:20]e000: Error 0x80070666: Cannot install a product when a newer version is installed.

Detailed results:
  Feature:                       Full-Text and Semantic Extractions for Search
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                Microsoft Visual C++ 2015 Redistributable
  Component error code:          1638
  Component log file:            C:Program FilesMicrosoft SQL Server140Setup BootstrapLog20171103_162358VCRuntime140_x64_Cpu64_1.log
  Error description:             VS Shell installation has failed with exit code 1638.
  Error help link:               https://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

  Feature:                       Database Engine Services
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                Microsoft Visual C++ 2015 Redistributable
  Component error code:          1638
  Component log file:            C:Program FilesMicrosoft SQL Server140Setup BootstrapLog20171103_162358VCRuntime140_x64_Cpu64_1.log
  Error description:             VS Shell installation has failed with exit code 1638.
  Error help link:               https://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

Any suggestions on how to deal with this error:

TITLE: Microsoft SQL Server 2017 Setup
------------------------------

The following error has occurred:

VS Shell installation has failed with exit code 1638.

For help, click: https://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0x5B39C8B9%25401434%25403

------------------------------
BUTTONS:

OK
------------------------------

This is a new laptop running

  • SQL Server 2016 express
  • Visual Studio 2017
  • SSMS 2017

I tried uninstalling anything related to SQL Server or Visual Studio.

Log: [3500:3970][2017-11-03T16:25:20]e000: Error 0x80070666: Cannot install a product when a newer version is installed.

Detailed results:
  Feature:                       Full-Text and Semantic Extractions for Search
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                Microsoft Visual C++ 2015 Redistributable
  Component error code:          1638
  Component log file:            C:Program FilesMicrosoft SQL Server140Setup BootstrapLog20171103_162358VCRuntime140_x64_Cpu64_1.log
  Error description:             VS Shell installation has failed with exit code 1638.
  Error help link:               https://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

  Feature:                       Database Engine Services
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                Microsoft Visual C++ 2015 Redistributable
  Component error code:          1638
  Component log file:            C:Program FilesMicrosoft SQL Server140Setup BootstrapLog20171103_162358VCRuntime140_x64_Cpu64_1.log
  Error description:             VS Shell installation has failed with exit code 1638.
  Error help link:               https://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
  • Remove From My Forums

  • Question

  • Detail:

    (01) 2017-10-19 02:14:41 Slp: Log provider ‘Microsoft.SqlServer.Chainer.Infrastructure.LogProviderFile’ has been registered
    (01) 2017-10-19 02:14:41 Slp: Log provider ‘Microsoft.SqlServer.Chainer.Infrastructure.LogProviderConsole’ has been registered
    (01) 2017-10-19 02:14:41 Slp: Log provider ‘Microsoft.SqlServer.Chainer.Infrastructure.LogProviderStatus’ has been registered
    (01) 2017-10-19 02:14:41 Slp: Reading XML resource ‘Microsoft.SQL.Chainer.PackageData.Package.xml’
    (01) 2017-10-19 02:14:41 Slp: Reading schema resource ‘Microsoft.SQL.Chainer.Package.Package.xsd’
    (01) 2017-10-19 02:14:41 Slp: Document ‘Microsoft.SQL.Chainer.PackageData.Package.xml’ validated with schema ‘Microsoft.SQL.Chainer.Package.Package.xsd’ has been successfuly loaded into datastore path ‘/Datastore/Package’
    (01) 2017-10-19 02:14:41 Slp: ———————————————————————-
    (01) 2017-10-19 02:14:41 Slp: Running Action: ReadProductXML
    (01) 2017-10-19 02:14:41 Slp: Reading XML resource ‘Microsoft.SQL.Chainer.Product.Product.xml’
    (01) 2017-10-19 02:14:41 Slp: Document ‘Microsoft.SQL.Chainer.Product.Product.xml’ validated with schema ‘Microsoft.SQL.Chainer.Product.Product.xsd’ has been successfuly loaded into datastore path ‘/Datastore/Product’
    (01) 2017-10-19 02:14:41 Slp: Completed Action: ReadProductXML, returned True
    (01) 2017-10-19 02:14:41 Slp: ———————————————————————-
    (01) 2017-10-19 02:14:41 Slp: Running Action: LoadExtensions
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘MSI’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.MsiExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘MSI’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘Config’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.ConfigExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘Config’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘Common’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Chainer.ExtensionCommon.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘Common’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘SqlConfigBase’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.SqlConfigBase.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘SqlConfigBase’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘Slp’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.SetupExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘Slp’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘RulesEngine’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.RulesEngineExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘RulesEngine’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘WorkflowData’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Chainer.WorkflowData.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘WorkflowData’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘SlpConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.SlpExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘SlpConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘Clst’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.Cluster.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘Clst’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘AgentConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.AgentExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘AgentConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘SqlPowershellConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.PowershellExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘SqlPowershellConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘SSISConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.SSISExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘SSISConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘ISMasterConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.ISMasterExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘ISMasterConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘ISWorkerConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.ISWorkerExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘ISWorkerConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘DReplayConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.DistributedReplayExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘DReplayConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘ASConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.ASExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘ASConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘ReplConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.Repl_ConfigExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘ReplConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘ManagementToolsConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.ManagementToolsExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘ManagementToolsConfig’ version ‘14.0.1000.169’ loaded
    (01) 2017-10-19 02:14:42 Slp: Loading extension ‘ManagementToolsAdvancedConfig’ from file ‘C:Program FilesMicrosoft SQL Server140Setup BootstrapSQL2017x64.Microsoft.SqlServer.Configuration.ManagementToolsExtension.dll’
    (01) 2017-10-19 02:14:42 Slp: Extension ‘ManagementToolsAdvancedConfig’ version ‘14.0.1000.169’ loaded

    • Moved by

      Thursday, October 19, 2017 2:31 AM

I have received the following error while installing MSSQL 2017 on Windows 2012 R2.

vs shell installation has failed with exit code 1638

enter image description here

asked May 25, 2018 at 8:59

Hiren Parghi's user avatar

Hiren ParghiHiren Parghi

1,7531 gold badge19 silver badges29 bronze badges

2

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)

enter image description here

Then install SQL Server.

Do not forget to select «Database Engine Services«

enter image description here

Change «Startup Type» of SQL Server Browser from «Disabled» to «Automatic«

enter image description here

The installation will be done without any problems:

enter image description here

Then reinstall the Microsoft Visual C++ 2017 Redistributable (x86) and (x64)

answered Aug 7, 2018 at 17:52

Husam Ebish's user avatar

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

answered Nov 28, 2018 at 8:21

Mahmoud Valizadeh's user avatar

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.

answered Jul 2, 2018 at 3:23

Jaqueline's user avatar

1

This post provides a fix suggestion for the error message “VS Shell Installation has Failed with Exit Code 1638“, when trying to install SQL Server 2016 features on a Windows Server.

When you Might Get this Error?

You might get the “VS Shell Installation has Failed with Exit Code 1638” error message when trying to install specific SQL Server 2016 features on a Windows Server.

For example, you might get this error, when trying to install SQL Server Integration Services (SSIS) on a Windows Server.

Why you Might Get this Error?

The reason for getting this error is because, certain SQL Server 2016 features, in our example SSIS, have as a prerequisite “Visual C++ Redistributable for Visual Studio 2015”.

So, if you don’t have these redistributables (x86 and/or x64) on the specific server, that’s why you get the “VS Shell Installation has Failed with Exit Code 1638” error message.

How to Resolve the Issue

The above issue, can be easily resolved, by installing “Visual C++ Redistributable for Visual Studio 2015” (you can get it from here).

If however you already have a higher version of the Visual C++ Redistributable installed, for example Visual C++ Redistributable for Visual Studio 2017, you will have to uninstall this first in order to be able to install the 2015 version and after that, you can re-install the 2017 version as well.

So the workflow for fixing the specific issue would be:

  1. Uninstall Visual C++ Redistributable for Visual Studio 2017 (if installed)
  2. Install Visual C++ Redistributable for Visual Studio 2015 (x86 and/or x64 or both – you can get it from here)
  3. Re-install Visual C++ Redistributable for Visual Studio 2017 (if was installed in the first place – you can get it from here)
  4. Try again to install the SQL Server 2016 feature that you are trying to install

Note: Under certain circumstances, a restart might be required.

Strengthen your SQL Server Administration Skills – Enroll to our Online Course!

Check our online course on Udemy titled “Essential SQL Server Administration Tips” (special limited-time discount included in link).

Via the course, you will learn essential hands-on SQL Server Administration tips on SQL Server maintenance, security, performance, integration, error handling and more. Many live demonstrations and downloadable resources included!

Essential SQL Server Administration Tips - Online Course with Live Demonstrations and Hands-on Guides

(Lifetime Access/ Live Demos / Downloadable Resources and more!)

Enroll from $12.99

Featured Online Courses:

  • Boost SQL Server Database Performance with In-Memory OLTP 
  • Essential SQL Server Administration Tips
  • SQL Server Fundamentals – SQL Database for Beginners
  • Essential SQL Server Development Tips for SQL Developers
  • Introduction to Computer Programming for Beginners
  • .NET Programming for Beginners – Windows Forms with C#
  • Introduction to SQL Server Machine Learning Services
  • Introduction to Azure SQL Database for Beginners
  • SQL Server 2019: What’s New – New and Enhanced Features
  • Entity Framework: Getting Started – Complete Beginners Guide
  • How to Import and Export Data in SQL Server Databases
  • Learn How to Install and Start Using SQL Server in 30 Mins
  • A Guide on How to Start and Monetize a Successful Blog

Read Also:

  • SQL Server Installation and Setup Best Practices
  • The TempDB System Database in SQL Server
  • Where are temporary tables stored in SQL Server?
  • SQL Server 2016: TempDB Enhancements
  • tempdb growth
  • Introduction to SQL Server Machine Learning Services
  • Essential SQL Server Administration Tips
  • …more

Subscribe to our newsletter and stay up to date!

Subscribe to our YouTube channel (SQLNetHub TV)

Easily generate snippets with Snippets Generator!

Secure your databases using DBA Security Advisor!

Generate dynamic T-SQL scripts with Dynamic SQL Generator!

Check our latest software releases!

Check our eBooks!

Rate this article: 1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 5.00 out of 5)

Loading…

Reference: SQLNetHub.com (https://www.sqlnethub.com)

© SQLNetHub

Artemakis Artemiou

Artemakis Artemiou is a Senior SQL Server Architect, Author, a 9 Times Microsoft Data Platform MVP (2009-2018). He has over 20 years of experience in the IT industry in various roles. Artemakis is the founder of SQLNetHub and {essentialDevTips.com}. Artemakis is the creator of the well-known software tools Snippets Generator and DBA Security Advisor. Also, he is the author of many eBooks on SQL Server. Artemakis currently serves as the President of the Cyprus .NET User Group (CDNUG) and the International .NET Association Country Leader for Cyprus (INETA). Moreover, Artemakis teaches on Udemy, you can check his courses here.

Views: 7,532

Home
> SQL Errors, SQL Server, SQL Server 2017 > SQL Server 2017 Setup error – VS Shell installation has failed with exit code 1638

 
Today while installing SQL Server 2017 on my PC I got this popup on the Installation Progress tab. Earlier I had installed SQL Server 2017 but had to uninstall it for some reason. Now today while re-installing it I was getting this error.

TITLE: Microsoft SQL Server 2017 Setup
——————————
The following error has occurred:

VS Shell installation has failed with exit code 1638.

——————————
BUTTONS: OK
——————————

… and once you click OK, the installation resumes, but ends in error again, with following error details:

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 FilesMicrosoft SQL Server140Setup BootstrapLog20180824_225215VCRuntime140_x64_Cpu64_1.log
Visit https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000 &ProdVer=14.0.1000.169&EvtType=VCRuntime140_x64%40Install%400×1638 to get help on troubleshooting.

Resolution:

– As per the second error, the SQL Server setup tries to install Microsoft Visual C++ 2015 Redistributable, but as I already have Visual Studio 2017 installed, thus it is failing to install a previous version of VC++, so you need to:
   1. Uninstall Visual Studio 2017.
   2. Install SQL Server 2017
   3. Install Visual Studio 2017 back again.

– Or, rather than uninstalling whole VS 2017, you can simply:
   1. Uninstall the VC++ 2017 Redistributable
   2. Install SQL Server 2017
   3. Install the VC++ 2017 Redistributable (download: x86, x64)

 

Artemakis Artemiou is a Senior SQL Server Architect, Author, a 9 Times Microsoft Data Platform MVP (2009-2018). He has over 20 years of experience in the IT industry in various roles. Artemakis is the founder of SQLNetHub and {essentialDevTips.com}. Artemakis is the creator of the well-known software tools Snippets Generator and DBA Security Advisor. Also, he is the author of many eBooks on SQL Server. Artemakis currently serves as the President of the Cyprus .NET User Group (CDNUG) and the International .NET Association Country Leader for Cyprus (INETA). Moreover, Artemakis teaches on Udemy, you can check his courses here.

Views: 7,532

Home
> SQL Errors, SQL Server, SQL Server 2017 > SQL Server 2017 Setup error – VS Shell installation has failed with exit code 1638

 
Today while installing SQL Server 2017 on my PC I got this popup on the Installation Progress tab. Earlier I had installed SQL Server 2017 but had to uninstall it for some reason. Now today while re-installing it I was getting this error.

TITLE: Microsoft SQL Server 2017 Setup
——————————
The following error has occurred:

VS Shell installation has failed with exit code 1638.

——————————
BUTTONS: OK
——————————

… and once you click OK, the installation resumes, but ends in error again, with following error details:

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 FilesMicrosoft SQL Server140Setup BootstrapLog20180824_225215VCRuntime140_x64_Cpu64_1.log
Visit https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000 &ProdVer=14.0.1000.169&EvtType=VCRuntime140_x64%40Install%400×1638 to get help on troubleshooting.

Resolution:

– As per the second error, the SQL Server setup tries to install Microsoft Visual C++ 2015 Redistributable, but as I already have Visual Studio 2017 installed, thus it is failing to install a previous version of VC++, so you need to:
   1. Uninstall Visual Studio 2017.
   2. Install SQL Server 2017
   3. Install Visual Studio 2017 back again.

– Or, rather than uninstalling whole VS 2017, you can simply:
   1. Uninstall the VC++ 2017 Redistributable
   2. Install SQL Server 2017
   3. Install the VC++ 2017 Redistributable (download: x86, x64)

 

-> SQL Server 2016 installation failed with below error,

TITLE: Microsoft SQL Server 2016 Setup
——————————
The following error has occurred:
VS Shell installation has failed with exit code 1638.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.5026.0&EvtType=0x5B39C8B9%25401434%25403
——————————
BUTTONS:
OK
——————————

-> In my case, all components completed fine except Integration Services. Below was the error found during setup for Integration services,

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 FilesMicrosoft SQL Server130Setup BootstrapLog20191119_153017VCRuntime140_x64_Cpu64_1.log
Visit http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.5026.0&EvtType=VCRuntime140_x64%40Install%400×1638 to get help on troubleshooting.
Product Update:
Product Update has successfully applied KB 4052908 <http://support.microsoft.com/?id=4052908&gt;. These updates have set the patch level of the Setup operation to 13.2.5026.0.

-> Above error is pretty clear that it is not able to install Microsoft Visual C++ 2015 Redistributable.

-> Details.txt contained below message/error,

(04) 2019-11-19 15:42:11 Slp: The directory monitor thread is interrupted due to the following exception while monitoring the notifications for directory ‘C:Program FilesMicrosoft SQL Server’
(04) 2019-11-19 15:42:11 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(04) 2019-11-19 15:42:11 Slp: Inner exceptions are being indented
(04) 2019-11-19 15:42:11 Slp:
(04) 2019-11-19 15:42:11 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.MonitorThreadInterruptedException
(04) 2019-11-19 15:42:11 Slp: Message:
(04) 2019-11-19 15:42:11 Slp: The directory monitor thread is interrupted. Message: ‘The directory monitor thread is interrupted due to a StopMonitor call.’
(04) 2019-11-19 15:42:11 Slp: HResult : 0x86a40016
(04) 2019-11-19 15:42:11 Slp: FacilityCode : 1700 (6a4)
(04) 2019-11-19 15:42:11 Slp: ErrorCode : 22 (0016)
(04) 2019-11-19 15:42:11 Slp: Data:
(04) 2019-11-19 15:42:11 Slp: ErrorMessage = The directory monitor thread is interrupted due to a StopMonitor call.
(04) 2019-11-19 15:42:11 Slp: WatsonData = Microsoft.SqlServer.Configuration.Sco.MonitorThreadInterruptedException@22
(04) 2019-11-19 15:42:11 Slp: Stack:
(04) 2019-11-19 15:42:11 Slp: at Microsoft.SqlServer.Configuration.Sco.DirectoryMonitor.Monitor()

-> Tried this article. But Integration Services installation failed again with same error.

-> Checked Add/Remove programs for list of “Microsoft Visual C++ ….” installation and I could see Visual C++ 2013, 2015, 2017 Redistributable  installed.

-> I was installing SQL Server 2016 on a new server with no other SQL Server instances. So i thought of uninstalling Microsoft Visual C++ 2015, 2017 Redistributable both X64, X86 and start the install again. But, I couldn’t uninstall from Add/Remove programs.

-> When I click on Microsoft Visual C++ 2015, 2017 Redistributable and clicked on Modify or Uninstall, nothing happened. Couldn’t see any uninstall/Modify dialog box coming up. I even tried that after restarting the server, but no luck.

-> Executed below from administrative command prompt.

"C:ProgramDataPackage Cache{80586c77-db42-44bb-bfc8-7aebbb220c00}VC_redist.x64.exe" /uninstall

"C:ProgramDataPackage Cache{3ee5e5bb-b7cc-4556-8861-a00a82977d6c}VC_redist.x64.exe" /uninstall

"C:ProgramDataPackage Cache{206898cc-4b41-4d98-ac28-9f9ae57f91fe}VC_redist.x86.exe" /uninstall

"C:ProgramDataPackage Cache{6c6356fe-cbfa-4944-9bed-a9e99f45cb7a}VC_redist.x64.exe" /uninstall

-> Please note that, I performed above action as this was a new database server and had no worries of any existing SQL Server instances.

-> Rebooted the server and performed the SQL Server Integration Services install again and this time it installed just fine.

Thank You,
Vivek Janakiraman

Disclaimer:
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.

Источник

Возможно, вам также будет интересно:

  • Ошибка установки sniper ghost warrior
  • Ошибка установки service pack 1 windows 7
  • Ошибка установки secret net studio
  • Ошибка установки sa соединения терминала verifone
  • Ошибка установки rockstar launcher код 1

    • Понравилась статья? Поделить с друзьями:
    0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии