Network Packet Payload Error when Trying to Create Distributed Availability GroupSpecifying the failover...

What is the idiomatic way to say "clothing fits"?

Detention in 1997

Is there an expression that means doing something right before you will need it rather than doing it in case you might need it?

In 'Revenger,' what does 'cove' come from?

Could the museum Saturn V's be refitted for one more flight?

Unlock My Phone! February 2018

How do conventional missiles fly?

Arrow those variables!

Why is this clock signal connected to a capacitor to gnd?

What is the most common color to indicate the input-field is disabled?

GFCI outlets - can they be repaired? Are they really needed at the end of a circuit?

Bullying boss launched a smear campaign and made me unemployable

Am I breaking OOP practice with this architecture?

I would say: "You are another teacher", but she is a woman and I am a man

What method can I use to design a dungeon difficult enough that the PCs can't make it through without killing them?

Madden-Julian Oscillation (MJO) - How to interpret the index?

Why no variance term in Bayesian logistic regression?

If human space travel is limited by the G force vulnerability, is there a way to counter G forces?

What does the expression "A Mann!" means

Should I tell management that I intend to leave due to bad software development practices?

Why does this cyclic subgroup have only 4 subgroups?

How could indestructible materials be used in power generation?

Do UK voters know if their MP will be the Speaker of the House?

Is it possible to create a QR code using text?



Network Packet Payload Error when Trying to Create Distributed Availability Group


Specifying the failover partner when using Availability GroupsSQL Server 2012 Availability Group issueMultiple named Instances and Availability GroupsServices Cannot Connect to Multi-Subnet Availability Group After FailoverDistributed Availability Group Failover IssueAlways on Failover ClusterCannot remove Database from Distributed AlwaysOn Group on Secondary Windows ClusterSQL Server Distributed Availability Group databases not syncing after a server rebootSwitch-SQLAvailability error during DB Restore in AlwaysON GroupWhy is the Read-Only Routing not functioning in this Availability Group?













0















I am attempting to create a distributed AG on SQL 2016 SP1, but keep getting the following errors. I have tried this in a VirtualBox (local desktop) and actual VMWare virtual environment but getting the same errors each time.



The distributed AG creates successfully on both WFCs, but when I try to "ALTER AVAILABILITY GROUP [Dist AG Name] JOIN" on the primary replica of the 'remote' AG, the command completes successfully, but I immediately get this error in the log:




A connection timeout has occurred while attempting to establish a
connection to availability replica 'AG1' with id
[FCAA4083-D6B8-1BAC-9E8C-6AECE34513E6]. Either a networking or
firewall issue exists, or the endpoint address provided for the
replica is not the database mirroring endpoint of the host server
instance.




On the primary replica of the 'local' AG, I start getting these errors in the log repeatedly:




Length specified in network packet payload did not match number of
bytes read; the connection has been closed. Please contact the vendor
of the client library. [CLIENT: 192.168.56.104]




These are the bytes that show up in Event Viewer event:



0000: AC 45 00 00 14 00 00 00   ¬E...... 
0008: 14 00 00 00 41 00 47 00 ....A.G.
0010: 31 00 53 00 45 00 52 00 1.S.E.R.
0018: 56 00 45 00 52 00 31 00 V.E.R.1.
0020: 5C 00 41 00 47 00 31 00 .A.G.1.
0028: 49 00 4E 00 53 00 54 00 I.N.S.T.
0030: 31 00 00 00 00 00 00 00 1.......


In both environments, I am only dealing with a single subnet and a single domain. I've also tried removing all special characters from VM hostnames, instance names, AG names, and listener names during troubleshooting.



