Scenario is Windows 2003 Enterprise and SQL Server 2000 Enterprise.

I need to know what rights, policies and / or other configurations are
needed for SQL Server to install on a cluster.
(for that matter, any SQL Server install on / in a 2003 environment). It
seems that things may have changed somewhat with 2003.

We trying to install today with a sql service domain account added to the
local admin group of both nodes of the cluster. Cluster service login was
already configured. We tried logging in as the sql service account and the
install failed. The admin added the sql service account as part of the
domain admin group and still wouldn't install. Finally, the domain admin
(who is enterprise domain admin) used his login to install and it worked, we
still used the sql service domain account as the services login. We have had
a lot of difficulty in this type of install. The admin say it is a "security
thing" but won't elaborate. I know about a few of the policy setting and
rights things, but I need a real and better understanding of **exactly**
what we need, to make this work properly.

Hi Frankm,

I learned you failed to install SQL Server Clustering using SQL Service
Account. Based on my experience, it likes a windows installation permission
problem. Could you please provide the detailed error message? When did the
error occur? Please describe it in detail.

As I know, there are a few Windows-level accounts that need to be
configured prior to installing both the server cluster and the SQL Server
2000 virtual server.

a. An account must be created for the administration and ownership of the
server cluster. It must be a valid domain administrator account. This
account is also used during the installation of the SQL Server 2000 virtual
server.
b. At least one account must be created that will administer the SQL Server
as well as the SQL Server Agent. This can be two separate accounts, and
does not need to be a domain administrator, but a valid domain account. If
desired, it can be the same as the account listed in the prior bullet
point, but it is helpful to keep the accounts separate.

For more information regarding this issue, please refer to the following
article:
SQL Server 2000 Failover Clustering
http://www.microsoft.com/technet/pro.../failclus.mspx

I also found the following articles for your reference
How to Install SQL Server 2000 Clustering
http://www.sql-server-performance.co...g_install_main.
asp

269229 How to Manually Re-Create the Cluster Service Account
http://support.microsoft.com/?id=269229

SQL Server 7.0 and 2000 Clustering Resources
http://www.sql-server-performance.co..._resources.asp

283811 HOW TO: Change the SQL Server or SQL Server Agent Service Account
http://support.microsoft.com/?id=283811

I am looking forward to hearing from you soon.
Regards,

Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Thank you for your response...

The error occurred during the part of the install that said "Setup is
creating virtual server resources on the cluster".
The error was: "The cluster resource failed to come online. If extended
error information was reported by the cluster service it can be obtained in
the Event Log."
After clicking OK on the error message, the install then said "Setup is
performing cleanup operations on cluster nodes".

The install was never completed. To clean up, We had to remove the registry
entry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer and remove Microsoft
SQL Server from Program files.






""Yuan Shao"" <v-yshao (AT) online (DOT) microsoft.com> wrote

Hi Frankm,

Do you install a named instance of Microsoft SQL Server 2000 virtual
server? If so, please check to see if the following article addresses your
problem.

815431 PRB: Installation of a Named Instance of SQL Server 2000 Virtual
Server
http://support.microsoft.com/?id=815431

Based on my experience, this error message "The cluster resource failed to
come online¡*" is general. Please check the sqlclstr.log and cluster.log
and provide the detailed error information from these log files so that I
can narrow down this issue.

Also, such issues tend to be complex and take up extensive research time.
I'd like to set your expectations that it may take a while for us to help
you narrow down the problem and we may eventually redirect you to PSS to
continue working with a dedicated Support Professional. If this is
critical, I'd recommend contacting PSS and opening a Support incident
troubleshoot this further. If you need any help in this regard, please let
me know.

Regards,

Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.