Re: SQL 2000 Problems on One Node Only

The fact that in the error message you are getting Login Failed for user
(null) means that the Cluster service is trying to log in with Windows
Authentication, but that it has lost its access token.

Make sure that node 1 can reach the Domain Controllers and that the Windows
Time is synchronizing correctly.

Since both the Cluster and SQL Server service accounts are Local
Administrators, there shouldn't be anything at the NTFS or registry level;
however, in your GPO's, have you given all of the USER ACCESS RIGHTS to
either the Local Administrators group or these service accounts explicitly?

Also, how is SQL Server set up to allow Local Administrators to log into SQL
Server? Did you leave the BUILTIN\Administrators group? You shouldn't, but
should give explicit access to these two service accounts.

The SQL Server service account will need to be a SQL Server system
administrator; however, the Cluster service account will only need to login,
no other privileges. It only needs to run SELECT @@SERVER as the IsAlive
check.

Sincerely,


Anthony Thomas


--

"Jerry" <digjrice@xxxxxx> wrote in message
news:1128915696.471779.231960@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thank you for replying! I checked both the cluster account (a domain
> account that is in the local administrator group on both nodes), and
> the SQL Server account (currently running under my Domain Admin account
> until we get this working, so it is also in the local Administratos
> group at this point) and they are set up identically. The SQL Server
> service does start up for a short period of time, but then it starts
> getting those errors and clustering pulls it back down. The GPO we
> apply is the exact same one for both nodes, so I don't think it's
> anything in there, but I did check it over to be sure.
>
> Any further help is greatly appreciated! Thanks...
>


.

Relevant Pages

  • Re: Service Accounts on SQL Server, Best Practices
    ... SQL Server and SQL Server Agent service accounts do not need to be a local administrator or domain administrator for Failover Clustering on Windows 2000 ... If the service account for SQL Server is not an administrator in a cluster, the administrative shares cannot be deleted on any nodes of the cluster. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Sql server 2005 clustered service group
    ... I always do this as part of cluster setup (prepoulate the groups with the ... Jasper Smith (SQL Server MVP) ... add accounts to the domain groups. ... needs rights to add the service accounts to the domain group ...
    (microsoft.public.sqlserver.setup)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Now, for the first problem, adding the 3rd node as a member of the cluster. ... You then installed a 2nd instance of SQL Server. ... DBC01 (Disks, SQL Server resources) ... Install RTM SS2K and designate the node membership. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Cluster will not fail over.
    ... > As far as the TCP/IP issue goes, you had to rebuild the cluster and were ... > able to restore the master database. ... > a cluster installation you'll have to revisit. ... >> This worked bringing up the sql server in minimal mode. ...
    (microsoft.public.sqlserver.clustering)
  • Re: active/passive with multiple instances
    ... An Active/Passive cluster is always called that and never Passive/Active. ... There is only 1 SQL Server per instance:) Just so other don't get confused. ... It does matter about the hardware, to achieve true HA it needs to happen at ... a SQL Server DBA plain and simply doesn't care about it being ...
    (microsoft.public.sqlserver.clustering)