Wondering if anyone has ran into this before. I don't see anything in the SP2 release notes that suggests its a bug, but I'm willing to try an SP2 upgrade if anyone thinks its worthwhile. (Unfortunately I am not in a position to be able to upgrade my prod environment for some time which is why I haven't tried it yet.)



I can also post full endpoint/AG/listener creation scripts if anyone is willing to try to reproduce or provide troubleshooting tips.



Thanks!









share







New contributor




rhinohuey is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    0















    I am attempting to create a distributed AG on SQL 2016 SP1, but keep getting the following errors. I have tried this in a VirtualBox (local desktop) and actual VMWare virtual environment but getting the same errors each time.



    The distributed AG creates successfully on both WFCs, but when I try to "ALTER AVAILABILITY GROUP [Dist AG Name] JOIN" on the primary replica of the 'remote' AG, the command completes successfully, but I immediately get this error in the log:




    A connection timeout has occurred while attempting to establish a
    connection to availability replica 'AG1' with id
    [FCAA4083-D6B8-1BAC-9E8C-6AECE34513E6]. Either a networking or
    firewall issue exists, or the endpoint address provided for the
    replica is not the database mirroring endpoint of the host server
    instance.




    On the primary replica of the 'local' AG, I start getting these errors in the log repeatedly:




    Length specified in network packet payload did not match number of
    bytes read; the connection has been closed. Please contact the vendor
    of the client library. [CLIENT: 192.168.56.104]




    These are the bytes that show up in Event Viewer event:



    0000: AC 45 00 00 14 00 00 00   ¬E...... 
    0008: 14 00 00 00 41 00 47 00 ....A.G.
    0010: 31 00 53 00 45 00 52 00 1.S.E.R.
    0018: 56 00 45 00 52 00 31 00 V.E.R.1.
    0020: 5C 00 41 00 47 00 31 00 .A.G.1.
    0028: 49 00 4E 00 53 00 54 00 I.N.S.T.
    0030: 31 00 00 00 00 00 00 00 1.......


    In both environments, I am only dealing with a single subnet and a single domain. I've also tried removing all special characters from VM hostnames, instance names, AG names, and listener names during troubleshooting.



    Wondering if anyone has ran into this before. I don't see anything in the SP2 release notes that suggests its a bug, but I'm willing to try an SP2 upgrade if anyone thinks its worthwhile. (Unfortunately I am not in a position to be able to upgrade my prod environment for some time which is why I haven't tried it yet.)



    I can also post full endpoint/AG/listener creation scripts if anyone is willing to try to reproduce or provide troubleshooting tips.



    Thanks!









    share







    New contributor




    rhinohuey is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0








      I am attempting to create a distributed AG on SQL 2016 SP1, but keep getting the following errors. I have tried this in a VirtualBox (local desktop) and actual VMWare virtual environment but getting the same errors each time.



      The distributed AG creates successfully on both WFCs, but when I try to "ALTER AVAILABILITY GROUP [Dist AG Name] JOIN" on the primary replica of the 'remote' AG, the command completes successfully, but I immediately get this error in the log:




      A connection timeout has occurred while attempting to establish a
      connection to availability replica 'AG1' with id
      [FCAA4083-D6B8-1BAC-9E8C-6AECE34513E6]. Either a networking or
      firewall issue exists, or the endpoint address provided for the
      replica is not the database mirroring endpoint of the host server
      instance.




      On the primary replica of the 'local' AG, I start getting these errors in the log repeatedly:




      Length specified in network packet payload did not match number of
      bytes read; the connection has been closed. Please contact the vendor
      of the client library. [CLIENT: 192.168.56.104]




      These are the bytes that show up in Event Viewer event:



      0000: AC 45 00 00 14 00 00 00   ¬E...... 
      0008: 14 00 00 00 41 00 47 00 ....A.G.
      0010: 31 00 53 00 45 00 52 00 1.S.E.R.
      0018: 56 00 45 00 52 00 31 00 V.E.R.1.
      0020: 5C 00 41 00 47 00 31 00 .A.G.1.
      0028: 49 00 4E 00 53 00 54 00 I.N.S.T.
      0030: 31 00 00 00 00 00 00 00 1.......


      In both environments, I am only dealing with a single subnet and a single domain. I've also tried removing all special characters from VM hostnames, instance names, AG names, and listener names during troubleshooting.



      Wondering if anyone has ran into this before. I don't see anything in the SP2 release notes that suggests its a bug, but I'm willing to try an SP2 upgrade if anyone thinks its worthwhile. (Unfortunately I am not in a position to be able to upgrade my prod environment for some time which is why I haven't tried it yet.)



      I can also post full endpoint/AG/listener creation scripts if anyone is willing to try to reproduce or provide troubleshooting tips.



      Thanks!









      share







      New contributor




      rhinohuey is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      I am attempting to create a distributed AG on SQL 2016 SP1, but keep getting the following errors. I have tried this in a VirtualBox (local desktop) and actual VMWare virtual environment but getting the same errors each time.



      The distributed AG creates successfully on both WFCs, but when I try to "ALTER AVAILABILITY GROUP [Dist AG Name] JOIN" on the primary replica of the 'remote' AG, the command completes successfully, but I immediately get this error in the log:




      A connection timeout has occurred while attempting to establish a
      connection to availability replica 'AG1' with id
      [FCAA4083-D6B8-1BAC-9E8C-6AECE34513E6]. Either a networking or
      firewall issue exists, or the endpoint address provided for the
      replica is not the database mirroring endpoint of the host server
      instance.




      On the primary replica of the 'local' AG, I start getting these errors in the log repeatedly:




      Length specified in network packet payload did not match number of
      bytes read; the connection has been closed. Please contact the vendor
      of the client library. [CLIENT: 192.168.56.104]




      These are the bytes that show up in Event Viewer event:



      0000: AC 45 00 00 14 00 00 00   ¬E...... 
      0008: 14 00 00 00 41 00 47 00 ....A.G.
      0010: 31 00 53 00 45 00 52 00 1.S.E.R.
      0018: 56 00 45 00 52 00 31 00 V.E.R.1.
      0020: 5C 00 41 00 47 00 31 00 .A.G.1.
      0028: 49 00 4E 00 53 00 54 00 I.N.S.T.
      0030: 31 00 00 00 00 00 00 00 1.......


      In both environments, I am only dealing with a single subnet and a single domain. I've also tried removing all special characters from VM hostnames, instance names, AG names, and listener names during troubleshooting.



      Wondering if anyone has ran into this before. I don't see anything in the SP2 release notes that suggests its a bug, but I'm willing to try an SP2 upgrade if anyone thinks its worthwhile. (Unfortunately I am not in a position to be able to upgrade my prod environment for some time which is why I haven't tried it yet.)



      I can also post full endpoint/AG/listener creation scripts if anyone is willing to try to reproduce or provide troubleshooting tips.



      Thanks!







      availability-groups distributed-availability-groups





      share







      New contributor




      rhinohuey is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.










      share







      New contributor




      rhinohuey is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      share



      share






      New contributor




      rhinohuey is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 2 mins ago









      rhinohueyrhinohuey

      1




      1




      New contributor




      rhinohuey is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      rhinohuey is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      rhinohuey is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          0






          active

          oldest

          votes












          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "182"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          rhinohuey is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f233895%2fnetwork-packet-payload-error-when-trying-to-create-distributed-availability-grou%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          rhinohuey is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          rhinohuey is a new contributor. Be nice, and check out our Code of Conduct.













          rhinohuey is a new contributor. Be nice, and check out our Code of Conduct.












          rhinohuey is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Database Administrators Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f233895%2fnetwork-packet-payload-error-when-trying-to-create-distributed-availability-grou%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Anexo:Material bélico de la Fuerza Aérea de Chile Índice Aeronaves Defensa...

          Always On Availability groups resolving state after failover - Remote harden of transaction...

          update json value to null Announcing the arrival of Valued Associate #679: Cesar Manara ...