20
2013
SQL Server Installation failed with error status: 1639
Today while installing SQL Server 2008 R2 with SP1, installation failed with following error code,
——————
MSI (s) (4C:9C) [04:51:32:016]: Product: SQL Server 2008 R2 SP1 Database Engine Services – Update ‘Service Pack 1 for SQL Server Database Services 2008 Core Instance (64-bit) (KB2528583)’ could not be installed. Error code 1639. Additional information is available in the log file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130820_043842\sql_engine_core_inst_Cpu64_1.log.
MSI (s) (4C:9C) [04:51:32:016]: Windows Installer installed an update. Product Name: SQL Server 2008 R2 SP1 Database Engine Services. Product Version: 10.51.2500.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: Service Pack 1 for SQL Server Database Services 2008 Core Instance (64-bit) (KB2528583). Installation success or error status: 1639.
MSI (s) (4C:9C) [04:51:32:016]: Windows Installer installed the product. Product Name: SQL Server 2008 R2 SP1 Database Engine Services. Product Version: 10.51.2500.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1639.
MSI (s) (4C:9C) [04:51:32:016]: MainEngineThread is returning 1639
Info 1639.Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
——————-
Investigated all database options we selected and didn’t found any issue, then searched over online forums, similar issue was found reported at following thread http://scn.sap.com/thread/2103921
In our case we found the problem as usage of space in the folder names for e.g. “SQL Server Installable”, now when we modified the folder name without any space for e.g. “SQLServer_Installable” then issue got fixed and installation went successful.
So the learning from this is, never ever use space in Folder names, File names, Database names, User names, etc. to make life simple and easy in Windows operating system else you may continue to land up in such issues.
Hope it may help someone.
References:
Following link provided solution, http://scn.sap.com/thread/2103921
If issue is not as above described then following link can be referred as well, http://social.msdn.microsoft.com/Forums/sqlserver/en-US/4d6158a1-b601-428c-aad4-a1716e76de1a/install-sql-server-problem

