Troubleshooting the ESI SharePoint Adapter

This section provides known problems and limitations for troubleshooting the ESI SharePoint Adapter.

Symptom

Prevention, resolution, or workaround

SharePoint provisioning fails when you create a web application or a SQL Server database in ESI.

  • Verify the SQL Server authentication method and try again. Integrated Security may be used instead of SQL Authentication, or vice versa.

  • Verify the username and password and try again.

  • The provisioning wizard lists all SQL instances that are installed on the server. Ensure that the correct SQL instance is selected and that the authentication mechanism matches.

SharePoint cannot connect to the named instance when the named and default instances are on the SQL server to which SharePoint connects remotely.

In a multi-server deployment where ESI and SharePoint Central Admin are on a computer that is distinct from the SQL server computer, ESI and SharePoint connect to SQL Server remotely. If the SQL Server computer has a named instance in addition to the default one, the connection to the named instance may fail. To validate the deployment scenario, ensure that SQL Management Studio can connect remotely to the target SQL Server instance.

The recommended setup is to have the remote SQL Server computer with either the default instance or the named instance, but not both. If the SQL Server computer must have both the default and named instances, then SharePoint access should be limited to the default instance.

ESI cannot open a farm.

  • Ensure that the SharePoint Foundation 2010 SP1 or SharePoint Server 2010 SP1 API is installed on the ESI host computer.

  • Verify the SQL Server or configuration database name are spelled correctly and try again.

  • If the ESI Server cannot join the farm domain controller because of an authentication failure, verify the domain settings and try again.

  • Verify that the network connection to the farm is available and functioning and try again.

  • Verify the SQL Server authentication method that is used and try again. Integrated Security may be used instead of SQL Authentication, or vice versa.

  • Verify that the correct SQL instance is used. If the farm is remote, the full SQL Server and instance name is required in the same format used by SQL Server.