Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
SQL setup errors and questions [0xC3EC783C] RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    what account needed to be the owner of the database on the backend server.  Should it be the person installing the instance or should it be a service account.

     

    In LCS 2005 there was a place to supply the credentials to connect to the backend, I do not see that in OCS 2007.  I was receiving a nondescript WMI error when installing the frontend OCS server (consolidated).

     

    I am also receiving an error message now when I tried to reinstall the pool database.  I cleaned up unused databases and reinstalled the pool.

    When installing the pool I get this error.

     

    “Failure
    [0xC3EC783C] An error occurred while running DB script.

    “

     

    The only thing I can find on it is a server 2000 error with Windows Script Host 5.6.

     

    This is a new database, named instance.

    Friday, June 15, 2007 6:12 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    The script cannot connect to the database at all. 

    The database may have gone funky.  I will recreat a database then try this process again and get back to you on how this worked.

    Thanks for the help

     

     

    Much appreciated.

     

    This is about all the output I could pull form running the script...

     

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

    Connecting to SQL Server on \\testexch-sql\ocs
    Error connecting (
      name:        Error
      description:
      number:      -2147467259
      message:    
    )
    Attempting to start SQL Server and connect...

     

    after the start and connect it says failed, out of range, invalid handle.

     

     

    -Caleb

     

    Monday, July 23, 2007 2:07 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

     

    Connectivity issues due to logic failure can be the cause of this type. For instance if you are installing the OCS pool and databases onto a custered SQL 2005 / 2000 Server and the Clustered NIC configuration is mal-configured. To create the OCS 2007 pool and creates the SQL 200x databases you will need to be a member of the Domain Admins and inherently the RTCUniversalServer Admins group.

     

    If you have not tried this already install the OCS 2007 Administartive tools onto the SQL Server and then create the OCS 2007 Pool from the console of the OCS 2007 sever. This will eliminate network issues as a source of thre problem. The credentials that you are logged into the SQL Server 200x with will be the ones that will be used to update the SQL Server login / security information that will allow the creation of the OCS / RTC databases.

     

    Please provide me with the details of your SQL Server installation.

     

    Version of SQL Server

    Operarating system version that SQL Server is installed on

    SP levels for the Server OS and the SQL Server install

     

    Ans anything else that you feel I may need.

     

    Thanks,

     

    Mike Adkins OCS beta support team

    Thursday, July 12, 2007 11:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    "Domain Admins and inherently the RTCUniversalServer Admins group"

    i am in both

     

     

    " onto a custered SQL 2005 / 2000 Server and the Clustered NIC configuration is mal-configured."

    No cluster, two single servers one backend one frontend.

     

     

    SQL 2005 sp2

    OS windows 2k3 sp2

     

     The two servers are on different subnets (i am reaching now) but I don't think that would matter.

    They can ping and should be able to commnicate to each other just fine.  (the LCS server and SQL server are on different subnets too, its the same SQL server and the VMs for each product are on the same host)

     

    It is also a named instance not the default instance of SQL that I am trying to run OCS pool on. 

     

    Any ideas or more info would help.

    THanks

     

    Monday, July 16, 2007 6:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Is the OCS server on a windows 2003 SP2 server also? There ahve been a lot of people having issues with SP2.
    Monday, July 16, 2007 6:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    it is now.

     

    it was not when i started trying this.

     

     

    Monday, July 16, 2007 7:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

     

    When you are going through the OCS 2007 pool creation wizard you are prompted to enter the name of the SQL Server 2005 named instance. You should enter the SQL server named instance name in the following format e. g. MySQLServer\MyNamedInstance

     

    Now that I know that you are working with a new installation of SQL Server 2005. I would like you to make sure that the Network connection protocols are enabled.

     

    a. Open the SQL Server 2005 configuration manager and locate "SQL Server 2005 Network Configuration"

     

    b. Expand this and highlight "Protocols for MSSQLServer"

     

    c. Make sure that Named Pipes, TCP\IP and Shared Memory are enabled

     

    d. Now make sure that the client protocols are enabled

     

    e. Located and expand SQL Native Client Configuration

     

    f. Highlight Client protocols

     

    g. Make sure that Shared Memory and VIA are disabled and TCP/IP along with Named Pipes are enabled

     

    h. restart the MSSQLServer service

    Monday, July 16, 2007 10:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I did the above suggestions.

     

    I now get

    Failure
    [0xC3EC783C] An error occurred while running DB script.

     

    This is while running the Pool setup on the SQL server, from the SQL server. On instance testexch-sql\ocs.

    It can find the database but it fails in doing anything with it.

     

    So now it seems the install has taken a step or two back.

     

    The OCS server cannot contact the database, it can ping the SQL server, no firewalls.

     

    I have been juggling this very vague error intermittenly between installing LCS and OCS....

     

    Any ideas on a cause?

     

    I have created a pool once and had the adding of a server fail (original error in post) now I am getting a DB script error.

    Tuesday, July 17, 2007 8:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

     

    I have reseached our KB on the error that you are getting and it usually occurs when issues with the file structure impede the script that writes the database. The scipt is named poolcfgdbsetup.wsf and is located in the OCS 2007 install folders c:\office communications server_Eval\EnterpriseEdition\setup\i386\dbsetup. You can run this script from its command prompt and it should provide us with a screen full of information and most likely the lines of the script that run just before the error occurs. We can use this step as a last resort if you feel uncomfortrable with it.

     

    c:\office communications server_Eval\EnterpriseEdition\setup\i386\dbsetup\>csript  poolcfgdbsetup.wsf  /SQLServer:\\servername\instance

     

    If you have not tried this already when you are using the OCS application to deploy the new pool then please check the dbexists option to force the application to write the database information.

     

    I would like a copy of the error log that is written when the pool configuration fails. Please zip it up and attach it to this issue.

     

    Thanks,

     

    Mike Adkins

    Thursday, July 19, 2007 2:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The script cannot connect to the database at all. 

    The database may have gone funky.  I will recreat a database then try this process again and get back to you on how this worked.

    Thanks for the help

     

     

    Much appreciated.

     

    This is about all the output I could pull form running the script...

     

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

    Connecting to SQL Server on \\testexch-sql\ocs
    Error connecting (
      name:        Error
      description:
      number:      -2147467259
      message:    
    )
    Attempting to start SQL Server and connect...

     

    after the start and connect it says failed, out of range, invalid handle.

     

     

    -Caleb

     

    Monday, July 23, 2007 2:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Caleb,

     

    Let me know if you need more assistance after you rebuild your SQL Server.

     

    Thanks,

     

    Mike Adkins

    Monday, July 23, 2007 8:44 PM