Re: Event ID 1094

You might check to see if your heartbeat adapters are configured per the
following KB:

http://support.microsoft.com/kb/258750

It is not normal for the heartbeat to show up failed if both cluster nodes
are online. If you're seeing the heartbeat failed during the "link failure",
this would be normal.

Regards,
John


"Brandon" <Brandon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E45C18A4-7774-456A-BC20-C4E9D5FB0F82@xxxxxxxxxxxxxxxx
No, I know there has to be a network connection for the servers to see the
cluster.

I did a hardware failover test. The Active server(s1) have users
accessing
data, SQL 2005 failover, and then I pull the network cables on s1 to force
a
hardware failure and force the cluster to failover to the passive
server(s2)
which it does.

When I plug the network cables into the now passive server(s1), it does
not
re-join the cluster I just get the red circle with an x and then a blue
with
!.

I resolved the issue by downing the servers and then bringing them back up
in the order I wanted them to join the cluster.

I have noticed that the heartbeat on the passive server shows failed in
the
cluster administrator. Is this normal?

"John Toner [MVP]" wrote:

So you've pulled the network cables and you're expecting the cluster
node to
join a node without network access? Clusters join using IP and RPC
communications so if you have no network, it isn't going to join.

If I'm misunderstanding you, then you might want to check the node that
is
"online" and verify that the cluster name and cluster IP resources are
online. If these are offline, you won't be able to join.

Regards,
John

"Brandon" <Brandon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9423856C-7C74-4286-82F7-2C9230365181@xxxxxxxxxxxxxxxx
In a Windows 2003 2 node cluster once a failover occurs, pulled the
network
cables and heartbeat cable, the second server will not join the
cluster
again. I get the following error in the system event log

Event Type: Error
Event Source: ClusSvc
Event Category: Node Mgr
Event ID: 1094
Date: 4/19/2006
Time: 10:35:13 AM
User: N/A
Computer: PKSD03
Description:
Cluster service failed to obtain information from the server cluster
configuration database. The error code was 1726.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Thanks for any help!
Brandon





.

Relevant Pages

  • Re: Loss of Connectivity
    ... Either on the Heartbeat or Primary Nic. ... Does the passive node shut its cluster service down? ... If it actually loses total network connectivity, ... We have a Windows 2003 Server Enterprise w/SP2 Running in a cluster. ...
    (microsoft.public.windows.server.clustering)
  • RE: REDHAT CLUSTER
    ... Had my first server ... I posted some info and technical details of implementing heartbeat up on ... Subject: REDHAT CLUSTER ... storage and RHEL 3 installed in both the servers. ...
    (RedHat)
  • Re: configure sql cluster with one NIC (two nic but teamed)
    ... Columnist, SQL Server Professional ... Can you use one teamed nic to serve both public and heartbeat role? ... > you can change IPs within a cluster. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Cluster could not fail over
    ... So in this case is the Heartbeat the cause of the problem? ... the 500ms round trip for the failover. ... the cluster service starts a heavy-weight ... > MVP - Windows Server - Clustering ...
    (microsoft.public.windows.server.clustering)
  • Re: Cluster could not fail over
    ... heartbeat network is the initiator for a node resource failover? ... the cluster service starts a heavy-weight ... MVP - Windows Server - Clustering ...
    (microsoft.public.windows.server.clustering)