This article has been archived. It is offered "as is" and will no longer be updated.
When you use the Microsoft Office Communications Server Deployment Wizard to create a new Enterprise pool on a front-end server, you receive the following error message:
Detecting the existence of the pool backend --------------------------- Error --------------------------- An error occurred during the pool backend detection: Pool backend discovery failed. Failed to start SQL service or invalid SQL instance. This can happen due to network or credential problems. Please make sure network is good and logon has sufficient permissions. Click 'Cancel' to close the wizard. Click 'Try Again' to go back to the previous page and enter a different pool backend instance. Click 'Continue' to move forward. ---------------------------
This problem may occur if the back-end server that is running Microsoft SQL Server is not configured to accept remote connections.
To verify that the SQL Server installation is configured to accept remote connections, follow these steps:
On the front-end server, create a Data Link file (*.udl). For example, create a file that is named Test.udl, and then save it on the desktop.
Double-click the newly created file to set the properties for the Data Link.
On the Provider tab, click Microsoft OLE DB Provider for SQL Server in the OLE DB Provider(s) list.
On the Connection tab, type the SQLServerName\InstanceName in the Select or enter a server name box.
Note SQLServerName\InstanceName is a placeholder for the SQL Server name and the Instance name.
Under Enter information to log on to the server, select Use Windows NT Integrated security.
Note When you select this option, the connection will be tested with the currently logged-on user. Make sure that you use the same account that you use for Communication Server Setup to log on to the front-end server.
Click Test Connection.
You receive the following error message if the back-end server that is running SQL Server is not configured to accept remote connections:
--------------------------- Microsoft Data Link Error --------------------------- Test connection failed because of an error in initializing provider. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. ---------------------------
To resolve this issue, you must configure SQL Server 2005 to allow for remote connections. To do this, follow these steps.
Note The steps that are listed in this section for step 1 also work to configure remote connections for SQL Server 2008.
Enable remote connections on the instance of SQL Server to which you want to connect from a remote computer:
Click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
Connect to the appropriate instance that you want to use for pool creation.
In SQL Server Management Studio, right-click the appropriate SQL Server, and then click Properties.
In the Server Properties page, click Connections under Select a page.
Under Remote server connections, click to select the Allow remote connections to this server check box, and then click OK.
Turn on the SQL Server Browser service. To do this, follow these steps:
Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Surface Area configuration.
On the SQL Server 2005 Surface Area Configuration page, click Surface Area Configuration for Services and Connections.
On the Surface Area Configuration for Services and Connections page, click SQL Server Browser under Select a component and then configure its services and connections.
In the Startup type list, click Automatic, and then click Apply.
Note When you click the Automatic option, the SQL Server Browser service starts automatically every time that you start Windows.
Click Start, and then click OK.
SQL Server 2008 does not include the Surface Area Configuration tool under the Configuration Tools menu. It was removed because of security considerations.
The SQL Server 2008 SQL Server Browser service can be set to start automatically by using the local Services management console (services.msc)
For more information about how to configure SQL Server 2005 to allow for remote connections, click the following article number to view the article in the Microsoft Knowledge Base:
914277 How to configure SQL Server 2005 to allow remote connections