Post reply

Identical versions required (take 2)

  • October 24, 2016 at 8:39 am

    #314747

    Hi,

    Please I need advise,

    Environment: 2 node active/active

    Situation: Both Nodes running ok with SQL Server 2008R2 10.50.1600.1, I proceed to upgrade to version SP3

    10.60.6000.34, Node A sucessfully updated, Node B failed with a exit code -2067791871, finally both nodes are:

    Node A:10.60.6000.34

    Node B:10.50.2500.0

    Cluster is active and ok due to maintenance time window was over, no more changes could be applied, tested or rolled back. What potential problems I will see and How I must re-apply SP3 in the failing node ???

    :w00t:

    Thanks for your ideas.

  • October 24, 2016 at 8:52 am

    #1908396

    luismarinaray (10/24/2016)

    Hi,

    Please I need advise,

    Environment: 2 node active/active

    Situation: Both Nodes running ok with SQL Server 2008R2 10.50.1600.1, I proceed to upgrade to version SP3

    10.60.6000.34, Node A sucessfully updated, Node B failed with a exit code -2067791871, finally both nodes are:

    Node A:10.60.6000.34

    Node B:10.50.2500.0

    Cluster is active and ok due to maintenance time window was over, no more changes could be applied, tested or rolled back. What potential problems I will see and How I must re-apply SP3 in the failing node ???

    :w00t:

    Thanks for your ideas.

    Start reading the log files. From what you posted, no idea.

  • October 25, 2016 at 2:49 pm

    #1908776

    Thanks for your response,

    I am thinking that I updated Node B inappropiatedly :ermm:

    all this issue for me is related with failover cluster manager and how is distributed the charge between nodes.

    I am looking for ways to pause failover between nodes, so I can run again service pack 3

    meanwhile, all SQL Server instances are running (if you have any idea on how to do this I will appreciate).

    Sincerely,

    Newbie with cluster management and

    Thanks again for your idea.

  • December 6, 2016 at 6:55 am

    #1916216

    Hi,

    After almost two months with this incident, I have discovered the following fact:

    Node B has: Trace FlagStatus

    902 ON

    The SQL Server is working normal, remember that I have inherited this environment,

    I would like to hear your suggestions to remove this flag on Node B, have you experienced this situation, what could happen ?

    Thanks again

Viewing 4 posts - 1 through 3 (of 3 total)

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