Troubleshooting and Tech Help > SQL Server Requirements > Common reasons for SQL server installation failure

Common reasons for SQL server installation failure

<< Click to Display Table of Contents >>

Navigation:  Troubleshooting and Tech Help > SQL Server Requirements >

Common reasons for SQL server installation failure

Letting Docsvault install MSSQL Server

 

Following are the most common reasons for failure of background SQL server express 2008 R2 installation during Docsvault Configuration Process. You can also study the SQL server failure reason in the install summary located at: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\Summary.txt

 
Weak Password

 

If you are installing Docsvault Server on a machine that is running a Server OS (like Windows Server 2003 or 2008, etc.) or if your domain has a strong password requirement policy, you will need to provide a strong (complex) password as per your network policy during the Docsvault Configuration process.

 

Same Username and Hostname

 

If the Windows username you are installing under is the same as the machine(host) name, SQL server will install but the SQL server service will not start up. To resolve this simply change the Hostname for your computer or install under another windows account.

 

.Net Framework v3.5 SP1

 

Even if you have .Net Framework v4 or above installed, SQL server still needs .Net Framework v3.5 SP1 also installed on your machine. For server OSes like Windows Server 2008 and above, .Net Framework v3.5 can be installed as a feature from the Server Manager dialog.  

 

Hard Drive Compression

 

If the data location you specified is compressed (hard disk compression enabled from properties>advanced dialog), the SQL server will not be able to create the necessary database files and the Docsvault configuration process will fail. To disable compression on hard disk (if enabled) go to the folders properties dialog and click the Advanced button under the general tab. Uncheck the ‘Compress contents to save disk space’ checkbox if checked. After applying the changes start the Docsvault Configuration process again by double clicking the Docsvault Server Manager icon on desktop.

 

 

Rebooting machine after uninstalling previous versions of SQL server

 

If you uninstalled any previous SQL server installations on your machine or the current background installation of SQL server was not successful for reasons other than specified above, you will need to reboot Windows before you attempt to start the Docsvault Configuration process again.

 

 

Incomplete download of SQL server install files

 
During configuration Docsvault will automatically download the install files for SQL server express 2008 R2 if necessary. Sometimes due to bad internet connectivity if the download is not successful the Docsvault Configuration process will fail. Following are the general guidelines for the SQL server install file/folder sizes in the server program folder

 

For Docsvault v5 and above:

In C:\Program Files (x86)\Docsvault <edition>\Server\SQL Folder Size: > 580 MB (64 bit OS)

 

For Docsvault v4.x:

In C:\Program Files (x86)\Docsvault <edition>\Server\SQLEXPR_64_ENU.EXE > 56 MB (for 32 bit OS) or > 75 MB (for 64 bit OS)

 

 

Uncommon Errors:

 

If your summary.txt file reports errors related to performance counters registry entry see this:
http://blogs.technet.com/b/yongrhee/archive/2009/10/06/how-to-rebuild-performance-counters-on-windows-vista-server2008-7-server2008r2.aspx

 

If the SQL browser does not start due to failed ssrp redirection (browser service for sql 2000) see this https://sqllearnings.wordpress.com/tag/ssrp-redirection-service/