locked
An error occured during the pool backend detection RRS feed

  • Question

  •  

    Hi, I'm a network designer/Implementor in and IT consultant group.

    last day I was tring to install OCS 2007 on a server but in "Step 2 : Create Enterprise Pool" (Enterprise Edition>Deploy Pool in a Consolidated Topology>Create Enterprise Pool) I got this error message as written below :

    ----------------------------------------------------------------------------------------

     

    "An error occured 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 networks is good and logon has sufficient permissions."

     

    -----------------------------------------------------------------------------------------

     

    I filled the fields with these infos :

     

    Pool Name : msg01

    Domain : messenger.org

    Pool FQDN : msg.messenger.org

    SQL Server instance : MSG\MSSQLSERVER

    -----------------------------------------------------------------------------------------

     

    My System's specifications is as described below:

     

    - Windows Server 2003 Enterprise Edition (32-bit)

    - SQL Server 2005 + SP2 (default setup - windows authentication - Set all SQL services to run - named instance : MSSQLSERVER)

    - Protocols for MSSQLSERVER : Shared Memory, Named Pipes, TCP/IP are enabled

    - Server's FQDN : msg.messenger.org

    - No firewall installed/enabled

    all of these components are installed on one server.

     

    ------------------------------------------------------------------------------------------

     

    I've also tried the installation with new SQL named instance, but it doesn't help.

    Can somebody please help me to solve the problem!

     

    Thanks,

    CyberEgo

     

    Thursday, March 13, 2008 11:51 AM

All replies

  •  CyberEgo wrote:

    I filled the fields with these infos :

     

    Pool Name : msg01

    Domain : messenger.org

    Pool FQDN : msg.messenger.org

    SQL Server instance : MSG\MSSQLSERVER

     

    For the SQL Server instance, did you try using:

     

    [FQDN]\MSSQLSERVER

     

    Also, are you positive about the instance name?

    Thursday, March 13, 2008 12:43 PM
  • yea, I've tried the [FQDN]\MSSQLSERVER but it doesn't help!

     

    Thursday, March 13, 2008 12:50 PM
  • I guess I should back up. 

     

    Is SQL running?

    Are all 3 SQL services showing a green light in your system tray?

     

    Thursday, March 13, 2008 12:59 PM
  •  

    SQL Server Integration Services

    SQL Server FullText Search (MSSQLSERVER)

    SQL Server (MSSQLSERVER)

    SQL Server Analysis Services (MSSQLSERVER)

    SQL Server Reporting Services (MSSQLSERVER)

    SQL Server Browser

    SQL Server Agent (MSSQLSERVER)

     

    is Running

    Thursday, March 13, 2008 1:31 PM
  • The user account you're using must have sufficient privileges on the SQL instance (assign sysadmin at the very least, or check all the boxes if you're still having problems) and be a member of the RTCUniversalServerAdmins group.
    Friday, March 14, 2008 12:39 AM
  • Hi frineds,

    As I was so suspicious about SQL named instance because I found out that named instance field is blank in SQL server management studio, First I defined a new instance but it failed again so I uninstalled all SQL components and Installed them again, but this time I defined an SQL named instance and everything went ok, anyway, thankyou rsi3 and Tom Pacyk for your replies.

     

    Friday, March 14, 2008 2:34 PM
  • I have the same problem as you.
    Where do I check if my SQL server is running? I can't find that in Windows Server 2003.
    I haven't got allot of expirience with it.

    Thanks in advance.
    Thursday, October 9, 2008 4:59 PM
  • Problem is solved. I thought I was using SP1, but after looking up the SQL2005 version I saw that it wasn't the case...
    After upgrading SQL with SP2 everything worked.

    Thanks for the help guy's!
    Monday, October 13, 2008 6:57 PM