Installation: Configuration wizard fails(informazioni in lingua inglese)
Data pubblicazione: 2011/03/07
Issue: Installation: Configuration wizard fails
Summary: During installation, the FAST Search Server 2010 for SharePoint Configuration Wizard is used to configure either a single server or a multiple server deployment. If the configuration wizard fails, there are several possible causes.
Symptom: The configuration of your single or multiple server deployment is unsuccessful, and an error message will be displayed.
Causes: Choose the cause that best matches the error message, or work them through in sequential order:
Cause 1: The Windows Firewall is disabled
Cause 2: The deployment.xml file has an additional character at the beginning of the file
Cause 3: The Windows PowerShell execution policy is incomplete
Cause 4: The SQL database connection string is wrong
Cause 5: The size of the SQL database is increased from its default value
Cause 6: The SharePoint Unified Logging Service (ULS) is installed incorrectly
Cause 7: The FAST Search Server 2010 for SharePoint administration server is installed on a certain kind of multiple processor system
Cause 1: The Windows Firewall is disabled
A typical indication of this cause is that the configuration wizard fails on the non-administration servers.
Resolution: Enable Windows Firewall
Enable the Windows Firewall on the non-administration servers. See Verify that Windows Firewall is turned on on all servers in the FAST Search Server 2010 for SharePoint farm
Run the FAST Search Server 2010 for SharePoint Configuration Wizard.
Cause 2: The deployment.xml file has an additional character at the beginning of the file
A typical indication of this cause is an error message that states:
“Set-FASTSearchIPSec : XML Validation error: Data at the root level is invalid. Line 1, position 1. At line:1 char:20”
The configuration wizard reads the deployment.xml file to obtain information about the topology of the FAST Search Server 2010 for SharePoint deployment. If the deployment.xml file is saved in Visual Studio, a character is added at the beginning of the file (UTF-16’s Byte Order Mark (BOM)). This causes problem when the file is used for configuration of the non-administration servers.
Resolution: Save the deployment.xml file in a different editor from Visual Studio
To validate the deployment.xml file, open PowerShell and run the
Set-FASTSearchIPSec –Createcmdlet.If this cmdlet fails, it is probably the additional character that causes the configuration wizard to fail.
Copy and save the contents of the deployment.xml file in a text editor that does not implement UTF-16 (for example Notepad).
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 an error message that states:
“psconfig.ps1 cannot be loaded because the execution scripts is disabled on this system”.
The reason is probably that the execution policy for PowerShell scripts does not enable scripts to run remotely.
Resolution: Enable PowerShell scripts to run as Administrator and to run remotely.
Ensure that PowerShell scripts are running as Administrator, and that the PowerShell scripts are enabled to run remotely. For information about how to do this, see Enable Windows PowerShell scripts to run.
Run the FAST Search Server 2010 for SharePoint Configuration Wizard.
Cause 4: The SQL database connection string is wrong
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 an incorrect database connection string.
Resolution: Verify that the database connection string is correct for both the database server name and the instance name of the database
Verify with SQL Server Configuration Manager that you have specified the correct connection string; with or without instance name. For information about how to do this, see the step about Database settings in Configure a stand-alone deployment.
Run the FAST Search Server 2010 for SharePoint Configuration Wizard.
Cause 5: The size of the SQL database is increased from its default value
A typical indication of this cause is an error message that states “Configuration failed” when you configure the administration server. The message will not explain why it failed, and you must examine the log file to get the details. If the SQL database size is the cause, the log file indicates that creating the FASTSearchAdminDatabase fails due to a time-out.
This time-out occurs if the initial database size that is defined by the MS SQL Server master database, is increased from its default size.
Resolution: Change the initial database size back to default
From the SQL Server Management Studio, configure the default initial size of the database back to 2MB.
Run the FAST Search Server 2010 for SharePoint Configuration Wizard.
Cause 6: The SharePoint Unified Logging Service (ULS) is installed incorrectly
A typical indication of this cause is an error message that states:
“An error occurred while configuring Post setup - C:\Program Files\Common Files\Microsoft Shared\ULS\14\ULSControllerService.exe. You cannot call a method on a null-valued expression. At C:\FASTSearch\installer\scripts\include\logging.ps1:280 char:33”.
FAST Search Server 2010 for SharePoint uses the ULSCommonCore component to interface with the SharePoint Unified Logging Service (ULS). When the error message refers to the ULSControllerService, the reason may be that the ULS package is installed incorrectly or that the service is not registered.
To determine whether the ULSControllerService can be started, run this command:
net start ULSControllerService
If the service starts successfully, run the configuration wizard again to see whether it succeeds.
If the service cannot start and the error message states that the service name is invalid, this means the ULS package is installed incorrectly and the service is not registered. Follow these resolution steps to resolve the problem:
Resolution: Uninstall the Microsoft ULS Common Core if the ULSControllerService cannot be started
Check C:\Program Files\Common Files\Microsoft Shared\ULS\14\ to confirm that ULSControllerService.exe is not there.
In this situation, for the ULSControllerService to be successfully installed by the configuration wizard, you actually have to uninstall the ULSCommonCore component for the configuration to finish.
Uninstall the Microsoft ULS Common Core Components 14 via the Control Panel and Uninstall a program. Select the Microsoft ULS Common Core Components 14 program and select ‘Uninstall’.
Run the FAST Search Server 2010 for SharePoint Configuration Wizard.
Cause 7: The FAST Search Server 2010 for SharePoint administration server is installed on a certain kind of multiple processor system
A typical indication of this cause is an error message that states “Configuration failed” when you configure the administration server. The message will not explain why it failed, and you must examine the log file to get the details. If a certain multiple processor system is the cause, this error can be found in the log file:
“ Verbose Utility.Execute - Finished executing "E:\FASTSearch\bin\ResourceStoreInstaller.exe" Error InstallResourceStore - An error occurred while executing binary "E:\FASTSearch\bin\ResourceStoreInstaller.exe". Return code is not 0. Error Utility.WriteException - Exception - : Exception - System.Management.Automation.RuntimeException: An error occurred while installing Resource store.
ERROR ( message:Unknown attribute "verbs.allowUnlisted". ”
This might occur on systems with multiple processors and hyperthreading, and the reason is that configuration of the administration server fails due to a timing issue when communicating with IIS to set up the Resource Store.
Resolution: Temporarily reduce number of processors on the FAST Search Server 2010 for SharePoint administration server
Disable the processors on the administration server by using the Microsoft System Configuration Utility (msconfig). Start msconfig.exe, select the Boot tab and then click on Advanced Options.
Select ‘Number of processors’ and set it to 1.
Restart the administration server.
Run the FAST Search Server 2010 for SharePoint Configuration Wizard on the administration server again.
When configuration of the administration server is complete, set the number of processors back to original status and restart the server.
When the administration server is verified running, configure the non-administration server(s) in the deployment.
Vedere anche
Concetti
Cronologia delle modifiche
| Data | Descrizione | Motivo |
|---|---|---|
2011/03/07 |
Pubblicazione iniziale |