One of the most common task for a DBA’s are to perform installation of new SQL Server versions and installing patches. Most often or not everything goes just smooth, but there will be many occasions we end up with failures with various errors and it will be difficult to find the cause and the solution of the failure.
Below are some of the common errors and their resolutions which can cause the SQL Server setup failure.
SQL Server 2008 R2 setup failed with “Error 1406. Could not write value to key \SOFTWARE. System error. Verify that you have sufficient access to that key, or contact your support personnel”
– Run setup as Administrator
– Make sure Administrator has full control on the registry key reported in the error.
– This issue can happen, if there are any kind of virus/adware/malware/Addons on the system. Scan the system and fix any such issues.
– There is a connect bug raised for the same, please check of there are any latest updates.
Error 997. Overlapped I/O operation is in progress during SQL Server installation
– Check the account with which you logged on to the server, make sure it is not a account with temporary profile.
– Run the Setup locally on the server and make sure you run the setup, by right-clicking on the Setup file and choose Run-As-Administrator.
– Disable any Anti-virus and reboot the server.
– Check for any problems with the disk drive where you are installing SQL Server files.
Invalid license data. Reinstall is required Error while trying to connect to SQL Server Management Studio (SSMS)
– Try to repair the SQL Server shared components(If you cannot launch the setup from control panel, use the Setup.exe from setup media.
– After repair, if it SSMS still fail with the same error, then uninstall Visual Studio 2010 or 2012 and then attemt the repar of the shared components again.
Errors while trying run SQL Server 2008 R2 setup to add second SQL node.
Microsoft.SqlServer.Configuration.Agent.InputValidationException: The credentials you provided for the SQL Server Agent service are invalid. To continue, provide a valid account and password for the SQL Server Agent service.
There are various reasons why this error can occur, below are some of the common causes.
– SQL Server installation on the first node may have not been completely successful and may have not created the SQL Server Agent cluster resouce. Check cluster manager and verifiy, if both the SQL Server and SQL Agent cluster resources got created. If SQL Agent resource is not created, then repair the installation on first node and fix any errors returned by the setup on first node.
– Another cause of this error could be that the SQL Server Agent resouce may be in failed or OFFLINE state. Bring it online on first node, before you again attempt the ADD NODE on second server.
– Another option is try and run the setup from command line. Run the below setup from an elevated command prompt on second server.
setup.exe /ACTION=AddNode /INSTANCENAME="
Setup failed while trying to Add node at the initial steps in the “add Node Rules” setup wizard and returned below error.
Rule Check Result
Rule "SQL Server Database Services feature state" failed.
The SQL Server Database Services feature failed when it was initially installed. The feature must be removed before the current scenario can proceed.
– This error would mostly appear, if there was a failure with the SQL Server installation on the first node. Look into the setup logs on first node and fix the issue and run repair on the first node and make sure SQL Server and SQL Agent resources are online on the first node.
– If after fixing the problems with the first node, still if you are seeing this error on the second node, then follow the below steps.
o Change the below registry key on first node and the second node
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLServer\ConfigurationState
Change all 4 values from 2 to 1
o Run repair on the first node, make sure it complets successfully.
o Run the Add node operation on the second node.
Rule “Setup account privileges” failed.
The account that is running SQL Server Setup does not have one or all of the following rights: the right to back up files and directories, the right to manage auditing and the security log and the right to debug programs. To continue, use an account with both of these rights.
– Ensure that the account which you are using to launch the setup is local administrator on the server.
– Make sure you run the setup by right-clicking and choose Run-as-Administrator.
– Add the account which you are running the setup to below local security policies. Click Start -> Run -> Type secpol.msc -> Select option “Local Security Policy” -> Choose “Local Policies” -> then on right side, go to properties of each of the below mentioned policies and add the account which is used to run the SQL setup.
o Backup files and directories
o Debug Programs
o Manage auditing and security log
Error Code: 1067
MSI (s) (5C!6C) [14:50:06:117]: Product: Microsoft SQL Server 2005 — Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, “How to: View SQL Server 2005 Setup Log Files” and “Starting SQL Server Manually.”
The error is (1067) The process terminated unexpectedly..Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, “How to: View SQL Server 2005 Setup Log Files” and “Starting SQL Server Manually.”
– Above errors occur when you try to install SQL Server on a server which has ratio of number or processors between logical processors is not a power of 2. Example, on a computer which has a one socket with 6 logical processors which is not a power of 2.
– The resolution to this problem is as mentioned in the below KB article
Could not fix registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\MICROSOFTBCM\MSSQLServer\SuperSocketNetLib\Lpc.The SQL Server registry keys from a prior installation cannot be modified. To continue, see SQL Server Setup documentation about how to fix registry keys.
– Setup may fail complaining about a particular registry key, in which case, cleanup any previous failed installation of SQL Server, grant full permission to the mentioned registry key to your account and to SQL service account and then rerun the setup by choosing Rus-as-Administrator.
– There could be variations of this error like after uninstalling SQL Server and then when you attempt to reinstall again, the following error occurs. “Rule ‘Consistency validation for SQL Server registry keys’ failed”. The SQL Server registry keys from a prior installation cannot be modified. Further in the logs, you may notice error “File C:\TEMP\en_sql_server_2008_r2_standard_x86_x64_ia64_dvd_521546\x64\FixSqlRegistryKey_x86.exe does not exist!”
– To fix the above error, download the new setup media, as the existing one appears corrupt or not complete. Another option is to copy the file “FixSqlRegistryKey_x86.exe” into x64 folder from another setup media which has this file in x86 to x64 folders of setup media.
There are many other errors which cause SQL Server setup failure and will try to add as many as possible. Send me any issues you encountered, so that I can add them, which will be helpful for others.
This is applicable on below versions of SQL Server
SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
Hope this was helpful.
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.