I am attempting to install 64 bit SQL Server 2005 on a two node Windows
Server 2008 SP2 cluster. I get to the part of the install "Remote Account
Information" where I am required to enter an user name and password that is
a valid administrator on both nodes. I enter the information of an account
that is an administrator on both nodes and I get this message:

================================================== ============================
SQL Server 2005 Setup requires administrator permissions on every cluster
node. To continue, update permissions for the account currently running
Setup, or log in with an account that has administrator permissions on every
cluster node, and then run SQL Server Setup again.

================================================== ============================

I am unable to get further in the installation. I have done many successful
cluster intalls on Windows 2003 clusters. Does anyone have any ideas on how
to solve this?

It seems like you don't have administrative privilege on nodes. Make sure
you have admin privilege on both nodes. User a Domain account with local
admin rights..


--
Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA
Houston, TX
http://blogcastrepository.com/blogs/santhosh/
http://www.sivarajan.com/publications.html


"Loren Z" <anonymous (AT) discussions (DOT) microsoft.com> wrote

The account I am running under does have administrative priviledges on both
nodes. However, this message is still appearing. Has anyone seen this
before?


"Santhosh Sivarajan" <Santhoshetmr (AT) Hotmail (DOT) com> wrote

I would like to add that the account which I am using to run the setup
belongs to the local administrators group on each node. It is not the local
administrator account on the server nodes. The local administrator account
has been disabled on each node.

When I try and run the setup I right-click on the setup file and choose "Run
as administrator". It fails. If I just double-click on the setup file and
try and go through the setup. It still fails.


"Loren Z" <anonymous (AT) discussions (DOT) microsoft.com> wrote

Start here:
http://support.microsoft.com/kb/936302

You need to explicitly add the install execution account to the
administrators group on both nodes. Sometimes the inheritance from the
Domain Admins group doesn't work. To be safe, I would manually log in to
each node using the install account.

Finally, you can have no users on remote consoles on either node during the
installation. Anyone left logged in and the installation fails.


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Loren Z" <anonymous (AT) discussions (DOT) microsoft.com> wrote

And here is a webcast on exactly how to do that install:
http://support.microsoft.com/kb/953170


--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"Loren Z" <anonymous (AT) discussions (DOT) microsoft.com> wrote

Here is a twist for you. I have a domain account I'm using to install SQL
2005 in every server's Local Admin group. I have confirmed I can log into
the server using that account. I am logged in with the account when I
attempt to install SQL 2005. I get all the way to the REMOTE ACCOUNT
INFORMATION window, which populates the account information for me. I type
in the proper password and click NEXT. I get an error stating

SQL Server 2005 Setup requires administrator permissions on every cluster
node. To continue, update permissions for the account currently running
Setup, or log in with an account that has admnistrator permssions on every
cluster node, and then run SQL Server Setup again.

I am going to try to add some Local Security Policy roles to see if that
fixes it. Otherwise, I am stumped. Any help would be appreciated.
--
Troy


"Geoff N. Hiten" wrote:

This is part of the error in the SQL Server Setup log.

MSI (c) (90!44) [10:24:49:366]: PROPERTY CHANGE: Modifying SqlLogMessage
property. Its current value is '<EndFunc Name='VerifyAdminAccount'
Return='70006' GetLastError='0'>'. Its new value: 'Username, password, domain
not accepted by ValidateAllNodeUserAccount'.



--
Troy


"Troy" wrote:

Thanks Geoff.

I watched the webcast and followed all of the advice regarding running The
cluster validation wizard and creating a new cluster group for SQL Server.
However, I still get that message and am unable to continue.

The account that I am running the execution under is in the local
administrators group on both nodes. I start the installation by
right-clicking on the setup file and choosing "Run as administrator". The
standalone local administrator account is disabled and I am not sure if this
is causing the problem. From wikipedia:

"When logging into Vista as a standard user, a logon session is created and
a token containing only the most basic privileges is assigned. In this way,
the new logon session is incapable of making changes that would affect the
entire system. When logging in as a user in the Administrators group, two
separate tokens are assigned. The first token contains all privileges
typically awarded to an administrator, and the second is a restricted token
similar to what a standard user would receive. User applications, including
the Windows Shell, are then started with the restricted token, resulting in
a reduced privilege environment even under an Administrator account. When an
application requests higher privileges or "Run as administrator" is clicked,
UAC will prompt for confirmation and, if consent is given, start the process
using the unrestricted token.[4]"

Can it be possible that on the second node it is using the restricted token?


"Geoff N. Hiten" <SQLCraftsman (AT) gmail (DOT) com> wrote

I believe that it is possible in SQL Server 2008 it is possible to do a
standalone cluster install on one node and then bring on the other node
later. Is it possible to do this with SQL Server 2005?


"Geoff N. Hiten" <SQLCraftsman (AT) gmail (DOT) com> wrote