Table of Contents
SQL Server Error : 1639 Details
SQL Server Error: 1639
Severity: 16
Event Logged or not: No
Description:
The eror occurs during installation of SQL Server
Severity 16 Description:
Indicates general errors that can be corrected by the user.
SQL Server error 1639 happens during the installation of SQL Server. It happens for a variety of causes, ranging from folder naming issues to SQL port issues.
We assist our customers with SQL related faults on a regular basis as part of our Server Management Services.
Let’s talk about the probable causes and solutions for this mistake today.
SQL Server installation on a Windows PC fails for a variety of reasons. To name a few, there are:
The installation directory’s name contains a space.
Orphaned entries in the Windows installer registry due to leftovers from a prior installation.
In the SQL port, another service is operating.
The problem with the transient folder in Windows.
As a result, the installation fails, and users see an error message stating that the SQL installation failed. The details of the precise error message can be seen in the Summary logs.
Reading sql server error log location from SQL Query
Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.
USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go
For other ways to read and find error log location please our artcile https://sqlserver-dba.co.uk/error-log/sql-server-identify-location-of-the-sql-server-error-log-file.html
Solution for Resolving the Error
What is the solution to SQL error 1639?
As previously stated, unnecessary characters in the installation folder name are a main cause of this problem. For example, there must be no space between the terms in the folder name. If the installation folder’s name is SQL Server 2008, changing it to SQLServer2008 or SQL Server 2008 is a good idea.
The failed installation can then be removed from the server using “Add and Remove Programs.” Finally, by right-clicking on the setup file and selecting “Run as administrator,” we may restart the installation.
Remove and reinstall the Windows installation
Another possibility for this error is a problem with the Windows installer. We may fix this by uninstalling and reinstalling the Windows installation.
a) Press the Start and Run buttons.
b) Type msiexec /unreg into the Run box, then press ENTER.
c) Press the Start and Run buttons.
d) Type msiexec /regserver into the Run box and press ENTER.
Stop the SQL port service from functioning.
TCP 1433, 4022, 135, 1434 are the common ports used by SQL Server and associated database engine services by default. Any other service operating on this port could cause the SQL installation to fail. As a result, we may need to terminate the service on 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
SQL Server Error Code and solution summary
SQL Server Error: 1639
Severity: 16
Event Logged or not: No
Description:
The eror occurs during installation of SQL Server