Cannot set up replication between two servers
I am trying to subscribe a 2016 (sp2, cu1) server to another 2017 server. I am getting the following error message:
For merge publications, the version of the Subscriber must not exceed the version of the Publisher
The database on the subscriber is running in compatibility mode 2016 (130) and the publisher is running in 2017 (140). The version of SSMS on the subscriber is also lower than the version on the publisher.
Any advice?
Additional details
While I am aware that on surface level this should be working it still is not, could the error I am getting be hiding a different problem?
- Publisher Compatibility level: 140
- Subscriber Compatibility level: 130
I am unable to set the compatibility level of the subscriber to 140 because the server is running 2016 and not 2017. I am also unable to upgrade the publisher right now because of business reasons (I am unable to take the server offline for any period of time). I addition to this, we have other 2016 (sp2, cu1) servers running as subscriber to this server. The publisher server is also the distributor, so both are running on SQL Server 2017 which is a high version of SQL Server than the subscriber.
sql-server replication sql-server-2016 ssms merge-replication
asked 4 hours ago
Nicholas SaulNicholas Saul
12
New contributor
Nicholas Saul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
|
show 2 more comments
I am trying to subscribe a 2016 (sp2, cu1) server to another 2017 server. I am getting the following error message:
For merge publications, the version of the Subscriber must not exceed the version of the Publisher
The database on the subscriber is running in compatibility mode 2016 (130) and the publisher is running in 2017 (140). The version of SSMS on the subscriber is also lower than the version on the publisher.
Any advice?
Additional details
While I am aware that on surface level this should be working it still is not, could the error I am getting be hiding a different problem?
- Publisher Compatibility level: 140
- Subscriber Compatibility level: 130
I am unable to set the compatibility level of the subscriber to 140 because the server is running 2016 and not 2017. I am also unable to upgrade the publisher right now because of business reasons (I am unable to take the server offline for any period of time). I addition to this, we have other 2016 (sp2, cu1) servers running as subscriber to this server. The publisher server is also the distributor, so both are running on SQL Server 2017 which is a high version of SQL Server than the subscriber.
sql-server replication sql-server-2016 ssms merge-replication
asked 4 hours ago
Nicholas SaulNicholas Saul
12
New contributor
Nicholas Saul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
can you runselect @@versionon both servers and provide results.
– MarmiK
4 hours ago
Publisher: Microsoft SQL Server 2017 (RTM-CU6) (KB4101464) - 14.0.3025.34 (X64) Apr 9 2018 18:00:41 Copyright (C) 2017 Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor) Subscriber: Microsoft SQL Server 2016 (SP2-CU1) (KB4135048) - 13.0.5149.0 (X64) May 19 2018 09:41:57 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor)
– Nicholas Saul
4 hours ago
Well, if that are the servers than it should not cause any issue, I am sure this are fresh installs and not upgrades. as compatibility says this should work fine source Unless there is distributor in picture.
– MarmiK
3 hours ago
Welcome, @NicholasSaul. Please edit your question to include the information you answered in a comment. Comments here aren't for extended discussion.
– Colin 't Hart
3 hours ago
Please specify compatibility mode of replicatoin database on both serversSELECT compatibility_level FROM sys.databases WHERE name = 'DBName';
– MarmiK
3 hours ago
|
show 2 more comments
I am trying to subscribe a 2016 (sp2, cu1) server to another 2017 server. I am getting the following error message:
For merge publications, the version of the Subscriber must not exceed the version of the Publisher
The database on the subscriber is running in compatibility mode 2016 (130) and the publisher is running in 2017 (140). The version of SSMS on the subscriber is also lower than the version on the publisher.
Any advice?
Additional details
While I am aware that on surface level this should be working it still is not, could the error I am getting be hiding a different problem?
- Publisher Compatibility level: 140
- Subscriber Compatibility level: 130
I am unable to set the compatibility level of the subscriber to 140 because the server is running 2016 and not 2017. I am also unable to upgrade the publisher right now because of business reasons (I am unable to take the server offline for any period of time). I addition to this, we have other 2016 (sp2, cu1) servers running as subscriber to this server. The publisher server is also the distributor, so both are running on SQL Server 2017 which is a high version of SQL Server than the subscriber.
sql-server replication sql-server-2016 ssms merge-replication
asked 4 hours ago
Nicholas SaulNicholas Saul
12
New contributor
Nicholas Saul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I am trying to subscribe a 2016 (sp2, cu1) server to another 2017 server. I am getting the following error message:
For merge publications, the version of the Subscriber must not exceed the version of the Publisher
The database on the subscriber is running in compatibility mode 2016 (130) and the publisher is running in 2017 (140). The version of SSMS on the subscriber is also lower than the version on the publisher.
Any advice?
Additional details
While I am aware that on surface level this should be working it still is not, could the error I am getting be hiding a different problem?
- Publisher Compatibility level: 140
- Subscriber Compatibility level: 130
I am unable to set the compatibility level of the subscriber to 140 because the server is running 2016 and not 2017. I am also unable to upgrade the publisher right now because of business reasons (I am unable to take the server offline for any period of time). I addition to this, we have other 2016 (sp2, cu1) servers running as subscriber to this server. The publisher server is also the distributor, so both are running on SQL Server 2017 which is a high version of SQL Server than the subscriber.
sql-server replication sql-server-2016 ssms merge-replication
sql-server replication sql-server-2016 ssms merge-replication
asked 4 hours ago
Nicholas SaulNicholas Saul
12
New contributor
Nicholas Saul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 4 hours ago
Nicholas SaulNicholas Saul
12
New contributor
Nicholas Saul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 30 mins ago
Nicholas Saul
asked 4 hours ago
Nicholas SaulNicholas Saul
12
New contributor
Nicholas Saul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 4 hours ago
Nicholas SaulNicholas Saul
12
asked 4 hours ago
Nicholas SaulNicholas Saul
12
12
New contributor
Nicholas Saul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Nicholas Saul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Nicholas Saul is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
can you runselect @@versionon both servers and provide results.
– MarmiK
4 hours ago
Publisher: Microsoft SQL Server 2017 (RTM-CU6) (KB4101464) - 14.0.3025.34 (X64) Apr 9 2018 18:00:41 Copyright (C) 2017 Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor) Subscriber: Microsoft SQL Server 2016 (SP2-CU1) (KB4135048) - 13.0.5149.0 (X64) May 19 2018 09:41:57 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor)
– Nicholas Saul
4 hours ago
Well, if that are the servers than it should not cause any issue, I am sure this are fresh installs and not upgrades. as compatibility says this should work fine source Unless there is distributor in picture.
– MarmiK
3 hours ago
Welcome, @NicholasSaul. Please edit your question to include the information you answered in a comment. Comments here aren't for extended discussion.
– Colin 't Hart
3 hours ago
Please specify compatibility mode of replicatoin database on both serversSELECT compatibility_level FROM sys.databases WHERE name = 'DBName';
– MarmiK
3 hours ago
|
show 2 more comments
1
can you runselect @@versionon both servers and provide results.
– MarmiK
4 hours ago
Publisher: Microsoft SQL Server 2017 (RTM-CU6) (KB4101464) - 14.0.3025.34 (X64) Apr 9 2018 18:00:41 Copyright (C) 2017 Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor) Subscriber: Microsoft SQL Server 2016 (SP2-CU1) (KB4135048) - 13.0.5149.0 (X64) May 19 2018 09:41:57 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor)
– Nicholas Saul
4 hours ago
Well, if that are the servers than it should not cause any issue, I am sure this are fresh installs and not upgrades. as compatibility says this should work fine source Unless there is distributor in picture.
– MarmiK
3 hours ago
Welcome, @NicholasSaul. Please edit your question to include the information you answered in a comment. Comments here aren't for extended discussion.
– Colin 't Hart
3 hours ago
Please specify compatibility mode of replicatoin database on both serversSELECT compatibility_level FROM sys.databases WHERE name = 'DBName';
– MarmiK
3 hours ago
1
1
can you run
select @@version on both servers and provide results.– MarmiK
4 hours ago
can you run
select @@version on both servers and provide results.– MarmiK
4 hours ago
Publisher: Microsoft SQL Server 2017 (RTM-CU6) (KB4101464) - 14.0.3025.34 (X64) Apr 9 2018 18:00:41 Copyright (C) 2017 Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor) Subscriber: Microsoft SQL Server 2016 (SP2-CU1) (KB4135048) - 13.0.5149.0 (X64) May 19 2018 09:41:57 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor)
– Nicholas Saul
4 hours ago
Publisher: Microsoft SQL Server 2017 (RTM-CU6) (KB4101464) - 14.0.3025.34 (X64) Apr 9 2018 18:00:41 Copyright (C) 2017 Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor) Subscriber: Microsoft SQL Server 2016 (SP2-CU1) (KB4135048) - 13.0.5149.0 (X64) May 19 2018 09:41:57 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor)
– Nicholas Saul
4 hours ago
Well, if that are the servers than it should not cause any issue, I am sure this are fresh installs and not upgrades. as compatibility says this should work fine source Unless there is distributor in picture.
– MarmiK
3 hours ago
Well, if that are the servers than it should not cause any issue, I am sure this are fresh installs and not upgrades. as compatibility says this should work fine source Unless there is distributor in picture.
– MarmiK
3 hours ago
Welcome, @NicholasSaul. Please edit your question to include the information you answered in a comment. Comments here aren't for extended discussion.
– Colin 't Hart
3 hours ago
Welcome, @NicholasSaul. Please edit your question to include the information you answered in a comment. Comments here aren't for extended discussion.
– Colin 't Hart
3 hours ago
Please specify compatibility mode of replicatoin database on both servers
SELECT compatibility_level FROM sys.databases WHERE name = 'DBName';– MarmiK
3 hours ago
Please specify compatibility mode of replicatoin database on both servers
SELECT compatibility_level FROM sys.databases WHERE name = 'DBName';– MarmiK
3 hours ago
|
show 2 more comments
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
});
}
});
Nicholas Saul 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%2f227490%2fcannot-set-up-replication-between-two-servers%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
Nicholas Saul is a new contributor. Be nice, and check out our Code of Conduct.
Nicholas Saul is a new contributor. Be nice, and check out our Code of Conduct.
Nicholas Saul is a new contributor. Be nice, and check out our Code of Conduct.
Nicholas Saul 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%2f227490%2fcannot-set-up-replication-between-two-servers%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
1
can you run
select @@versionon both servers and provide results.– MarmiK
4 hours ago
Publisher: Microsoft SQL Server 2017 (RTM-CU6) (KB4101464) - 14.0.3025.34 (X64) Apr 9 2018 18:00:41 Copyright (C) 2017 Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor) Subscriber: Microsoft SQL Server 2016 (SP2-CU1) (KB4135048) - 13.0.5149.0 (X64) May 19 2018 09:41:57 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor)
– Nicholas Saul
4 hours ago
Well, if that are the servers than it should not cause any issue, I am sure this are fresh installs and not upgrades. as compatibility says this should work fine source Unless there is distributor in picture.
– MarmiK
3 hours ago
Welcome, @NicholasSaul. Please edit your question to include the information you answered in a comment. Comments here aren't for extended discussion.
– Colin 't Hart
3 hours ago
Please specify compatibility mode of replicatoin database on both servers
SELECT compatibility_level FROM sys.databases WHERE name = 'DBName';– MarmiK
3 hours ago