Re: I Surrender.....Help?
- From: Stacy Hein <shein@xxxxxxxxxxxx>
- Date: Mon, 24 Jul 2006 13:29:01 -0700
I would suggest you find out if there are domain policies that have other
restrictions for the domain service logins. I have run into where the logins
are in the local admin group but are restricted via domain policy from
logging in locally.
Hope this helps.
"Geoff N. Hiten" wrote:
Make sure that each node can resolve the names of the other nodes and the.
cluster virtual machine via DNS. Name resolution is critical to cluster
setup.
Verify the Edition of SQL you are installing. SQL 2005 Standard Edition
will only install to two nodes on a cluster. You need SQL 2005 Enterprise
Edition to build a 4-node cluster (I suspect this may be the critical
problem). I have also run into some cluster problems when a client
inadvertantly installed 32-bit SQL 2005 on a 64-bit OS platform.
Install the SQL client tools only on your primary install node. Read the
cluster install checklist and make sure to follow it completely. Finally,
check the system event logs and SQL installer logs on each node to see where
the failure is coming from. Feel free to post logs here for followup
analysis.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Jay" <Jay@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:13C169C7-6FA1-4FC0-AFDF-67A56C2FFF9F@xxxxxxxxxxxxxxxx
Geoff - Thanks so much for your reply and the checklist.
The cluster is operating 100% - All groups and resources fail-over to any
one of the 4-nodes.
Checked the networking - looks fine....(No Netbios on the Private).
The Cluster and SQL Service accounts are Domain Accounts that both belong
to
the Local Admin Groups on each node.
Task scheduler is started, and Node1 is the only one I'm currently logged
into.......
Help!!!
<G>
"Geoff N. Hiten" wrote:
Start by verifying that all of your cluster nodes can see all the
existing
resources correctly. Move the cluster group around between nodes. Move
your disk resources to each node. Check your public and private network
communication paths and configurations. Verify that the cluster service
account is a domain account with local admin rights on each node. Same
for
the SQL Server and installer account. Make sure the Windows Task
Scheduler
service is running on all nodes. Finally, log our of all consoles but
the
node you are installing from.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Jay" <Jay@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:45B32DAC-4352-4C36-9A3B-2C4D44C3BA1A@xxxxxxxxxxxxxxxx
I'm trying to install a 3+1 - SQL2005 x64 Cluster configuration on 4
nodes
of
my Win2003 Server x64 ENT DL585s.
When I load the SQL2K5 installer it loads the SCC......
The SCC consistently comes back saying that 2 nodes of my cluster are
"unavailable".
The message reads something along the lines of "SQL Server requires
Windows
2000 Service Pack 4 or Windows XP Service Pack 1 or later"
All 4 nodes were just and configured identically. I've tried a
dozentimes
and the same 2 nodes always show as "unavailable"....
If you have any idea what might be causing this I would really
appreciate
your feedback!
TIA,
- Prev by Date: Re: New Hardware, moving
- Next by Date: Re: New Hardware, moving
- Previous by thread: RE: Microsoft Search Not working
- Next by thread: Re: Cluster group and group 0
- Index(es):
Relevant Pages
|
