Network Packet Payload Error when Trying to Create Distributed Availability Group
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
asked 7 mins ago
rhinohueyrhinohuey
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.
add a comment |
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
asked 7 mins ago
rhinohueyrhinohuey
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.
add a comment |
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
asked 7 mins ago
rhinohueyrhinohuey
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.
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
availability-groups distributed-availability-groups
asked 7 mins ago
rhinohueyrhinohuey
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.
asked 7 mins ago
rhinohueyrhinohuey
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.
asked 7 mins ago
rhinohueyrhinohuey
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.
asked 7 mins ago
rhinohueyrhinohuey
1
asked 7 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.
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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.
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
