Clustering SQL Server 2000 Analysis Services

We are in the process of deploying AS on a 2-node Active-Passive SQL Server
2000 MSCS cluster. I understand there is a MS white paper on how to cluster
it which requires lots of manual changes. If we were to follow this paper,
would it be possible to have the AS tools shared across with other SQL
virtual servers on the same cluster? Any experiences with this configuration
are appreciated.
NewsgroupUser wrote:

> We are in the process of deploying AS on a 2-node Active-Passive SQL Server
> 2000 MSCS cluster. I understand there is a MS white paper on how to cluster
> it which requires lots of manual changes. If we were to follow this paper,
> would it be possible to have the AS tools shared across with other SQL
> virtual servers on the same cluster? Any experiences with this configuration
> are appreciated.
I've used reciently that paper (http://support.microsoft.com/?kbid=308023)
with a virtual cluster over Microsoft Virtual Server 2005/Win2K3, and
really works.
I've tested failover and no problems..
coke.cl [-en-] gmail.com
http://www.foto-digital.cl/

Clustering Resource depencies

Hello,

With SQL2000 configured with MSCS, we had to stop the SQL service to add additional disk in the SQL Cluster group (in order to use these disks for databases for example).. this was due to the dependencies between the resources.
Do we still have the same issue with SQL2005 running on the cluster? Does the new mountpoint support help in this scenario?
Thanks
Jerome

Yes, the same issue does exist with SQL Server 2005 when adding disks. The new mountpoint support does not really help in this scenario as the mountpoint disk should also be added as a dependent disk to the resource group. It is possible to add the mountpoint without adding the disk to the resource group, but in that case the loss of the disk would not be detected by the cluster service; the SQL Server would attempt to continue running even without the disk (and mountpoint).

Thanks,

Don

Clustered SQL 2000

I am currently running a SQL 2000 Ent Server sitting on a MSCS running W2K3 Ent Edition.

One of the nodes is giving me problems, and I suspect that it is due to the build.

I want to evict the offending from the cluster and then rebuild the OS from scratch, and then rejoin the cluster.

My question then is how do I install SQL 2000 Server, up to tha same revision as the existing node, on the newly installed node without overwritting any of the existing data?you should be able to do so just back up your databases system and user
when you reinstall sql server
the advanced options will prompt you for the cluster install.
but as you already know. you will have to update the installation to be as current in version as your existing node.

ClusterBack and Restore

What's the best way to backup cluster and restore it incase of outage?
TIA
Env: MSCS 2000
OS: Win2000 Adv Srv
SQL2k
System State backups of the nodes, $ backup of the shared disks, SQL file
backup to a shared disk. Test, test, test. To know if you have everything
for a restore, perform one on your test cluster.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
"Vai2000" <nospam@.microsoft.com> wrote in message
news:%23tS7tk1IGHA.3752@.TK2MSFTNGP11.phx.gbl...
> What's the best way to backup cluster and restore it incase of outage?
> TIA
> Env: MSCS 2000
> OS: Win2000 Adv Srv
> SQL2k
>
|||Shouldn't we use the Cluster SDK API for backup?
BackupClusterDatabase
RestoreClusterDatabase
TIA
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:uA0rX44IGHA.3452@.TK2MSFTNGP12.phx.gbl...
> System State backups of the nodes, $ backup of the shared disks, SQL file
> backup to a shared disk. Test, test, test. To know if you have everything
> for a restore, perform one on your test cluster.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> "Vai2000" <nospam@.microsoft.com> wrote in message
> news:%23tS7tk1IGHA.3752@.TK2MSFTNGP11.phx.gbl...
>
|||Cluster Aware backup software, no clue on API's - I am not a programmer!
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
"Vai2000" <nospam@.microsoft.com> wrote in message
news:eX7Bzf6IGHA.3100@.tk2msftngp13.phx.gbl...
> Shouldn't we use the Cluster SDK API for backup?
> BackupClusterDatabase
> RestoreClusterDatabase
> TIA
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:uA0rX44IGHA.3452@.TK2MSFTNGP12.phx.gbl...
>

Cluster/SQL 2005/1 node install

We have setup a MSCS with no problem. Have a SAN with mounted volumes and
installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
yet, but we are planning for the future(2008) when we will have a second node.
The installation goes fine. No problems. It ends saying the startup of the
service(s) failed, you will have to start them manually from the Cluster
Administration.
We go to the Cluster Administration and right-click to Bring Online. It
still fails.
Event Log
[sqsrvres] ODBC sqldriverconnect failed
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
principal name is incorrect.
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]Cannot generate SSPI context
SQL Log:
2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
(X64)
Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
2007-03-21 15:00:51.05 Server All rights reserved.
2007-03-21 15:00:51.05 Server Server process ID is 5644.
2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
PM (UTC). This is an informational message only; no user action is required.
2007-03-21 15:00:51.05 Server Registry startup parameters:
2007-03-21 15:00:51.05 Server -d
M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-03-21 15:00:51.05 Server -l
M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
informational message; no user action is required.
2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
memory privilege was not granted.
2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
distributed transactions involving Microsoft Distributed Transaction
Coordinator (MS DTC). This is an informational message only. No user action
is required.
2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
in the endpoint configuration.
2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
informational message only. No user action is required.
2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
is running the server is 'SVR-SQL-yyy'. This is an informational message
only. No user action is required.
2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
disabled or not configured.
2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
is disabled or not configured.
2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
2007-03-21 15:00:53.47 Server A self-generated certificate was
successfully loaded for encryption.
2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
<ipv4> 1433].
2007-03-21 15:00:53.49 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
2007-03-21 15:00:53.50 Server The SQL Network Interface library could
not register the Service Principal Name (SPN) for the SQL Server service.
Error: 0x2098. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message.
Further action is only required if Kerberos authentication is required by
authentication policies.
2007-03-21 15:00:53.50 Server SQL Server is now ready for client
connections. This is an informational message; no user action is required.
2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
has completed. This is an informational message only. No user action is
required.
2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
informational message only. No user action is required.
Thanks and God Bless,
ThomBeaux
The service account did not have the:
(local policy) - Act as part of the OS
Thanks and God Bless,
ThomBeaux
"ThomBeaux" wrote:

> We have setup a MSCS with no problem. Have a SAN with mounted volumes and
> installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
> yet, but we are planning for the future(2008) when we will have a second node.
> The installation goes fine. No problems. It ends saying the startup of the
> service(s) failed, you will have to start them manually from the Cluster
> Administration.
> We go to the Cluster Administration and right-click to Bring Online. It
> still fails.
> Event Log
> [sqsrvres] ODBC sqldriverconnect failed
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
> principal name is incorrect.
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]Cannot generate SSPI context
>
> SQL Log:
> 2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
> (X64)
> Oct 14 2005 00:35:21
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
> 2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
> 2007-03-21 15:00:51.05 Server All rights reserved.
> 2007-03-21 15:00:51.05 Server Server process ID is 5644.
> 2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
> 'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
> 2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
> using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
> PM (UTC). This is an informational message only; no user action is required.
> 2007-03-21 15:00:51.05 Server Registry startup parameters:
> 2007-03-21 15:00:51.05 Server -d
> M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
> 2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
> 2007-03-21 15:00:51.05 Server -l
> M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
> 2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
> base (=7). This is an informational message only. No user action is required.
> 2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
> informational message; no user action is required.
> 2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
> memory privilege was not granted.
> 2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
> allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
> mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
> mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
> Distributed Transaction Coordinator (MS DTC). This is an informational
> message only. No user action is required.
> 2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
> distributed transactions involving Microsoft Distributed Transaction
> Coordinator (MS DTC). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
> in the endpoint configuration.
> 2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
> 2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
> database 'master' (1). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
> 2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
> 2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
> 2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
> is running the server is 'SVR-SQL-yyy'. This is an informational message
> only. No user action is required.
> 2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
> 2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
> 2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
> disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
> is disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
> 2007-03-21 15:00:53.47 Server A self-generated certificate was
> successfully loaded for encryption.
> 2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
> <ipv4> 1433].
> 2007-03-21 15:00:53.49 Server Server local connection provider is ready
> to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
> 2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
> accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
> 2007-03-21 15:00:53.50 Server The SQL Network Interface library could
> not register the Service Principal Name (SPN) for the SQL Server service.
> Error: 0x2098. Failure to register an SPN may cause integrated authentication
> to fall back to NTLM instead of Kerberos. This is an informational message.
> Further action is only required if Kerberos authentication is required by
> authentication policies.
> 2007-03-21 15:00:53.50 Server SQL Server is now ready for client
> connections. This is an informational message; no user action is required.
> 2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
> 2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
> transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
> has completed. This is an informational message only. No user action is
> required.
> 2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
> informational message only. No user action is required.
>
> --
> Thanks and God Bless,
> ThomBeaux

