I'm trying to enable SQL Filestream on Windows Server 2012 and SQL Server 2016 64 bit, Management Studio 2017
The machine config is Windows Server 2012, 64 Bit SQL Server 2016, and SQL Server Management Studio 2017. When I use SQL Server Configuration Manager to enable filestream, it gives me an error that I do not know how to get around.
There was an unknown error applying the FILESTREAM settings. check the
parameters are valid. (0x80041008)
sql-server ssms filestream windows-server-2012-r2 configuration-manager
edited Dec 18 '18 at 20:28
MDCCL
6,85331745
asked Dec 17 '18 at 17:43
samsam
1
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
The machine config is Windows Server 2012, 64 Bit SQL Server 2016, and SQL Server Management Studio 2017. When I use SQL Server Configuration Manager to enable filestream, it gives me an error that I do not know how to get around.
There was an unknown error applying the FILESTREAM settings. check the
parameters are valid. (0x80041008)
sql-server ssms filestream windows-server-2012-r2 configuration-manager
edited Dec 18 '18 at 20:28
MDCCL
6,85331745
asked Dec 17 '18 at 17:43
samsam
1
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Windows and SQL Server both are 64-bit?
– CR241
Dec 17 '18 at 18:22
see this SO question
– Kin
Dec 17 '18 at 18:41
1
I've removed the image in your question because it only shows the same error message you have pointed out in your text. You can add it again following this link and clicking rollback button of any of the other edits.
– McNets
Dec 17 '18 at 20:37
add a comment |
The machine config is Windows Server 2012, 64 Bit SQL Server 2016, and SQL Server Management Studio 2017. When I use SQL Server Configuration Manager to enable filestream, it gives me an error that I do not know how to get around.
There was an unknown error applying the FILESTREAM settings. check the
parameters are valid. (0x80041008)
sql-server ssms filestream windows-server-2012-r2 configuration-manager
edited Dec 18 '18 at 20:28
MDCCL
6,85331745
asked Dec 17 '18 at 17:43
samsam
1
The machine config is Windows Server 2012, 64 Bit SQL Server 2016, and SQL Server Management Studio 2017. When I use SQL Server Configuration Manager to enable filestream, it gives me an error that I do not know how to get around.
There was an unknown error applying the FILESTREAM settings. check the
parameters are valid. (0x80041008)
sql-server ssms filestream windows-server-2012-r2 configuration-manager
sql-server ssms filestream windows-server-2012-r2 configuration-manager
edited Dec 18 '18 at 20:28
MDCCL
6,85331745
asked Dec 17 '18 at 17:43
samsam
1
edited Dec 18 '18 at 20:28
MDCCL
6,85331745
asked Dec 17 '18 at 17:43
samsam
1
edited Dec 18 '18 at 20:28
MDCCL
6,85331745
edited Dec 18 '18 at 20:28
MDCCL
6,85331745
edited Dec 18 '18 at 20:28
MDCCL
6,85331745
6,85331745
asked Dec 17 '18 at 17:43
samsam
1
asked Dec 17 '18 at 17:43
samsam
1
asked Dec 17 '18 at 17:43
samsam
1
1
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Windows and SQL Server both are 64-bit?
– CR241
Dec 17 '18 at 18:22
see this SO question
– Kin
Dec 17 '18 at 18:41
1
I've removed the image in your question because it only shows the same error message you have pointed out in your text. You can add it again following this link and clicking rollback button of any of the other edits.
– McNets
Dec 17 '18 at 20:37
add a comment |
Windows and SQL Server both are 64-bit?
– CR241
Dec 17 '18 at 18:22
see this SO question
– Kin
Dec 17 '18 at 18:41
1
I've removed the image in your question because it only shows the same error message you have pointed out in your text. You can add it again following this link and clicking rollback button of any of the other edits.
– McNets
Dec 17 '18 at 20:37
Windows and SQL Server both are 64-bit?
– CR241
Dec 17 '18 at 18:22
Windows and SQL Server both are 64-bit?
– CR241
Dec 17 '18 at 18:22
see this SO question
– Kin
Dec 17 '18 at 18:41
see this SO question
– Kin
Dec 17 '18 at 18:41
1
1
I've removed the image in your question because it only shows the same error message you have pointed out in your text. You can add it again following this link and clicking rollback button of any of the other edits.
– McNets
Dec 17 '18 at 20:37
I've removed the image in your question because it only shows the same error message you have pointed out in your text. You can add it again following this link and clicking rollback button of any of the other edits.
– McNets
Dec 17 '18 at 20:37
add a comment |
1 Answer
1
active
oldest
votes
Root Cause?
During October we installed SQL Server 2016 on the server – but the desktop icons were still set to SQL Server 2017. When I used the 2016 Configuration Manager, it seemed to work.
Multiple versions installed on TEST Server:
Configuration manager on TEST Server with Configuration Manager 2017:
SQL Server Version on TEST Server:
Using SQL Server 2016 Configuration Manager:
So basically we were running the wrong version of configuration manager. Also we did a server restart. When I had previously tried to configure it on both 2016, 2017 configuration manager, it didn't work.
edited Dec 18 '18 at 20:27
MDCCL
6,85331745
answered Dec 18 '18 at 19:40
samsam
1
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%2f225189%2fim-trying-to-enable-sql-filestream-on-windows-server-2012-and-sql-server-2016-6%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
Root Cause?
During October we installed SQL Server 2016 on the server – but the desktop icons were still set to SQL Server 2017. When I used the 2016 Configuration Manager, it seemed to work.
Multiple versions installed on TEST Server:
Configuration manager on TEST Server with Configuration Manager 2017:
SQL Server Version on TEST Server:
Using SQL Server 2016 Configuration Manager:
So basically we were running the wrong version of configuration manager. Also we did a server restart. When I had previously tried to configure it on both 2016, 2017 configuration manager, it didn't work.
edited Dec 18 '18 at 20:27
MDCCL
6,85331745
answered Dec 18 '18 at 19:40
samsam
1
add a comment |
Root Cause?
During October we installed SQL Server 2016 on the server – but the desktop icons were still set to SQL Server 2017. When I used the 2016 Configuration Manager, it seemed to work.
Multiple versions installed on TEST Server:
Configuration manager on TEST Server with Configuration Manager 2017:
SQL Server Version on TEST Server:
Using SQL Server 2016 Configuration Manager:
So basically we were running the wrong version of configuration manager. Also we did a server restart. When I had previously tried to configure it on both 2016, 2017 configuration manager, it didn't work.
edited Dec 18 '18 at 20:27
MDCCL
6,85331745
answered Dec 18 '18 at 19:40
samsam
1
add a comment |
Root Cause?
During October we installed SQL Server 2016 on the server – but the desktop icons were still set to SQL Server 2017. When I used the 2016 Configuration Manager, it seemed to work.
Multiple versions installed on TEST Server:
Configuration manager on TEST Server with Configuration Manager 2017:
SQL Server Version on TEST Server:
Using SQL Server 2016 Configuration Manager:
So basically we were running the wrong version of configuration manager. Also we did a server restart. When I had previously tried to configure it on both 2016, 2017 configuration manager, it didn't work.
edited Dec 18 '18 at 20:27
MDCCL
6,85331745
answered Dec 18 '18 at 19:40
samsam
1
Root Cause?
During October we installed SQL Server 2016 on the server – but the desktop icons were still set to SQL Server 2017. When I used the 2016 Configuration Manager, it seemed to work.
Multiple versions installed on TEST Server:
Configuration manager on TEST Server with Configuration Manager 2017:
SQL Server Version on TEST Server:
Using SQL Server 2016 Configuration Manager:
So basically we were running the wrong version of configuration manager. Also we did a server restart. When I had previously tried to configure it on both 2016, 2017 configuration manager, it didn't work.
edited Dec 18 '18 at 20:27
MDCCL
6,85331745
answered Dec 18 '18 at 19:40
samsam
1
edited Dec 18 '18 at 20:27
MDCCL
6,85331745
edited Dec 18 '18 at 20:27
MDCCL
6,85331745
edited Dec 18 '18 at 20:27
MDCCL
6,85331745
6,85331745
answered Dec 18 '18 at 19:40
samsam
1
answered Dec 18 '18 at 19:40
samsam
1
answered Dec 18 '18 at 19:40
samsam
1
1
add a comment |
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%2f225189%2fim-trying-to-enable-sql-filestream-on-windows-server-2012-and-sql-server-2016-6%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
Windows and SQL Server both are 64-bit?
– CR241
Dec 17 '18 at 18:22
see this SO question
– Kin
Dec 17 '18 at 18:41
1
I've removed the image in your question because it only shows the same error message you have pointed out in your text. You can add it again following this link and clicking rollback button of any of the other edits.
– McNets
Dec 17 '18 at 20:37