Cluster installation problem

  •  

    Hi,

    I am getting this error while trying a fresh SQL 2000 install on Windows 2003 Server.

    "setup could not connect to the database to update cluster-specific information in the system tables" After this the Install just cleans up and comes out of the setup. Its a Active passive configuration

    Any suggestions would be appreciated.

    Thanks

    Ajay

  • Is it a named instance?

    Installation of a named instance of SQL Server 2000 virtual server on a Windows 2003-based cluster fails (815431)

    I tend to do this, named instance or not, and have not experienced issues as a result.

    K. Brian Kelley
    @kbriankelley

  • yes we are giving a name SQLA to the instance and not going with a default (local machine name) name.

    Ajay

  • Then make sure you set up aliases on all physical nodes before doing the installation as per the article. Once you've gotten at least SP3 for SQL Server 2000 on there, you can undo the aliases.

    K. Brian Kelley
    @kbriankelley

  • Thanks for the reply. I configured the client n/w utility with the virtualservername\instance name as mentioned in the article on both the nodes. Still the error does not go away. I checked the SQL*.log files. SQL is successfully configured on Node A but it craps out on Node B giving the above mentioned error.

    Also one thing I would like to mention here. The domain account that we are trying to use here to run cluster service has local administrative rights but the MSSQLServer Service has been granted only the neccessary permission in user policy(Its not local admin) Its the policy here. 

    The permissions given to that account are:

    Act as part of the operating system

    Bypass traverse checking

    Increase quotas

    Lock pages in memory

    Log on as a batch job

    Log on as a service

    Replace a process level token

     

    There are lot of messages in Event log that does not make any sense.

    The description for Event ID ( 10000 ) in Source ( Microsoft Search ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: SQL Server Fulltext (TCSQLA).

     

    please help

     

  • Guys.. I finally tried by making it a local admin account for MSSQLServer service and it worked. Well we will remove it from admin group after verifying that all neccessary permissions are there to that service account.

    Thanks for your help

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply