SQL server error 1639 occurs at the time of the SQL Server installation. It happens due to a number of reasons ranging from issues with folder name to SQL port.
As a part of our Server Management Services, we help our Customers to fix SQL related errors regularly.
Let us today discuss the possible causes and fixes for this error.
What causes the SQL error 1639?
Installation of SQL Server on windows machine fails due to a number of reasons. Some of them to list out are:
- The name of the installation directory has space in it.
- Remnants of the previous installation that leave orphaned entries in the windows installer registry.
- Another service running in the SQL port.
- The issue with the Windows temp folder.
As a result, the installation fails and users face the message that the SQL installation completed with failures. You can get the details of the exact error message from the Summary logs. The error message would look like:
Let us now look at the possible fixes for this error.
How to fix the SQL error 1639?
As we discussed earlier a major reason for this error is unwanted characters in the installation folder name. For instance space between the words in the folder name is not permitted. Therefore, if the installation folder name is SQL Server 2008, it is a good idea to change it to SQLServer2008 or SQL_Server_2008.
Next, we can remove the failed installation from the server using “Add and Remove Programs”. Finally, we can start the installation again by a right-click on the setup file and choosing “Run as administrator” option.
Unnregister and re-register Windows installer
Another reason for this error could be an issue with the Windows installer. We could solve this by an unregister and re-register of the Windows installer.
a) Click Start and the Run.
b) In the Run box type msiexec /unreg and then ENTER.
c) Click Start and the Run.
d) In the Run box type msiexec /regserver and then ENTER.
Stop the service running on the SQL port
By default, the typical ports used by SQL Server and associated database engine services are: TCP 1433, 4022, 135, 1434. If any other service is running in this port, it may cause a failure for the SQL installation. Thus we may need to stop the service running in that port. To find the service running in the port,
1.Open command prompt as administrator.
2.Use the command netstat -a -n -o and it shows the result in the order "protocol, local IP:local port, foreign IP:foreign port, port state, and pid".
3.View the local port and pid from the result in step 2.
4.Open task manager and navigate to details tab.
5.Search for the pid obtained in step 3 in the details tab to get the details of the service.
Now that we have the service name, we could either stop that service or change the port number of the service to complete the SQL installation
[Need help to fix SQL errors? We are available 24×7.]
Conclusion
In short, the SQL server error 1639 occurs at the time of the SQL Server installation. The major reasons for this error include extra spaces in the installation file name, another service using SQL port, etc. Today we saw how our Support Engineers fixes this error.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
GET STARTED
var google_conversion_label = «owonCMyG5nEQ0aD71QM»;
Hi All,
Today I was installing microsoft SQL developer/express on my laptop. However the installation ends in a
1639 error.
Unable to install SQL Server (setup.exe). Exit code (Decimal): -2068052377Error description: Invalid command line argument. Consult the windows Installer SDK for detailed command line help.
How can I fix this error?
These are parts of the log files:
Log file 1
Configuration file:
C:Program FilesMicrosoft SQL Server140Setup BootstrapLog20180823_181447ConfigurationFile.ini
Detailed results:
Feature:
Database Engine Services
Status:
Failed
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 FilesMicrosoft SQL Server140Setup BootstrapLog20180823_181447sql_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:
https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=
14.0.1000.169&EvtType=sql_engine_core_inst.msi%400x162A16FE%400×1639
Log file 2
MSI (s) (4C:0C) [18:15:28:084]: Machine policy value ‘TransformsSecure’ is 0
MSI (s) (4C:0C) [18:15:28:085]: User policy value ‘TransformsAtSource’ is 0
MSI (s) (4C:0C) [18:15:28:086]: Machine policy value ‘DisableUserInstalls’ is 0
MSI (s) (4C:0C) [18:15:28:086]: Specified instance {36C9ADEE-91B0-4FFA-9CBA-9164CE6089D5} via transform :InstID02.mst;:InstName02.mst is already installed. MSINEWINSTANCE requires a new instance
that is not installed.
MSI (s) (4C:0C) [18:15:28:087]: MainEngineThread is returning 1639
MSI (s) (4C:94) [18:15:28:088]: User policy value ‘DisableRollback’ is 0
MSI (s) (4C:94) [18:15:28:088]: Machine policy value ‘DisableRollback’ is 0
MSI (s) (4C:94) [18:15:28:088]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (4C:94) [18:15:28:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionInstallerRollbackScripts 3: 2
MSI (s) (4C:94) [18:15:28:089]: Note: 1: 1402 2: HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionInstallerRollbackScripts 3: 2
MSI (s) (4C:94) [18:15:28:089]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.
Counter after decrement: -1
MSI (c) (18:C0) [18:15:28:091]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.
Counter after decrement: -1
MSI (c) (18:C0) [18:15:28:091]: MainEngineThread is returning 1639
=== Verbose logging stopped: 23/08/2018
18:15:28 ===
Thanks very much.
Regards,
Giovanni
I’ve been struggling to install sql server 2017 for a few days now. I keep getting message:
Oops… Unable to install SQL Server(setup.exe). Exit
code(Decimal)-2068052377 Error description:Invalid command line
argument.Consult the Windows Installer SDK for detailed command line
help.
I’ve tried to delete all sql folders , registry keys, uninstall everything related to SQL Server, installing as admin, cleaning and fixing the registry, rebooting,… Still cant install. Please help. Thanks in advance! I attached image and logs
Last week, I was installing SQL Server 2012 on one of the database server. Unfortunately, the installation was failed with the error 1639. I have given below the details of this error code.
Product: Microsoft SQL Server Browser – Update Service Pack 1 for Microsoft SQL Server Browser (KB-NUMBER)’ could not be installed. Error code 1639.
Root Cause
I was not able to find any reason behind this error because I had followed all prerequisites before starting this installation. I went to some forums to get a root cause of this error 1639 or solution to fix it and what i found is described in this article.
This issue (Error 1639) comes when there is a blank space between your SQL Server setup folder directories. As I found my setup files were placed under a directory named “SQL Server 2012”. You can see there are two blank space between this directory name. This was the main reason or cause behind getting this SQL Server installation error. Read next section to fix this issue and install SQL Server successfully on your database server.
Resolution
To fix this issue, we have decided to first uninstall SQL Server instance that was failed to install. I have uninstalled it from “Add and Remove Programs” and deleted all SQL Server folders that was created during the installation. Once failed installation of SQL Server was uninstalled from database server, we have rebooted the machine to proceed with fresh installation.
As I mentioned above, issue was due to blank space between the parent directory of SQL Server setup files. You can see the name of directory in below screenshot.
Now I have removed the blank space between the words of this folder name and changed it to “SQLServer2012”. You can see the below screenshot of this change.
That’s all to fix this issue. Now go ahead and start the installation again for your work.
Once this directory was renamed, I have started the SQL Server installation process. I had launched setup file and proceed for installation. You can also right click on setup file and choose “Run as Administrator” to start the installation. Follow all windows and processes of installation process as you did last time to install it. This time your SQL Server instance will be installed without any issue.
The key takeaway from this issue is to never keep any bank space between files or folders otherwise you will be end up with similar issues.
I hope you like this article. Please Like, Share, Comment & Subscribe to this website to get all new articles directly to your index. You can also follow our Facebook page and Twitter handle to get latest updates.
Read More:
- SQL Server Interview Questions & Answers on Architecture
- SQL Server Interview Questions & Answers on Indexes
- Microsoft SQL Server DBA Interview Questions & Answers
- SQL Server Interview Questions & Answers on Backup & Recovery
- Author
- Recent Posts
I am working at one of the top MNCs and have extensive experience on all versions of SQL Server since 2000,I have good hands on experience onfollowing database features: Database Mirroring, Always ON, Replication, Log Shipping, Geo-Clustering and Performance Tuning and delivered many SQL Server projects on consolidation, upgrades, heterogeneous replication, HA / DR solutions, automation and major performance tuning
Summary
Article Name
How to Fix SQL Server Installation Error 1639?
Description
Last week, I was installing SQL Server 2012 on one of the database server. Unfortunately, the installation was failed with the error 1639. I have given below the details of this error code. Product: Microsoft SQL Server Browser – Update Service Pack 1 for Microsoft SQL Server Browser (KB-NUMBER)’ could not be installed. Error code 1639.
Я уже несколько дней пытаюсь установить sql server 2017. Я получаю сообщение:
К сожалению… Не удалось установить SQL Server(setup.exe). Код выхода (десятичный)-2068052377 Описание ошибки: недопустимый аргумент командной строки. Для получения подробной справки по командной строке обратитесь к пакету SDK для установщика Windows.
Я попытался удалить все папки sql, ключи реестра, удалить все, что связано с SQL Server, установить как администратор, очистить и исправить реестр, перезагрузить… Все еще не могу установить. Пожалуйста помоги. Заранее спасибо! Я прикрепил изображение и логи
2019-10-15 15:03