Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]
This topic contains problem resolution information to assist you in troubleshooting Gemini installation failure or errors that occur during Setup.
General Troubleshooting Tips
Troubleshoot a Command Line Installation
Troubleshoot a Scale-out Deployment
Check Prerequisites
General Troubleshooting Tips
If you cannot complete installation verification steps due to missing components or configurations, you can try to resolve the problems using the following steps.
Step 1: Verify SharePoint is working correctly
Before you troubleshoot a Gemini deployment, be sure the Web application and site collection are operational. You should be able to access SharePoint Central Administration from the Start menu. You should be able to access the default Web application through either https://localhost or http://<servername>.
Do not proceed with Gemini deployment troubleshooting until you have resolved all blocking issues that prevent SharePoint from running correctly.
Common troubleshooting techniques include re-running the SharePoint Configuration wizard to correct any problems on a new installation. This wizard is available fin the Microsoft Office Server 14 program group. Through the wizard, you can recreate the site collection for the default Web application. If you recreate the site collection, be sure to run iisreset /noforce afterwards.
Step 2: Verify the Engine service is installed
- In Administrative Tools, Services console application, verify that SQL Server Analysis Services (GEMINIBI) is started.
Step 3: Use SQL Server Setup to resolve setup
SQL Server Setup performs several installation and configuration steps that cannot be performed manually. The general approach you should follow for fixing a failed setup is as follows:
- Repair the Analysis Services deployment by re-running Setup and selecting the Repair option. For instructions, see, How to: Repair a Failed SQL Server 2008 R2 Installation.
- If that does not work, uninstall and then reinstall Analysis Services. If SharePoint is working correctly, be sure that you uninstall just the Analysis Services GEMINIBI named instance, and not the Database Engine.
Troubleshoot a Command Line Installation
This section lists errors that you might encounter and solutions for the resolving them.
| Problem | Resolution |
|---|---|
Setup appears to run without errors, but there is no success statement at the end, no summary.txt file in the Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log file folder, no SQL Server program group in the Start menu, and no SQL Server instance program files in the Microsoft SQL Server folder. |
Verify that you opened a command prompt window using the Run as Administrator option. If you do not choose this option, a command line installation does not succeed. |
The following error occurs: "The credentials you provided for <servicename> are invalid. To continue, provide a valid account and password for <servicename>." |
If you copied and then modified an example script, check for mistyped account names and passwords, extra spaces or missing spaces in the command line, and extra, missing, or erroneous delimiters around the value. In general, do not bracket a value with delimiter characters (either ' or ") unless the value includes an empty space. The values for some parameters are case-sensitive. Using all lower case values produces the best results. For account names, verify the account you specified is a domain account. For most services, you cannot use a local Windows user account. Verify the account is a member of the local Administrator group. After Setup is finished, you can remove the account from this group. |
The following error occurs: "The required value for setting 'FARMADMINPORT' is missing." |
The sample script for a new farm configuration includes a /FarmAdminPort parameter for connecting to the Central Administration web application. If you do not have a specific port number that you want to use, you should delete the parameter from the command. Setup will choose a random number that is valid for a new port on the computer. |
Troubleshoot a Scale-out Deployment
In a multi-server farm, additional configuration is required to enable server connections for cross-farm communication. The following error will occur if configuration is missing or invalid.
"Failed to connect to the database server. Ensure the database server exists, is a SQL server, and that you have the appropriate permissions to access the server."
To resolve this error, try the following:
- Enable remote connections on the first server.
- Open a port in Windows Firewall to allow an incoming connection to the database server. The default port is 1434 over TCP.
Enable remote connections
- On the computer that hosts the database server, click Start, right-click Computer, and then click Properties.
- Click Remote Settings.
- Select an option that allows remote connections. Choose Allow connections from computers running any version of Remote Desktop to accept incoming connections from non-Windows Vista computers.
- Click OK.
Open a SQL Server port through Windows Firewall
Accessing a remote SQL Server database server in a farm requires that you open a port through Windows Firewall. In the following steps you will verify if an exclusion rule is already defined that allows incoming requests through the port that SQL Server listens on. If a rule is not defined, you must create one.
Enable TCP and determine the port number for the database server
- On the computer that hosts the database server, start SQL Server Configuration Manager. It is in the Microsoft SQL Server program group on the start menu.
- Open the SQL Server Native Client 10.0 Configuration folder.
- Select Client Protocols.
- Right-click TCP/IP, and then click Properties.
- Note the value for default port. In a subsequent step, you will review the existing incoming exclusion rules to determine whether a rule is already defined for this port. By default, the port is 1433.
- Open the SQL Server Network Configuration folder.
- Select Protocols for SQL Server.
- Right-click TCP/IP, and then click Properties.
- On the Protocol tab, for Enabled, select Yes.
- Click OK.
- Restart the service. To do this, select the SQL Server Services folder, right-click the database server instance, and then click Restart.
If you installed the Database Server and Gemini at the same time, the instance to restart is SQL Server (GeminiBI). Otherwise, select the SQL Server instance that runs the SharePoint databases. By default, this is SQL Server (MSSQLSERVER).
Check whether an inbound rule is already defined in Windows Firewall
- On the computer that hosts the database server, select Administrative Tools, and then select Windows Firewall with Advanced Security.
- Select Inbound Rules.
- Scroll across to the Local Port column. Click the column to sort by value. Check the list for the port on which the database server is listening. By default, it is port 1433.
If no inbound rule is defined, create one now to allow incoming connections to the database server.
Create inbound rule to allow connections and requests from remote servers
- In Windows Firewall with Advanced Security, on the Actions menu, select New Rule.
- Click Port, and then click Next.
- Click TCP.
- Click Specific local ports, and then enter the port number that the database server is listening on. Click Next.
- Click Allow the connection, and then click Next.
- Clear the check box for Public, and then click Next.
- In Name, enter SQL Server Database Engine, and then click Finish.
Check Prerequisites
When deploying Analysis Services in a new farm, you must first run the SharePoint prerequisite installer. If you need to verify which prerequisites were installed, use the following steps.
- On the Start menu, click Server Manager.
- On the Roles Summary area of the Server Manager main window, click Add Roles.
- In Server Roles, select Application Server.
- Click Add Required Features to also select the features that are required by this role.
- In Server Roles, select Web Server.
- Click Next.
- Click Next again.
- In the Roles Services page for Application Server, select Web Server (IIS) Support.
- Click Add Required Role Services to also select the features that are required by this role.
- Click Next.
- Click Next again.
- In the Roles Services page for Web Server (IIS), select IIS 6.0 Management Compatibility to add it to the list of features.
- Click Next.
- On the Confirmation page, click Install. Wait for Setup to install the roles and services.
- Click Close.
- On the Features Summary area of the Server Manager main window, click Add Features.
- Select Windows PowerShell.
- Click Next.
- Click Install.
See Also
Tasks
How to: Install Gemini Services on a New Standalone Server
Concepts
Troubleshoot Gemini Configuration
Configure Analysis Services with SharePoint Integration
Plan an Analysis Services Deployment in a SharePoint Farm