Passive node starting the SQL Server services - services set to ma

Hello all,
I have a very bizarre situation with a single instance/two node/W2K3
cluster. The issue I am seeing is that the passive node is starting the sql
server services even though the resources are not owned by that node. The
restarts are occuring every five minutes. The system log shows the SYSTEM
account starting MSSQLSERVER. Then, 3 seconds later, I get a message stating
the service stopped. About 5-8 seconds later, I get a message that the
SQLSERVERAGENT could not be started because sqlservr.exe is not running. The
cluster log is not showing anything being started/stopped. The applicaiton
log is complaining about the errorlog being unavailable. However, this is
correct because the resources are not on this node.
The SQL Server services are set to manual on both nodes. Both nodes have
been rebooted in the past 24 hours due to EMC PowerPath upgrades. The only
thing that is a little bizare is that the SQL Server resource group and SQL
Server resource have the preferred owners/possible owners in reverse order.
IE (SQL Server resource group has NODE1/NODE2; SQL Server Resource has
NODE2/NODE1). Right now all resources are on NODE1.
Any ideas would be greatly appreciated.
Thanks in advance
Chris.
Manual start for services is correct for a cluster. The cluster should
control the services on each node. Look at the applicaiotn logs on both
nodes. Check the failover/failback settings. You may be seeing a failback
condition due to different preferred node settings.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Christopher" <Christopher@.discussions.microsoft.com> wrote in message
news:E5873D57-2A8F-4B7B-B76C-7146B8A629DD@.microsoft.com...
> Hello all,
> I have a very bizarre situation with a single instance/two node/W2K3
> cluster. The issue I am seeing is that the passive node is starting the
> sql
> server services even though the resources are not owned by that node. The
> restarts are occuring every five minutes. The system log shows the SYSTEM
> account starting MSSQLSERVER. Then, 3 seconds later, I get a message
> stating
> the service stopped. About 5-8 seconds later, I get a message that the
> SQLSERVERAGENT could not be started because sqlservr.exe is not running.
> The
> cluster log is not showing anything being started/stopped. The
> applicaiton
> log is complaining about the errorlog being unavailable. However, this is
> correct because the resources are not on this node.
> The SQL Server services are set to manual on both nodes. Both nodes have
> been rebooted in the past 24 hours due to EMC PowerPath upgrades. The
> only
> thing that is a little bizare is that the SQL Server resource group and
> SQL
> Server resource have the preferred owners/possible owners in reverse
> order.
> IE (SQL Server resource group has NODE1/NODE2; SQL Server Resource has
> NODE2/NODE1). Right now all resources are on NODE1.
> Any ideas would be greatly appreciated.
> Thanks in advance
> Chris.