Cluster/SQL 2005/1 node install

We have setup a MSCS with no problem. Have a SAN with mounted volumes and
installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
yet, but we are planning for the future(2008) when we will have a second node.
The installation goes fine. No problems. It ends saying the startup of the
service(s) failed, you will have to start them manually from the Cluster
Administration.
We go to the Cluster Administration and right-click to Bring Online. It
still fails.
Event Log
[sqsrvres] ODBC sqldriverconnect failed
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
principal name is incorrect.
[sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
message = [Microsoft][SQL Native Client]Cannot generate SSPI context
SQL Log:
2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
(X64)
Oct 14 2005 00:35:21
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
2007-03-21 15:00:51.05 Server All rights reserved.
2007-03-21 15:00:51.05 Server Server process ID is 5644.
2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
PM (UTC). This is an informational message only; no user action is required.
2007-03-21 15:00:51.05 Server Registry startup parameters:
2007-03-21 15:00:51.05 Server -d
M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-03-21 15:00:51.05 Server -l
M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is required.
2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
informational message; no user action is required.
2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
memory privilege was not granted.
2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
provides a description of the NUMA configuration for this computer. This is
an informational message only. No user action is required.
2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
distributed transactions involving Microsoft Distributed Transaction
Coordinator (MS DTC). This is an informational message only. No user action
is required.
2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
in the endpoint configuration.
2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
informational message only. No user action is required.
2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
is running the server is 'SVR-SQL-yyy'. This is an informational message
only. No user action is required.
2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
disabled or not configured.
2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
is disabled or not configured.
2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
2007-03-21 15:00:53.47 Server A self-generated certificate was
successfully loaded for encryption.
2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
<ipv4> 1433].
2007-03-21 15:00:53.49 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
2007-03-21 15:00:53.50 Server The SQL Network Interface library could
not register the Service Principal Name (SPN) for the SQL Server service.
Error: 0x2098. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message.
Further action is only required if Kerberos authentication is required by
authentication policies.
2007-03-21 15:00:53.50 Server SQL Server is now ready for client
connections. This is an informational message; no user action is required.
2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
has completed. This is an informational message only. No user action is
required.
2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
informational message only. No user action is required.
--
Thanks and God Bless,
ThomBeauxThe service account did not have the:
(local policy) - Act as part of the OS
--
Thanks and God Bless,
ThomBeaux
"ThomBeaux" wrote:
> We have setup a MSCS with no problem. Have a SAN with mounted volumes and
> installed SQL Server 2005 64-bit Enterprise on Node1. We do not have a Node2,
> yet, but we are planning for the future(2008) when we will have a second node.
> The installation goes fine. No problems. It ends saying the startup of the
> service(s) failed, you will have to start them manually from the Cluster
> Administration.
> We go to the Cluster Administration and right-click to Bring Online. It
> still fails.
> Event Log
> [sqsrvres] ODBC sqldriverconnect failed
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]SQL Network Interfaces: The target
> principal name is incorrect.
> [sqsrvres] checkODBCConnectError: sqlstate = HY000; native error = 80090322;
> message = [Microsoft][SQL Native Client]Cannot generate SSPI context
>
> SQL Log:
> 2007-03-21 15:00:51.05 Server Microsoft SQL Server 2005 - 9.00.1399.06
> (X64)
> Oct 14 2005 00:35:21
> Copyright (c) 1988-2005 Microsoft Corporation
> Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
> 2007-03-21 15:00:51.05 Server (c) 2005 Microsoft Corporation.
> 2007-03-21 15:00:51.05 Server All rights reserved.
> 2007-03-21 15:00:51.05 Server Server process ID is 5644.
> 2007-03-21 15:00:51.05 Server Logging SQL Server messages in file
> 'M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG'.
> 2007-03-21 15:00:51.05 Server This instance of SQL Server last reported
> using a process ID of 4360 at 3/21/2007 2:59:02 PM (local) 3/21/2007 7:59:02
> PM (UTC). This is an informational message only; no user action is required.
> 2007-03-21 15:00:51.05 Server Registry startup parameters:
> 2007-03-21 15:00:51.05 Server -d
> M:\SQLData\MSSQL.1\MSSQL\DATA\master.mdf
> 2007-03-21 15:00:51.05 Server -e M:\SQLData\MSSQL.1\MSSQL\LOG\ERRORLOG
> 2007-03-21 15:00:51.05 Server -l
> M:\SQLData\MSSQL.1\MSSQL\DATA\mastlog.ldf
> 2007-03-21 15:00:51.07 Server SQL Server is starting at normal priority
> base (=7). This is an informational message only. No user action is required.
> 2007-03-21 15:00:51.07 Server Detected 32 CPUs. This is an
> informational message; no user action is required.
> 2007-03-21 15:00:51.07 Server Cannot use Large Page Extensions: lock
> memory privilege was not granted.
> 2007-03-21 15:00:51.69 Server Using dynamic lock allocation. Initial
> allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.69 Server Lock partitioning is enabled. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 0: CPU
> mask: 0x00000000ffff0000 Active CPU mask: 0x00000000ffff0000. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Multinode configuration: node 1: CPU
> mask: 0x000000000000ffff Active CPU mask: 0x000000000000ffff. This message
> provides a description of the NUMA configuration for this computer. This is
> an informational message only. No user action is required.
> 2007-03-21 15:00:51.71 Server Attempting to initialize Microsoft
> Distributed Transaction Coordinator (MS DTC). This is an informational
> message only. No user action is required.
> 2007-03-21 15:00:52.96 Server Attempting to recover in-doubt
> distributed transactions involving Microsoft Distributed Transaction
> Coordinator (MS DTC). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:52.97 Server Database Mirroring Transport is disabled
> in the endpoint configuration.
> 2007-03-21 15:00:52.99 spid6s Starting up database 'master'.
> 2007-03-21 15:00:53.04 spid6s Recovery is writing a checkpoint in
> database 'master' (1). This is an informational message only. No user action
> is required.
> 2007-03-21 15:00:53.07 spid6s SQL Trace ID 1 was started by login "sa".
> 2007-03-21 15:00:53.08 spid6s Starting up database 'mssqlsystemresource'.
> 2007-03-21 15:00:53.13 spid6s Server name is 'SVR-SQL-xx'. This is an
> informational message only. No user action is required.
> 2007-03-21 15:00:53.13 spid11s Starting up database 'model'.
> 2007-03-21 15:00:53.13 spid6s The NETBIOS name of the local node that
> is running the server is 'SVR-SQL-yyy'. This is an informational message
> only. No user action is required.
> 2007-03-21 15:00:53.18 spid11s Clearing tempdb database.
> 2007-03-21 15:00:53.25 spid11s Starting up database 'tempdb'.
> 2007-03-21 15:00:53.29 spid14s The Service Broker protocol transport is
> disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s The Database Mirroring protocol transport
> is disabled or not configured.
> 2007-03-21 15:00:53.29 spid14s Service Broker manager has started.
> 2007-03-21 15:00:53.47 Server A self-generated certificate was
> successfully loaded for encryption.
> 2007-03-21 15:00:53.49 Server Server is listening on [ 10.1.4.188
> <ipv4> 1433].
> 2007-03-21 15:00:53.49 Server Server local connection provider is ready
> to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
> 2007-03-21 15:00:53.49 Server Server named pipe provider is ready to
> accept connection on [ \\.\pipe\$$\SVR-SQL-xxx\sql\query ].
> 2007-03-21 15:00:53.50 Server The SQL Network Interface library could
> not register the Service Principal Name (SPN) for the SQL Server service.
> Error: 0x2098. Failure to register an SPN may cause integrated authentication
> to fall back to NTLM instead of Kerberos. This is an informational message.
> Further action is only required if Kerberos authentication is required by
> authentication policies.
> 2007-03-21 15:00:53.50 Server SQL Server is now ready for client
> connections. This is an informational message; no user action is required.
> 2007-03-21 15:00:53.55 spid6s Starting up database 'msdb'.
> 2007-03-21 15:00:53.60 spid6s Recovery of any in-doubt distributed
> transactions involving Microsoft Distributed Transaction Coordinator (MS DTC)
> has completed. This is an informational message only. No user action is
> required.
> 2007-03-21 15:00:53.60 spid6s Recovery is complete. This is an
> informational message only. No user action is required.
>
> --
> Thanks and God Bless,
> ThomBeaux