Today on a test box we had to install SQL Server 2005 Enterprise Edition as a default instance. Since it was a test box, it was supposed to be a smooth sail. But it wasn’t to be.
DBA started the installation and it failed at the very early stages of installation. While installing the SQL Native client, the installer failed and the Summary.txt read
Product : SQL Native Client
Error : An installation package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package ‘sqlncli.msi’.
Looking at this error message, the DBA’s knee-jerk reaction was to copy the installation media all over again. The installation files were copied again to the local server still the installation failed with the same error message. This has to be something other than the corrupt installation media. sqlncli.msi file was present in the CD1 –> Setup folder and it was valid.
In order to check if any other instance of SQL Server was running, the DBA headed to services.msc console. He was right! There was an instance of SQL Server Express Edition already running. But this should not stop any new installation from proceeding. We wanted to get rid of that instance (since it a test box) but did not want to take any chances on a weekend. It is not strange to have wacky setups on test boxes. If we mess it up today, on a fine Monday morning the Application team will make lot of noise about their “critical” setup having issues.
Instead of uninstalling the SQL Server Express Edition (2005), we decided to just uninstall the Microsoft SQL Server Native Client. It turned out to be the right choice. After uninstalling Microsoft SQL Server Native Client the SQL Server installation proceeded further and completed successfully !
No big deal but it was good enough to send some jitters to the DBA on a lazy Saturday evening.