- 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
-
Moved by
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
First published on MSDN on Mar 26, 2018
Dear all,
Depending on which products were installed on the server beforehand, a SQL Server 2017 setup may fail with the following error :
TITLE: Microsoft SQL Server 2017 Setup
——————————
The following error has occurred:
VS Shell installation has failed with exit code 1638.
Note that it could happen even after SQL Server 2017 setup was executed successfully once already. Eg. the following steps would reach the situation : install a first SQL Server 2017 instance (no error), install SSMS 17 from the Web (no error), install a 2nd instance (error 1638).
Anyway, the important thing is that situation is covered by KB
4092997
and as indicated in the KB, a simple Repair of ‘Microsoft Visual C++ 2015 Redistributable (x64)’ followed by a server restart should clear the problem (please check the current KB content though, as it may be updated with further details after this post is published).
We’re working on making the interactive link of SQL Server setup’s pop-up message a bit more useful than it is today, and the more specific situation where our very own SSMS introduces the problem is under review.
Regards,
Guillaume Fourrat
Escalation Engineer
I have received the following error while installing MSSQL 2017 on Windows 2012 R2.
vs shell installation has failed with exit code 1638
asked May 25, 2018 at 8:59
Hiren ParghiHiren Parghi
1,7951 gold badge21 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)
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)
answered Aug 7, 2018 at 17:52
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
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
1
Hello I am unable to install SQL Server 2017 setup:
Here is my summary log:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068052378
Start time: 2018-08-25 04:34:19
End time: 2018-08-25 04:38:45
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: LAPTOP-1DOQ0VOG
Machine processor count: 4
OS version: Microsoft Windows 10 Home (10.0.17134)
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured
SQL Server 2017 Client Tools Connectivity
1033 14.0.1000.169 No Yes
SQL Server 2017 Client Tools Backwards Compatibility
1033 14.0.1000.169 No Yes
SQL Server 2017 Client Tools SDK
1033 14.0.1000.169 No
Yes
Package properties:
Description: Microsoft SQL Server 2017
ProductName: SQL Server 2017
Type: RTM
Version: 14
SPLevel: 0
Installation location: C:SQLServer2017MediaDeveloper_ENUx64setup
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT ServiceSQLAgent$UserNameSQL
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: TABULAR
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTELSVCACCT: <empty>
ASTELSVCPASSWORD: <empty>
ASTELSVCSTARTUPTYPE: 0
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:Program FilesMicrosoft SQL Server140Setup BootstrapLog20180825_043418ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
EXTSVCACCOUNT: <empty>
EXTSVCPASSWORD: <empty>
FEATURES: SQLENGINE
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTPYTHONLICENSETERMS: false
IACCEPTROPENLICENSETERMS: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:Program FilesMicrosoft SQL Server
INSTALLSHAREDWOWDIR: C:Program Files (x86)Microsoft SQL Server
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:Program FilesMicrosoft SQL Server
INSTANCEID: UserNameSQL
INSTANCENAME: UserNameSQL
ISMASTERSVCACCOUNT: NT AUTHORITYNetwork Service
ISMASTERSVCPASSWORD: <empty>
ISMASTERSVCPORT: 8391
ISMASTERSVCSSLCERTCN: <empty>
ISMASTERSVCSTARTUPTYPE: Automatic
ISMASTERSVCTHUMBPRINT: <empty>
ISSVCACCOUNT: NT AUTHORITYNetwork Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
ISTELSVCACCT: <empty>
ISTELSVCPASSWORD: <empty>
ISTELSVCSTARTUPTYPE: 0
ISWORKERSVCACCOUNT: NT AUTHORITYNetwork Service
ISWORKERSVCCERT: <empty>
ISWORKERSVCMASTER: <empty>
ISWORKERSVCPASSWORD: <empty>
ISWORKERSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
MRCACHEDIRECTORY:
NPENABLED: 0
PBDMSSVCACCOUNT: <empty>
PBDMSSVCPASSWORD: <empty>
PBDMSSVCSTARTUPTYPE: 0
PBENGSVCACCOUNT: <empty>
PBENGSVCPASSWORD: <empty>
PBENGSVCSTARTUPTYPE: 0
PBPORTRANGE: <empty>
PBSCALEOUT: false
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE:
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT ServiceMSSQL$UserNameSQL
SQLSVCINSTANTFILEINIT: true
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: LAPTOP-1DOQ0VOGUserName
SQLTELSVCACCT: NT ServiceSQLTELEMETRY$UserNameSQL
SQLTELSVCPASSWORD: <empty>
SQLTELSVCSTARTUPTYPE: Automatic
SQLTEMPDBDIR: <empty>
SQLTEMPDBFILECOUNT: 4
SQLTEMPDBFILEGROWTH: 64
SQLTEMPDBFILESIZE: 8
SQLTEMPDBLOGDIR: <empty>
SQLTEMPDBLOGFILEGROWTH: 64
SQLTEMPDBLOGFILESIZE: 8
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SUPPRESSPRIVACYSTATEMENTNOTICE: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:Program FilesMicrosoft SQL Server140Setup BootstrapLog20180825_043418ConfigurationFile.ini
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 BootstrapLog20180825_043418VCRuntime140_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%400×1638
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:Program FilesMicrosoft SQL Server140Setup BootstrapLog20180825_043418SystemConfigurationCheck_Report.htm