dbTalk Databases Forums  

Add node to cluster

microsoft.public.sqlserver.setup microsoft.public.sqlserver.setup


Discuss Add node to cluster in the microsoft.public.sqlserver.setup forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Paul M.
 
Posts: n/a

Default Add node to cluster - 01-11-2010 , 11:35 AM






I'm setting up SQL Server 2005 64-bit on a Windows 2003 64-bit, two-node
cluster.

When I get to the point of the installation where I'm asked to authenticate,
I receive this error:
"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'm logged in to both nodes as the Domain Administrator, so I can't imagine
why the process thinks I have insufficient permissions.


If I turn off one node, I can install a clustered instance on the remaining
machine, but thereafter, trying to add the other node results in the same
error message. I have searched for four days now and can't find any root
cause for this problem. For what it's worth, we currently have both SQL
Server 2000 and Exchange 2000 clustered on other machines, so I do have some
experience at this.

As always, any help would be appreciated.

Reply With Quote
  #2  
Old   
Geoff N. Hiten
 
Posts: n/a

Default Re: Add node to cluster - 01-11-2010 , 12:00 PM






I have seen some issues where an account with inherited rights doesn't
always check out correctly. Try adding this account directly to the local
administrators group on all nodes.

This can also happen if admin shares are disabled or certain services are
not started. A lot of the "lock downs" that many sysadmins do will disable
clustering.

Stupid question. Any reason you are not using Windwos 2008 or 2008 R2?
Clustering is way better, easier, and more stable on those operating
systems.


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


"Paul M." <Paul M. (AT) discussions (DOT) microsoft.com> wrote

Quote:
I'm setting up SQL Server 2005 64-bit on a Windows 2003 64-bit, two-node
cluster.

When I get to the point of the installation where I'm asked to
authenticate,
I receive this error:
"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'm logged in to both nodes as the Domain Administrator, so I can't
imagine
why the process thinks I have insufficient permissions.


If I turn off one node, I can install a clustered instance on the
remaining
machine, but thereafter, trying to add the other node results in the same
error message. I have searched for four days now and can't find any root
cause for this problem. For what it's worth, we currently have both SQL
Server 2000 and Exchange 2000 clustered on other machines, so I do have
some
experience at this.

As always, any help would be appreciated.

Reply With Quote
  #3  
Old   
Paul M.
 
Posts: n/a

Default Re: Add node to cluster - 01-11-2010 , 05:03 PM



Geoff -

First, thanks for your reply. In answer to your last question, driver
constraints require me to stay on Windows 2003 for the time being.

As to the rest, I'm not sure which account you're suggesting I add locally.
I'm installing as Domain Administrator so permissions shouldn't be a barrier
- that's the stumper. I have explicitly added the Domain Administrator to
the Local Administrators group though, as well as the account the cluster is
running under.

This is a raw build, so I've done little configuration and nothing to
explicitly secure the system. MSDTC gets set up, as do the services required
under the "Application Server" role. If you are aware of any permissions or
services that are required, I'm happy to check them.

Thanks again for your reply.
Paul

"Geoff N. Hiten" wrote:

Quote:
I have seen some issues where an account with inherited rights doesn't
always check out correctly. Try adding this account directly to the local
administrators group on all nodes.

This can also happen if admin shares are disabled or certain services are
not started. A lot of the "lock downs" that many sysadmins do will disable
clustering.

Stupid question. Any reason you are not using Windwos 2008 or 2008 R2?
Clustering is way better, easier, and more stable on those operating
systems.


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


"Paul M." <Paul M. (AT) discussions (DOT) microsoft.com> wrote in message
news:200535CA-6C06-40C3-9667-59E0FBB638FF (AT) microsoft (DOT) com...
I'm setting up SQL Server 2005 64-bit on a Windows 2003 64-bit, two-node
cluster.

When I get to the point of the installation where I'm asked to
authenticate,
I receive this error:
"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'm logged in to both nodes as the Domain Administrator, so I can't
imagine
why the process thinks I have insufficient permissions.


If I turn off one node, I can install a clustered instance on the
remaining
machine, but thereafter, trying to add the other node results in the same
error message. I have searched for four days now and can't find any root
cause for this problem. For what it's worth, we currently have both SQL
Server 2000 and Exchange 2000 clustered on other machines, so I do have
some
experience at this.

As always, any help would be appreciated.

.

Reply With Quote
  #4  
Old   
Geoff N. Hiten
 
Posts: n/a

Default Re: Add node to cluster - 01-12-2010 , 10:30 AM



It is OK to use the Domain Administrator account to execute the install.

Do not use the Domain Administrator account as the service account for any
SQL Services. By the same token, do not use any of the built-in Domain
Groups as your service groups for SQL 2005.

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


"Paul M." <=paul=at=pensoft=dot=com=> wrote

Quote:
Geoff -

First, thanks for your reply. In answer to your last question, driver
constraints require me to stay on Windows 2003 for the time being.

As to the rest, I'm not sure which account you're suggesting I add
locally.
I'm installing as Domain Administrator so permissions shouldn't be a
barrier
- that's the stumper. I have explicitly added the Domain Administrator to
the Local Administrators group though, as well as the account the cluster
is
running under.

This is a raw build, so I've done little configuration and nothing to
explicitly secure the system. MSDTC gets set up, as do the services
required
under the "Application Server" role. If you are aware of any permissions
or
services that are required, I'm happy to check them.

Thanks again for your reply.
Paul

"Geoff N. Hiten" wrote:

I have seen some issues where an account with inherited rights doesn't
always check out correctly. Try adding this account directly to the
local
administrators group on all nodes.

This can also happen if admin shares are disabled or certain services are
not started. A lot of the "lock downs" that many sysadmins do will
disable
clustering.

Stupid question. Any reason you are not using Windwos 2008 or 2008 R2?
Clustering is way better, easier, and more stable on those operating
systems.


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


"Paul M." <Paul M. (AT) discussions (DOT) microsoft.com> wrote in message
news:200535CA-6C06-40C3-9667-59E0FBB638FF (AT) microsoft (DOT) com...
I'm setting up SQL Server 2005 64-bit on a Windows 2003 64-bit,
two-node
cluster.

When I get to the point of the installation where I'm asked to
authenticate,
I receive this error:
"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'm logged in to both nodes as the Domain Administrator, so I can't
imagine
why the process thinks I have insufficient permissions.


If I turn off one node, I can install a clustered instance on the
remaining
machine, but thereafter, trying to add the other node results in the
same
error message. I have searched for four days now and can't find any
root
cause for this problem. For what it's worth, we currently have both
SQL
Server 2000 and Exchange 2000 clustered on other machines, so I do have
some
experience at this.

As always, any help would be appreciated.

.

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.