Previous FineBuild Troubleshooting SQL Configuration Problems Next

SQL Server Installation Problems

See for details on how to find and analyse the SQL Server installation logs. The following failure situations are the most common that have occurred during testing of FineBuild.

.Net 3.5 SP1 Problems

Experience has shown that the most frequent problem during the install of SQL Server is the installation of .Net 3.5 SP1. This installation also installs .Net 2.0 and .Net 2.0 SP2, and it is these components that cause the most problems.

If the install is performed on a newly-build Windows instance, problems seldom occur. However, if the .Net 3.5 SP1 installation is performed on a server that has been updated over many months or years, or has had .Net 3.0 already installed but does not have .Net 2.0 SP2 installed, failures are possible. In this situation there are two possible resolutions:

1. Research the error messages encountered and perform the suggested troubleshooting. Normally this includes removal of .Net 3.0 and re-running the .Net 3.5 SP1 install. In practice, this fixes only a few of the problems encountered, and always leaves the Windows environment in a state that is impossible to reproduce if the server has to be rebuilt.

2. Reformat the system drive and re-install Windows. Do not make any attempt to install .Net 3.0, but instead perform the .Net 3.5 SP1 install.

The recommended resolution is to always reinstall Windows if this problem occurs.

Password for the SQL Agent Account is Invalid

The SQL Agent account is the first account that gets validated during a SQL Server install. If there are any problems performing account validation this message is given but it does not always mean that the password is invalid.

If you get this message, and you are certain that the SQL Server Agent password is correct, then the most likely cause of this message is that the SQL Server machine cannot contact a Domain Controller to perform account validation. This problem is often caused by a firewall restriction, but can also be caused by a problem with the trust relationship between the domain and the server. You should follow your site procedures to report this problem to your Windows support team.

Network Interface Error

If you are performing a cluster install of SQL Server and you get a message similar to the one below, then review the list of potential causes.
Network Interface.jpg
Potential Cause Troubleshooting
No Public network available to the Cluster Use Cluste rManager to check the network configuration. A cluster must have at least one network configured for public access
Ghost Adaptor exists Review the advice given in In particular, ensure that no ghost adaptors or disabled adaptors are higher in the binding order than active adaptors
Incorrect Binding Order This very seldon occurrs as FineBuild automatically fixes most binding order problems. The troubleshooting is the same as that for Ghost Adaptors

Timing Issues on Guest Servers

The SQL Server install performs a number of timing tests during the install, and if one of these fail the install is cancelled. Most of these tests relate to service start and stop times, but even components that do not appear to use services (e.g. the PowerShell install) include timing tests.

It is very unusual to get a timing issue problem using FineBuild, because it automatically detects a slow system and increases the Service Startup Time, which overcomes most occurrences of this problem.

However, if this problem does happen, you may get one of the following symptoms:

1. An explicit message about a service not responding within the expected time

2. A reference to a folder name that does not exist on your server. These folder names relate to those used by Microsoft when building the SQL Server install media.

If a SQL Server install fails on any type of guest server (e.g. VMWare, Hyper-V, etc), then look in the SQL Server install logs to find the primary cause. If the error relates to a timing problem, then this means the guest server is running too slowly to perform a successful SQL Server install.

In all situations during the development of FineBuild where a timing problem occurred, one or both of the following actions allowed the install to be re-run successfully:

1. Provide additional resources to the guest server, especially CPU resource.

2. Reduce the number of other guest servers running on the host, to minimise I-O contention.

Copyright © 2012 Edward Vassie. License and Acknowledgements
Previous FineBuild Troubleshooting Top SQL Configuration Problems Next

Last edited Nov 14, 2012 at 10:43 AM by EdVassie, version 1