Cluster resource 'SQL IP Address 1 (SQLCluster)' in clustered service or
application 'SQL Server (MSSQLSERVER)' failed.

I receive this error when i try to "simulate failure of this resources" from
one node. (there are 2 nodes in this cluster environment) BUT The resources
is coming back online after that simulation. I'm also try to access from my
application when i do this simulation, my application is stuck for a moment
but when i refresh it's ok. So thats mean my failover is working

I'm using sql server 2008 and Win server 2008 on itanium based system

Is this a common error after we do a simulation? or do i need to look
further to investigate this error?

How are you "simulating" a resource failure? If the failure is momentary,
the Cluster service will try and bring the application back online on the
original node.

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


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

I go to :
1. Failover Cluster Management
2. Go to DBPCLUSTER.dbpmain.gov.my
3. Go to Services and Applications
4. Expand the tree - There are DBPCLUSTERdtc and SQL Server (MSSQLSERVER).
5. I select SQL Server (MSSQLSERVER) - I select Disk Drives. Under there i
select Cluster Disk 2 and right click. Then i choose More Actions - Simulate
Failure if this resources.Then i Simulate Failure of Cluster Disk 2. Done
6. The simulation pending for a momentary and bring back to online BUT i
receive error as my previous questions
"Cluster resource 'Cluster Disk 2' in clustered service or application 'SQL
Server (MSSQLSERVER)' failed."
7. I do simulate the Server Name---IP Address and receive the same error.
BUT it was momentary and bring online back
"Cluster resource 'SQL IP Address 1 (SQLCluster)' in clustered service or
application 'SQL Server (MSSQLSERVER)' failed."



"Geoff N. Hiten" wrote:

Failover Cluster Management tells you the Current Host Server. You can also
see the current host by looking at Server Manager or My Computer. My
(extremely limited experience) is that if its stuck for a moment, it restarts
on the same node. Failing over to another node takes a little longer.

This behavior is configurable by going into the properties of the resource
and editing the policies tab.

"Nicole G." wrote: