Post reply

Availability Group Listener

  • May 3, 2017 at 2:03 pm

    #402024

    We have Always On with 3 nodes on that first 2 nodes are SQL Server cluster and 3rd node is for secondary replica. Now the Listener is failing when tried to do failover from one node to another.

    Got below error from Failover cluster log

    Failover Cluster Manager encountered a fatal error.

    System.Runtime.InteropServices.InvalidComObjectException: COM object that has been separated from its underlying RCW cannot be used.
     at System.Windows.Documents.TextServicesHost.OnUnregisterTextStore(Object arg)
     at System.Windows.Documents.TextStore.OnDetach(Boolean finalizer)
     at System.Windows.Documents.TextEditor.DetachTextStore(Boolean finalizer)
     at MS.Internal.ShutDownListener.HandleShutDown(Object sender, EventArgs e)

    .Listener Fileshare is not coming online.

  • May 5, 2017 at 6:25 am

    #1941251

    all 3 nodes must be a member of the same windows server failover cluster, confirm this please

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • May 7, 2017 at 12:35 am

    #1941456

    Thanks Perry,

    Yes all 3 nodes are part of windows failover cluster.

    When selecting properties of Listener throwing below error.

    Availability group listener ABCCORPLIS-TST does not exist in availability group ABCCORPDBL-TST.

  • May 7, 2017 at 11:50 pm

    #1941506

    I have checked in AD whether the name and IP exists and respective team confirmed the same.

  • May 8, 2017 at 11:27 am

    #1941641

    Rechana Rajan - Sunday, May 7, 2017 12:35 AM

    Thanks Perry,

    Yes all 3 nodes are part of windows failover cluster.

    When selecting properties of Listener throwing below error.

    Availability group listener ABCCORPLIS-TST does not exist in availability group ABCCORPDBL-TST.

    So 2 nodes have a FCI hosted and the 3rd node has a standalone instance joined to the AG, correct

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • May 9, 2017 at 4:07 am

    #1941741

    Perry Whittle - Monday, May 8, 2017 11:27 AM

    Rechana Rajan - Sunday, May 7, 2017 12:35 AM

    Thanks Perry,

    Yes all 3 nodes are part of windows failover cluster.

    When selecting properties of Listener throwing below error.

    Availability group listener ABCCORPLIS-TST does not exist in availability group ABCCORPDBL-TST.

    So 2 nodes have a FCI hosted and the 3rd node has a standalone instance joined to the AG, correct

    Thanks Perry,

    Thats Correct

  • May 9, 2017 at 4:08 am

    #1941742

    The issue was because the filestream was only enabled in node 1 ,enabling the same in other nodes help resolve the issue.

    Thanks everyone for  the support

  • May 11, 2017 at 7:13 am

    #1942158

    thanks for confirming

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply