locked
Error setting up Pool RRS feed

  • Question

  •  

    Sirs,

     

    When setting up a new test environment for ocs 2007 i got the following error:

     

    ---------------------------
    Error
    ---------------------------
    An error occurred during the pool backend detection:

     

    Pool backend discovery failed.

     

    Failed to open SQL database.

     

     

    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.
    ---------------------------
    Cancel   Try Again   Continue  
    ---------------------------

     

    OCS machine is running windows server 2003 x86 R2 SP2

    DB Machine is running server 2008 with sql 2008 all firewall zones are set to allow

    Sharepoint databases which are on the same DB machine can be accessed fine.

     

    Backwards compatibility pack is installed on ocs machien

    Even management tools are installed and i can successfully connect from ocs machine to db machine

     

    On the databse server i get successfull logons :

    Login succeeded for user 'DOMAIN\admin'. Connection made using Windows authentication. [CLIENT: 192.168.1.61]

    FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.

     

    OCS machine account has DBcreator and Security admin rights, account that is logged on is domain admin.

     

    Any help is appreciated!

     

    Kind regards

    Marquisian

    Saturday, September 6, 2008 1:40 PM

Answers

  • Ok, with help of some other articles in this forum i figured out the solution :

     

    - create the database rtcconfig on the sql server

    - run poolcfgdbsetup.wsf /clean /slqserverdb02 /serverrole:EP /verbose

     

    Code Snippet

    Microsoft (R) Windows Script Host Version 5.6
    Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

    Connecting to SQL Server on db02
    SQL validation: Reconfigure encountered no errors, and SQL version is acceptable
    : 9.00.3068.00
    Opened database rtcconfig
    Restricting access and dropping database.
    Dropped database rtcconfig
    Creating database rtcconfig
        DbFile : PhysicalName = d:\program files\microsoft sql server\mssql.1\mssql\
    data\rtcconfig.mdf
        LogFile: PhysicalName = d:\program files\microsoft sql server\mssql.1\mssql\
    data\rtcconfig.ldf
    Executing batch dbcommon.sql on rtcconfig
    Executing batch PoolCfgTypes.sql on rtcconfig
    Executing batch PoolCfgTableSchema.sql on rtcconfig
    Executing batch PoolCfgMessages.sql on rtcconfig
    Executing batch PoolCfgSproc.sql on rtcconfig
    Executing batch PoolCfgInstances.sql on rtcconfig
    Executing resource DbReIndex on rtcconfig
    Setting security in rtcconfig
    Successfully added logins and db users to the specified database roles in rtccon
    fig
    Setting Db schema version to 46
    Setting Db sproc version to 46

     

     

    Now go back to the setup gui and create your enterprise pool, keep the database locations to the defaults and configuring the meeting, metadata and archiving shares. The enterprise pool will now be created successfully and you can continue the setup.

     

    Hope it will help other people running into this strange problem.

    For detailed instructions : http://dwjack.spaces.live.com/default.aspx


    Regards

    Marquisian

    Sunday, September 14, 2008 1:14 PM

All replies

  • Extra Information :

     

    I installed sql express 2005 SP2 on the OCS machine and STILL receive the same error when trying to create the pool

    Corrupt installation files or ?? anybody? I never ever had any trouble setting up ocs before, installed it more then 6 times on the same hardware, same software..

     

    help? Smile

     

     

    Saturday, September 6, 2008 8:26 PM
  • Are you attempting to install a consolidated Standard Edition server or an Enterprise Edition server?  Only the OCS Enterprise edition works with standard SQL server backend, and the OCS Standard edition works with a local installation of SQL Express, which it deploys automatically.  Running an Enterprise front-end node with a local SQL Express (or MSDE) installation is not supported.

     

    If you've been successful in the same scenario before, you might want to get re-image the server and run through the process again, assuming you don't have a DNS problem preventing the server from locating the SQL backend.

    Monday, September 8, 2008 12:33 PM
    Moderator
  • I'm setting up consolidated enterprise edition so, first server is frontend, 2nd server is mediation gateway, 3th server is sql server. The strange thing is that the same error message appears if you use the non supported local sql express installation and also if you use the remote sql 2008 server.

    All backward compatibility files are/were installed on the frontend

    I'll try to setup a new clean frontend but if you could shed some light on the error message?

     

    thanks for your reply, really appreciate it!

     

    regards

    Marquisian

     

    Tuesday, September 9, 2008 10:35 PM
  • hi

    till now, OCS 2k7 Server does not support SQL 2k8;

    the following links about "OCS Server 2k7 system requirement", hope it helps;

    http://technet.microsoft.com/en-us/library/bb870392.aspx

     

    if there is anything unclear,please free time to tell me, thanks;

     

    best regards

    -Jack

    Wednesday, September 10, 2008 8:02 AM
  • Sir,

     

    Thank you for the requirements, i knew these allready and i used ocs before on the sql 2008 beta with the backwards compatibility MSI installed. I just now installed a sql server 2005 on server 2003 x64, also i took a cliean windows server 2003 x86 machine, tried to create the pool and it gave the error that it must be sql 2005 sp1 (just for checking purposes) Installed service pack 2 of sql and tried to create the pool, and what do you think the error message was ? ;-)

     

     

    I tried to use the lcscmd command to do it on commandline (to get more info and the failure code was :

     

    Failure [0xC3EC783E] failed to open sql database.

     

    So there must be something else wrong, all requirements are met.

     

    regards

    Marquisian

    Wednesday, September 10, 2008 10:48 PM
  • Some extra troubleshooting steps i took using a windows server 2003 x64 with sql 2005 SP2 x64 and a windows server 2003 x86 with OCS (at least..trying to get it to install..)

     

     

    In the setup\dbsetup directory are the scripts that create the database files, when i run these on the ocs server

    :

    Code Snippet

    cscript dbsetup.wsf /clean /sqlserver:db02

    Microsoft (R) Windows Script Host Version 5.6
    Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

    Connecting to SQL Server on db02
    Restricting access and dropping database.
    Dropped database rtcdyn
    Creating database rtcdyn
    Executing resource SetDbOptions on rtcdyn
    Executing batch dbcommon.sql on rtcdyn
    Executing batch types.sql on rtcdyn
    Executing batch roles.sql on rtcdyn
    Executing batch dbrtcdyn.sql on rtcdyn
    Restricting access and dropping database.
    Dropped database rtc
    Creating database rtc
    Executing resource SetDbOptions on rtc
    Executing batch dbcommon.sql on rtc
    Executing batch types.sql on rtc
    Executing batch roles.sql on rtc
    Executing batch dbrtc.sql on rtc
    Executing resource LinkStaticAndDynamicDatabases on rtc
    Executing resource DbReIndex on rtc
    Successfully added logins and db users to the specified database roles in rtc
    Successfully assigned security to rtcdyn from rtc

     

     

     

    The databases for rtc and rtcdyn are created. (so no errors!)

     

    Code Snippet

    cscript poolcfgdbsetup.wsf /clean /sqlserver:db02


    Microsoft (R) Windows Script Host Version 5.6
    Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

    Connecting to SQL Server on db02
    Failed to open database rtcconfig

     

     

     

    It fails. so it's definetly not a connection or rights issue.

     

    regards

    Marquisian

    Thursday, September 11, 2008 9:37 PM
  • Ok, with help of some other articles in this forum i figured out the solution :

     

    - create the database rtcconfig on the sql server

    - run poolcfgdbsetup.wsf /clean /slqserverdb02 /serverrole:EP /verbose

     

    Code Snippet

    Microsoft (R) Windows Script Host Version 5.6
    Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

    Connecting to SQL Server on db02
    SQL validation: Reconfigure encountered no errors, and SQL version is acceptable
    : 9.00.3068.00
    Opened database rtcconfig
    Restricting access and dropping database.
    Dropped database rtcconfig
    Creating database rtcconfig
        DbFile : PhysicalName = d:\program files\microsoft sql server\mssql.1\mssql\
    data\rtcconfig.mdf
        LogFile: PhysicalName = d:\program files\microsoft sql server\mssql.1\mssql\
    data\rtcconfig.ldf
    Executing batch dbcommon.sql on rtcconfig
    Executing batch PoolCfgTypes.sql on rtcconfig
    Executing batch PoolCfgTableSchema.sql on rtcconfig
    Executing batch PoolCfgMessages.sql on rtcconfig
    Executing batch PoolCfgSproc.sql on rtcconfig
    Executing batch PoolCfgInstances.sql on rtcconfig
    Executing resource DbReIndex on rtcconfig
    Setting security in rtcconfig
    Successfully added logins and db users to the specified database roles in rtccon
    fig
    Setting Db schema version to 46
    Setting Db sproc version to 46

     

     

    Now go back to the setup gui and create your enterprise pool, keep the database locations to the defaults and configuring the meeting, metadata and archiving shares. The enterprise pool will now be created successfully and you can continue the setup.

     

    Hope it will help other people running into this strange problem.

    For detailed instructions : http://dwjack.spaces.live.com/default.aspx


    Regards

    Marquisian

    Sunday, September 14, 2008 1:14 PM
  • Thanks Marquisian,

     

    You hit a home run!

     

    Once again, I am amazed that a multi-billion dollar software company can create such dog poo and puts its customers through such hassles.

     

    Good luck,

    Mac

     

    Tuesday, December 9, 2008 7:36 PM
  • I had a similar problem when installing the Archiving Server, probably due to various oversights on my behalf.
    I did the same as you guys, creating the required DB on the SQL server, and then when it came to validating the role, I checked the checkbox to over-write the existing DB.
    Tuesday, May 12, 2009 10:58 PM