Previous FineBuild Components Inventory SQL Server Installation Problems Next

FineBuild Troubleshooting

This page gives some general advice on troubleshooting problems with the FineBuild process, and on problems caused by components that FineBuild installs.

Depending on the problem you have, please click on one of the following:

Generic FineBuild Troubleshooting Process Overview of how to deal with a failure during the FineBuild process
SQL Server Installation Problems Problems while FineBuild is running the Microsoft SQL Server install process
SQL Configuration Problems Problems while doing post-install configuration

Generic FineBuild Troubleshooting Process

The FineBuild scripts are designed to simplify troubleshooting, and can be restarted in the event of a failure. Wherever possible, a log of install activity is captured into one of two locations:

FineBuild logs DrvProg:\Program Files\Microsoft SQL Server\FineBuildLogs
All FineBuild activities are captured in the FineBuildInstall* text file. Where possible, the log file of a component install is also captured in this folder.
SQL Install logs DrvSys:\Program Files\Microsoft SQL Server\version\Setup Bootstrap\Logs
All SQL Server install activities are captured in this folder. Every time Setup is run, a subfolder is created to hold the log files of that process


If FineBuild fails, the following generic troubleshooting process should find the cause of the error.

1) The line number of the statement in error will be given in the console log.
Always make a note of this line number before proceeding further with any troubleshooting. Because of the way that VBScript error handling is performed, it is not possible to capture the line number within a FineBuild script.
2) Locate the line number within the script that has failed.
If the failure has not occurred in a utility subroutine then the line number should indentify the process that has caused the failure.
3) Check that the Process Id label relates to the subroutine where the error is found.
If it does not, then locate the Process Id label within the script and then work forward to identify the calling sequence that ended with the statement in error. If a subroutine is called multiple times it may be necessary to add additional messages to the script to identify exactly what caused the failure.
4) Failure caused by something outside of the FineBuild script (e.g. a missing file)
Correct the problem and prepare to re-run FineBuild.
5) Failure caused by something within the FineBuild script (e.g. a syntax error)
If possible correct the problem, report the issue on the FineBuild site and prepare to re-run FineBuild.
Once the cause of the failure has been corrected then FineBuild can normally be restarted at the point of failure. This is achieved by adding the following parameter to the command you used to start FineBuild:
/restart:auto
If the section of FineBuild processing has moved or deleted files before the failure occurred, then FineBuild will fail again when it finds that the expected file is no longer there. In this situation, the remaining steps in the section that failed must be performed manually, and FineBuild restarted so that it skips the section that has failed.

As an example, if FineBuild fails during Restart SQL Server processing at Process Id 5DB, some of the database files will have been deleted and so a simple /restart:auto will just result in another failure. In this situation, the remaining database files must be deleted manually. The reference to Copy System Database Files in the FineBuild Reference manual will show how to perform this processing. When this has been done, restart FineBuild so that it skips the 5DB processing, by specifying:
/restart:5DC
Copyright © 2012 Edward Vassie. License and Acknowledgements
Previous FineBuild Components Inventory Top SQL Server Installation Problems Next

Last edited Nov 14, 2012 at 10:41 AM by EdVassie, version 4

Comments

No comments yet.