Cannot Install 64 bit SQL Server 2005 on Windows Server 2008

#11

Yes, but the process uses the same remote execution technique that the
single-pass install does.

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

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

Quote:

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 in message
news:%23Spug8tFKHA.3800 (AT) TK2MSFTNGP04 (DOT) phx.gbl...
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 in message
news:u5LzgFtFKHA.4732 (AT) TK2MSFTNGP04 (DOT) phx.gbl...
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?

#12

Geoff N. Hiten wrote:

Quote:

Yes, but the process uses the same remote execution technique that the
single-pass install does.

But on less nodes. Am wondering what check are performed to validate the
'admin' account. Can the account perform standard admin tasks like
access c$, access the Task Scheduler, run computer management.

--
Hans

#13

The problem is you start on a node with SQL installed and it remote executes
the install on the target node.

This type of problem is why the SQL team ditched the whole "remote
execution" model and changed the whole cluster install process for SQL 2008.

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

"Hans" <hans (AT) nl (DOT) invalid> wrote

Quote:

Geoff N. Hiten wrote:
Yes, but the process uses the same remote execution technique that the
single-pass install does.

But on less nodes. Am wondering what check are performed to validate the
'admin' account. Can the account perform standard admin tasks like access
c$, access the Task Scheduler, run computer management.

--
Hans

#14

Geoff N. Hiten wrote:

Quote:

The problem is you start on a node with SQL installed and it remote
executes the install on the target node.

This type of problem is why the SQL team ditched the whole "remote
execution" model and changed the whole cluster install process for SQL
2008.

I must say I am very pleased with the sql2008(sp1) install. I put
'install' and 'addnode' batchfiles files and a slipstreamed sql2008 sp1
on a file share, so my colleges can install sql whiteout thinking.

Maybe Loren should check whether sql2008 is within his reach.

--
Hans

#15

Geoff, I am logged on to the active node through a remote desktop connection
to do the install. You mentioned that no users can be logged on to remote
consoles during the installation. If I cannot remote to the server, do I
have to log on to the actual server to do the install?

Thanks,

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

Quote:

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 in message
news:u5LzgFtFKHA.4732 (AT) TK2MSFTNGP04 (DOT) phx.gbl...
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?

#16

Thanks Hans. Unfortunately SQL Server 2008 will not be within reach for the
applications this server will host for another year or two.

"Hans" <hans (AT) nl (DOT) invalid> wrote

Quote:

Geoff N. Hiten wrote:

The problem is you start on a node with SQL installed and it remote
executes the install on the target node.

This type of problem is why the SQL team ditched the whole "remote
execution" model and changed the whole cluster install process for SQL
2008.

I must say I am very pleased with the sql2008(sp1) install. I put
'install' and 'addnode' batchfiles files and a slipstreamed sql2008 sp1 on
a file share, so my colleges can install sql whiteout thinking.

Maybe Loren should check whether sql2008 is within his reach.

--
Hans

#17

You can have one connection open to the install node, but nothing else.

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

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

Quote:

Geoff, I am logged on to the active node through a remote desktop
connection to do the install. You mentioned that no users can be logged on
to remote consoles during the installation. If I cannot remote to the
server, do I have to log on to the actual server to do the install?

Thanks,

"Geoff N. Hiten" <SQLCraftsman (AT) gmail (DOT) com> wrote in message
news:urQD77tFKHA.3392 (AT) TK2MSFTNGP02 (DOT) phx.gbl...
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 in message
news:u5LzgFtFKHA.4732 (AT) TK2MSFTNGP04 (DOT) phx.gbl...
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?

#18

We tried doing the install using a domain installatoin account and did not
get the message on the "Remote Account Information Window". The network team
is currently investigating what permissions are necessary.

We prefer to do the installations with a domain account that is a local
adaministrator on all nodes. Is this possible or is it necesssary to use a
domain administrator account?

"Hans" <hans (AT) nl (DOT) invalid> wrote

Quote:

Geoff N. Hiten wrote:

The problem is you start on a node with SQL installed and it remote
executes the install on the target node.

This type of problem is why the SQL team ditched the whole "remote
execution" model and changed the whole cluster install process for SQL
2008.

I must say I am very pleased with the sql2008(sp1) install. I put
'install' and 'addnode' batchfiles files and a slipstreamed sql2008 sp1 on
a file share, so my colleges can install sql whiteout thinking.

