Is .NET Framework 3.5 still needed with a SQL Server 2017 installation to utilize Database Mail?
I'm guessing .NET Framework 3.5 is still needed to use Database Mail with SQL Server 2017? As I had to include this on my SQL Server 2016 installs on Server 2016 not that long ago.
I was unable to find a definitive answer via the web, surprisingly, maybe it goes unsaid.
sql-server installation sql-server-2017 database-mail
add a comment |
I'm guessing .NET Framework 3.5 is still needed to use Database Mail with SQL Server 2017? As I had to include this on my SQL Server 2016 installs on Server 2016 not that long ago.
I was unable to find a definitive answer via the web, surprisingly, maybe it goes unsaid.
sql-server installation sql-server-2017 database-mail
add a comment |
I'm guessing .NET Framework 3.5 is still needed to use Database Mail with SQL Server 2017? As I had to include this on my SQL Server 2016 installs on Server 2016 not that long ago.
I was unable to find a definitive answer via the web, surprisingly, maybe it goes unsaid.
sql-server installation sql-server-2017 database-mail
I'm guessing .NET Framework 3.5 is still needed to use Database Mail with SQL Server 2017? As I had to include this on my SQL Server 2016 installs on Server 2016 not that long ago.
I was unable to find a definitive answer via the web, surprisingly, maybe it goes unsaid.
sql-server installation sql-server-2017 database-mail
sql-server installation sql-server-2017 database-mail
edited 1 hour ago
Tony Hinkle
2,6851423
2,6851423
asked 4 hours ago
Eric SwiggumEric Swiggum
16816
16816
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
No, it is not required for SQL Server 2017. The issue with Database Mail not working was fixed in 2016 SP1 CU2, and 2016 RTM CU2:
FIX: SQL Server 2016 Database Mail does not work on a computer that does not have the .NET Framework 3.5 installed or stops working after applying SQL Server update
I know of several SQL Server 2016 and 2017 systems that are installed without .NET 3.51, and Database Mail is working fine.
Note that .NET Framework 3.5 was not included in Hardware and Software Requirements for Installing SQL Server, and that the SQL Server 2016 and SQL Server 2017 view of this page is the same. The Database Mail issue was considered a defect in SQL Server 2016 and was fixed accordingly.
Great, thanks for the clarification, yes I recall the dubious CU for SQL 2016 that broke database mail, so I ran around verifying that .net 3.5 was installed. Good times.
– Eric Swiggum
1 hour ago
add a comment |
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
});
}
});
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%2f230628%2fis-net-framework-3-5-still-needed-with-a-sql-server-2017-installation-to-utiliz%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
No, it is not required for SQL Server 2017. The issue with Database Mail not working was fixed in 2016 SP1 CU2, and 2016 RTM CU2:
FIX: SQL Server 2016 Database Mail does not work on a computer that does not have the .NET Framework 3.5 installed or stops working after applying SQL Server update
I know of several SQL Server 2016 and 2017 systems that are installed without .NET 3.51, and Database Mail is working fine.
Note that .NET Framework 3.5 was not included in Hardware and Software Requirements for Installing SQL Server, and that the SQL Server 2016 and SQL Server 2017 view of this page is the same. The Database Mail issue was considered a defect in SQL Server 2016 and was fixed accordingly.
Great, thanks for the clarification, yes I recall the dubious CU for SQL 2016 that broke database mail, so I ran around verifying that .net 3.5 was installed. Good times.
– Eric Swiggum
1 hour ago
add a comment |
No, it is not required for SQL Server 2017. The issue with Database Mail not working was fixed in 2016 SP1 CU2, and 2016 RTM CU2:
FIX: SQL Server 2016 Database Mail does not work on a computer that does not have the .NET Framework 3.5 installed or stops working after applying SQL Server update
I know of several SQL Server 2016 and 2017 systems that are installed without .NET 3.51, and Database Mail is working fine.
Note that .NET Framework 3.5 was not included in Hardware and Software Requirements for Installing SQL Server, and that the SQL Server 2016 and SQL Server 2017 view of this page is the same. The Database Mail issue was considered a defect in SQL Server 2016 and was fixed accordingly.
Great, thanks for the clarification, yes I recall the dubious CU for SQL 2016 that broke database mail, so I ran around verifying that .net 3.5 was installed. Good times.
– Eric Swiggum
1 hour ago
add a comment |
No, it is not required for SQL Server 2017. The issue with Database Mail not working was fixed in 2016 SP1 CU2, and 2016 RTM CU2:
FIX: SQL Server 2016 Database Mail does not work on a computer that does not have the .NET Framework 3.5 installed or stops working after applying SQL Server update
I know of several SQL Server 2016 and 2017 systems that are installed without .NET 3.51, and Database Mail is working fine.
Note that .NET Framework 3.5 was not included in Hardware and Software Requirements for Installing SQL Server, and that the SQL Server 2016 and SQL Server 2017 view of this page is the same. The Database Mail issue was considered a defect in SQL Server 2016 and was fixed accordingly.
No, it is not required for SQL Server 2017. The issue with Database Mail not working was fixed in 2016 SP1 CU2, and 2016 RTM CU2:
FIX: SQL Server 2016 Database Mail does not work on a computer that does not have the .NET Framework 3.5 installed or stops working after applying SQL Server update
I know of several SQL Server 2016 and 2017 systems that are installed without .NET 3.51, and Database Mail is working fine.
Note that .NET Framework 3.5 was not included in Hardware and Software Requirements for Installing SQL Server, and that the SQL Server 2016 and SQL Server 2017 view of this page is the same. The Database Mail issue was considered a defect in SQL Server 2016 and was fixed accordingly.
edited 1 hour ago
answered 2 hours ago
Tony HinkleTony Hinkle
2,6851423
2,6851423
Great, thanks for the clarification, yes I recall the dubious CU for SQL 2016 that broke database mail, so I ran around verifying that .net 3.5 was installed. Good times.
– Eric Swiggum
1 hour ago
add a comment |
Great, thanks for the clarification, yes I recall the dubious CU for SQL 2016 that broke database mail, so I ran around verifying that .net 3.5 was installed. Good times.
– Eric Swiggum
1 hour ago
Great, thanks for the clarification, yes I recall the dubious CU for SQL 2016 that broke database mail, so I ran around verifying that .net 3.5 was installed. Good times.
– Eric Swiggum
1 hour ago
Great, thanks for the clarification, yes I recall the dubious CU for SQL 2016 that broke database mail, so I ran around verifying that .net 3.5 was installed. Good times.
– Eric Swiggum
1 hour ago
add a comment |
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%2f230628%2fis-net-framework-3-5-still-needed-with-a-sql-server-2017-installation-to-utiliz%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