Installation: Configuration wizard fails (FAST Search Server 2010 for SharePoint)
Applies to: FAST Search Server 2010
Issue: Installation: Configuration wizard fails
Summary: During installation, you use the FAST Search Server 2010 for SharePoint Configuration Wizard to configure both single server and multiple server deployments. If the configuration wizard should fail, this article lists some of the probable causes and how to resolve the issues.
Symptom: The configuration of the deployment is unsuccessful, and you will see an error message.
Causes: Choose the cause that best matches the error message you are seeing, or work through the causes in sequential order:
Cause 1: The Windows Firewall is disabled
Cause 2: The deployment.xml file has an invalid character at the beginning of the file
Cause 3: The Windows PowerShell execution policy is incomplete
Cause 4: You have entered an incorrect database connection string
Cause 5: You have increased the size of the SQL database from its default value
Cause 1: The Windows Firewall is disabled
One common reason why the configuration fails is that the Windows Firewall is disabled on one or more of the servers.
Resolution: Enable Windows Firewall
Enable the Windows Firewall on all servers. See Verify that Windows Firewall is turned on on all servers in the FAST Search Server 2010 farm.
Re-run the FAST Search Server 2010 for SharePoint Configuration Wizard.
Cause 2: The deployment.xml file has an invalid character at the beginning of the file
The configuration wizard reads the deployment.xml file to obtain information about the topology of the FAST Search Server 2010 for SharePoint deployment. If you have opened and saved the deployment.xml file in an editor (for example Visual Studio) that adds an UTF-16 Byte Order Mark (BOM) to the beginning of files, the configuration wizard fails to read the deployment.xml file properly.
A typical indication of this cause is this error message:
“Set-FASTSearchIPSec : XML Validation error: Data at the root level is invalid. Line 1, position 1. At line:1 char:20”
Resolution: Save the deployment.xml file in a text editor that does not implement UTF-16
Open and save the deployment.xml file in a text editor that does not implement UTF-16, for example Notepad.
Re-run the FAST Search Server 2010 for SharePoint Configuration Wizard.
Cause 3: The Windows PowerShell execution policy is incomplete
A typical indication of this cause is this error message:
“psconfig.ps1 cannot be loaded because the execution scripts is disabled on this system”.
The reason is probably that the execution policy for Windows PowerShell scripts does not allow scripts to run remotely.
Resolution: Enable Windows PowerShell scripts to run as Administrator and to run remotely
Ensure that Windows PowerShell scripts are running as Administrator, and that the Windows PowerShell scripts are allowed to run remotely. See Enable Windows PowerShell scripts to run for more information.
Re-run the FAST Search Server 2010 for SharePoint Configuration Wizard.
Cause 4: You have entered an incorrect database connection string
A typical indication of this cause is an error message that states: “Database validation failed” when you configure the administration server.
The reason is probably that an incorrect database connection string has been entered in the configuration wizard.
Resolution: Verify that the database connection string is correct
On the server where the SQL Server is installed, open SQL Server Configuration Manager from the Start menu. Under SQL Server Services, you see the SQL Server main service. The service name contains the connection string in parentheses.
Re-run the FAST Search Server 2010 for SharePoint Configuration Wizard.
Cause 5: You have increased the size of the SQL database from its default value
If the the initial database size that is defined by the MS SQL Server master database is increased from its default size, the creation of the FASTSearchAdminDatabase can fail because of a time-out.
An indication of this cause is an error message that states “Configuration failed” when you configure the administration server. To determine if the SQL database size has caused a time-out, you must examine the configuration wizard log file (psconfig.log) for details. This log file is typically located in:
<FASTSearchFolder>\var\log\installer\
where <FASTSearchFolder> is the path of the folder where you have installed FAST Search Server 2010 for SharePoint, for example C:\FASTSearch.
Resolution: Change the initial database size back to default
From the SQL Server Management Studio, reset the default initial size of the database to 2MB.
Re-run the FAST Search Server 2010 for SharePoint Configuration Wizard.