Maybe Loren should check whether sql2008 is within his reach.

--
Hans

#19

It may be checking ownership of the SQL 2005 cluster groups. If you cannot
set members in that group, the account will fail.

This requirement is gone in SQL 2008.

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

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

Quote:

We tried doing the install using a domain installatoin account and did not
get the message on the "Remote Account Information Window". The network
team is currently investigating what permissions are necessary.

We prefer to do the installations with a domain account that is a local
adaministrator on all nodes. Is this possible or is it necesssary to use a
domain administrator account?

"Hans" <hans (AT) nl (DOT) invalid> wrote in message
news:4a806efb$0$190$c5fe704e (AT) news6 (DOT) xs4all.nl...
Geoff N. Hiten wrote:

The problem is you start on a node with SQL installed and it remote
executes the install on the target node.

This type of problem is why the SQL team ditched the whole "remote
execution" model and changed the whole cluster install process for SQL
2008.

I must say I am very pleased with the sql2008(sp1) install. I put
'install' and 'addnode' batchfiles files and a slipstreamed sql2008 sp1
on a file share, so my colleges can install sql whiteout thinking.

Maybe Loren should check whether sql2008 is within his reach.

--
Hans

#20

Doing the install using a domain adminstrator account worked but for
security reasons this is not a long-term solution.

The solution that worked for us to get the domain account with
administrative rights on both nodes to get by the "Remote Account
Information" step was to set a new SPN record for the active node. This was
done using the Windows support tool executable "setspn". Domain admin
permissions were required for this but this only needs to be set when
initially installing SQL Server.

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

Quote:

It may be checking ownership of the SQL 2005 cluster groups. If you
cannot set members in that group, the account will fail.

This requirement is gone in SQL 2008.

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

"Loren Z" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message
news:uwQOP3qGKHA.4004 (AT) TK2MSFTNGP05 (DOT) phx.gbl...
We tried doing the install using a domain installatoin account and did
not get the message on the "Remote Account Information Window". The
network team is currently investigating what permissions are necessary.

We prefer to do the installations with a domain account that is a local
adaministrator on all nodes. Is this possible or is it necesssary to use
a domain administrator account?

"Hans" <hans (AT) nl (DOT) invalid> wrote in message
news:4a806efb$0$190$c5fe704e (AT) news6 (DOT) xs4all.nl...
Geoff N. Hiten wrote:

The problem is you start on a node with SQL installed and it remote
executes the install on the target node.

This type of problem is why the SQL team ditched the whole "remote
execution" model and changed the whole cluster install process for SQL
2008.

I must say I am very pleased with the sql2008(sp1) install. I put
'install' and 'addnode' batchfiles files and a slipstreamed sql2008 sp1
on a file share, so my colleges can install sql whiteout thinking.

Maybe Loren should check whether sql2008 is within his reach.

--
Hans

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Cannot Install 64 bit SQL Server 2005 on Windows Server 2008

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering

Re: Cannot Install 64 bit SQL Server 2005 on Windows Server 2008 - 08-09-2009 , 09:00 AM

Re: Cannot Install 64 bit SQL Server 2005 on Windows Server 2008 - 08-10-2009 , 11:25 AM

Re: Cannot Install 64 bit SQL Server 2005 on Windows Server 2008 - 08-10-2009 , 11:37 AM

Re: Cannot Install 64 bit SQL Server 2005 on Windows Server 2008 - 08-10-2009 , 02:03 PM

Re: Cannot Install 64 bit SQL Server 2005 on Windows Server 2008 - 08-10-2009 , 03:39 PM

Re: Cannot Install 64 bit SQL Server 2005 on Windows Server 2008 - 08-10-2009 , 03:40 PM

Re: Cannot Install 64 bit SQL Server 2005 on Windows Server 2008 - 08-10-2009 , 03:46 PM

Re: Cannot Install 64 bit SQL Server 2005 on Windows Server 2008 - 08-11-2009 , 01:01 PM

Re: Cannot Install 64 bit SQL Server 2005 on Windows Server 2008 - 08-11-2009 , 01:10 PM

Re: Cannot Install 64 bit SQL Server 2005 on Windows Server 2008 - 08-18-2009 , 12:32 PM