5 Comments + Add Comment
Leave a comment to Sanjay K
Subscribe to this blog via Email
Old Posts
- November 2017 (3)
- October 2017 (4)
- September 2017 (2)
- May 2017 (1)
- April 2017 (1)
- July 2016 (3)
- May 2016 (1)
- April 2016 (1)
- February 2016 (2)
- January 2016 (1)
- October 2015 (1)
- September 2015 (1)
- August 2015 (1)
- July 2015 (2)
- June 2015 (3)
- April 2015 (1)
- March 2015 (1)
- December 2014 (1)
- September 2014 (2)
- April 2014 (1)
- January 2014 (3)
- October 2013 (2)
- September 2013 (2)
- August 2013 (4)
- July 2013 (1)
- June 2013 (2)
- May 2013 (5)
- April 2013 (3)
- March 2013 (1)
- February 2013 (9)
- January 2013 (11)
- December 2012 (14)
- November 2012 (3)
- October 2012 (4)
- July 2012 (2)
- June 2012 (3)
- May 2012 (2)
- April 2012 (8)
- March 2012 (6)
- February 2012 (3)
- January 2012 (1)
- December 2011 (5)
- November 2011 (8)
- October 2011 (5)
- September 2011 (3)
- August 2011 (3)
- July 2011 (3)
- May 2011 (1)
- November 2010 (1)
Tags
Calender
M | T | W | T | F | S | S |
---|---|---|---|---|---|---|
« Nov | ||||||
1 | 2 | 3 | 4 | 5 | 6 | 7 |
8 | 9 | 10 | 11 | 12 | 13 | 14 |
15 | 16 | 17 | 18 | 19 | 20 | 21 |
22 | 23 | 24 | 25 | 26 | 27 | 28 |
View Post by Categories
Recent Articles
- Setting up Always ON Availability Group in Multi Subnet Cluster – Recommendations
- Configuring Replication with Always ON Availability Group
- Login failed for user ‘DOMAIN\COMPUTER$’. Reason: Could not find a login matching the name provided. [CLIENT: ]
- Modern Servicing Model (Service Pack and Cumulative Updates) for SQL Server 2017 and onwards
- Fix: SSMS 2012 opening Debug window when pressing F5
Hi
You saved my day, thanks a lot. Installation file has space so failed, come on this is not the first year of computer, stupid and silly.
Glad to hear that it helped 🙂
I’m trying to instal sql server 2014. when i installing its causes error in some featurs like Reporting sevices Native Failed
Database engine services Failed
Full text and semantic expression for search Failed
Sql server replication Failed.
so how can i solved this type of errors please help me…
Hi Sanjay, first and foremost check the bootstrap log, you can get error in summary and more detailed error in respective log files summary may point to, you can begin your troubleshooting from first error you see. If everything fails at first attempt most probably it may be linked with version of media or the privileges of account on server, rest you can post your errors and see if I can help further.
Final result: Failed: see details below
Exit code (Decimal): -2068052377
Start time: 2016-04-13 01:02:26
End time: 2016-04-13 01:06:22
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for FullText: Use the following information to resolve the error, and then try the setup process again.
Next step for Replication: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: SANJAY-PC
Machine processor count: 4
OS version: Windows 8
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 2014 Management Tools – Basic 1033 Express Edition 12.0.2000.8 No Yes
SQL Server 2014 Management Tools – Complete 1033 Express Edition 12.0.2000.8 No Yes
SQL Server 2014 Client Tools Connectivity 1033 Express Edition 12.0.2000.8 No Yes
SQL Server 2014 Client Tools Backwards Compatibility 1033 Express Edition 12.0.2000.8 No Yes
SQL Server 2014 Client Tools SDK 1033 Express Edition 12.0.2000.8 No Yes
SQL Server 2014 LocalDB 1033 Express Edition 12.0.2000.8 No Yes
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: F:\Application\SQL Server 2014\SQLEXPRADV_x64_ENU\x64\setup\
Installation edition: Express
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT:
ASSVCPASSWORD:
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS:
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME:
CLTRESULTDIR:
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT:
CLTSVCPASSWORD:
CLTWORKINGDIR:
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT:
CTLRSVCPASSWORD:
CTLRUSERS:
ENABLERANU: true
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, RS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME:
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SQLEXPRESS
FTSVCPASSWORD:
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: c:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: c:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SQLEXPRESS
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD:
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME:
MATRIXNAME:
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer$SQLEXPRESS
RSSVCPASSWORD:
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR:
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SQLEXPRESS
SQLSVCPASSWORD:
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: SANJAY-PC\Sanjay
SQLTEMPDBDIR:
SQLTEMPDBLOGDIR:
SQLUSERDBDIR:
SQLUSERDBLOGDIR:
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160413_010210\ConfigurationFile.ini
Detailed results:
Feature: Reporting Services – Native
Status: Failed: see logs for details
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: SQL Server Database Engine Services Instance Features
Component error code: 1639
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160413_010210\sql_engine_core_inst_Cpu64_1.log
Error description: Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sql_engine_core_inst.msi%400x162A16FE%400×1639
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 1639
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160413_010210\sql_engine_core_inst_Cpu64_1.log
Error description: Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sql_engine_core_inst.msi%400x162A16FE%400×1639
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
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: SQL Server Database Engine Services Instance Features
Component error code: 1639
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160413_010210\sql_engine_core_inst_Cpu64_1.log
Error description: Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sql_engine_core_inst.msi%400x162A16FE%400×1639
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 1639
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160413_010210\sql_engine_core_inst_Cpu64_1.log
Error description: Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sql_engine_core_inst.msi%400x162A16FE%400×1639
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160413_010210\SystemConfigurationCheck_Report.htm
This is overall summary so how i can solve..