No announcement yet.

A Clustered service fails in failover!

  • Filter
  • Time
  • Show
Clear All
new posts

  • A Clustered service fails in failover!

    ALMOST done I think but this for some reason does not work.

    I created a Windows Service which hosts a WCF application looking at/binding to the Clustered MSMQ

    The Windows service was first installed on both nodes of the cluster.

    I then created a cluster of this through the high availability wizard (selecting Generic service).

    The client which is sending data to the clustered MSMQ (external from the cluster but same domain/network) sends to the Clustered MSMQ fine.

    One of the nodes in the cluster sees the data through the Windows Service (ive got debugging trace to verify this)

    Then, when say NodeA goes down, NodeB *should* kick in but it fails to start the Clustered Windows Service with no explanation at all!

    It does this several times and still fails. I have to start the Windows Service manually on this Node through services.msc then it works just fine and the service is up and running and continues to process the messages from the Clustered MSMQ.

    something clearly isn't right here. Why does the Clustered service fail to "start" when one of the nodes goes down/appears offline? What am I doing wrong? Wrong setting somewhere?

    Thank you.

  • #2
    Re: A Clustered service fails in failover!

    after further investigating, it appears that I was running the service somewhat incorrectly. I am now... 2 steps backwards.

    I was running the service manually but reading from the clustered MSMQ which is fine but when time comes for a proper failover, it fails to do this.

    So now, I am not running the service manually and just letting the Cluster management do it but it fails as soon as I create the high availability app generic service.

    it says that The version of MSMQ cannot be detected and that the MSMQ service is not available.

    but it is available on the cluster. I can even look at it through computer management and see the queue and the messages coming in.

    any ideas?


    • #3
      Re: A Clustered service fails in failover!

      This is worth a review.


      • #4
        Re: A Clustered service fails in failover!


        I actually managed to get it working.
        I had to untick the "Use computer name as network name" optiion for that generic service....


        • #5
          Re: A Clustered service fails in failover!

          Good to hear. So no outstanding issues for you at the moment?


          • #6
            Re: A Clustered service fails in failover!

            No, thankfully! But that was frustrating. all the blogs/articles I read always said to make sure that it is checked/ticked. the cluster management does this automatic when you create a high availability service.

            but it does make me question if it is using the Clustered MSMQ and not the local instance of MSMQ...... how can I verify this?

            when I connect to the ClusteredMSMQ via MMC, I DO see messages being placed there.

            The problem I then have is that if I use this generic service elsewhere on the network, it does point to the Clustered MSMQ but does NOT appear to be reading messages from it. no errors.... so it makes me wonder if it actually is placing it on the ClusteredMSMQ or not.