4

I am getting the following error while trying to configure FileStream in SQL server 2012.

There was an unknown error applying the filestream settings. check the parameters are valid. (0x80041008)

I am configuring it using SQL server configuration manager.

Where as I am able to setup it for SQL server 2008 R2.

Banketeshvar Narayan
  • 3,799
  • 4
  • 38
  • 46

3 Answers3

3

I had this same problem just yesterday.

In my case it was because I had a 64-bit Windows and a 32-Bit SQL Server.

You do not see the exact error, but if you try to do it with T-SQL, then the proper error comes up in SQL, telling you something about "WOW64" not supporting filestream.

I just uninstalled and installed the right bit version of SQL, and all worked 100% again.

Fred
  • 2,402
  • 4
  • 31
  • 58
  • Is there any other possibility for this error? I've got 64 bit windows 7 and my SQL Server 2008 R2 is also 64 bit which is evident from @@version - `Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1)` – RBT Dec 01 '16 at 00:07
  • To enable the feature first you have to enable the feature from SQL Server configuration manager UI. I've not seen any T-SQL anywhere to enable the feature for the SQL Server installation. You can only configure the `File Stream access level` using `EXEC sp_configure filestream_access_level, 2`. Can you please share the T-SQL script you are talking about which gives "WOW64" specific error. – RBT Dec 01 '16 at 00:10
  • This was LONG ago, I cannot remember this anymore... however, I'm sure the script you posted above was the one producing the "WOW64" error. You are also using SQL 2008, maybe that produces another error from SQL 2012. I cannot think of any other cause for this error, sorry! – Fred Dec 02 '16 at 10:53
  • I was finally able to fix the issue by installing SP2 patch of SQL Server 2008 R2. I've also added my experience as an answer in case it helps someone. Thanks for your response. – RBT Dec 02 '16 at 11:10
3

In my case the problem I was running the SQL Server 2014 configuration manager. While this usually shouldn't cause problems, in my case it did. Configuring FILESTREAM using the SQL Server 2012 configuration manager worked.

If it still doesn't work, make sure you're up-to-date. SQL Server 2012 has received quite a lot of patches (SP2, SP3, and some updates).

Sebazzz
  • 1,205
  • 2
  • 15
  • 33
0

TL;DR

I simply installed Service pack 2 (SP2) patch of SQL Server 2008 R2 and everything started working for me.

Read on if you want to know more. Configuration wise my box was all correct and the file stream feature should have been working on my default instance of SQL Server 2008 R2. Here are my box details:

Operating System: Windows 7 Ultitmate SP1 (64 Bit)
SQL Server Version: SQL Server 2008 R2 SP1

On SQL Server if I run this query select @@version it was returning following details:

Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

Whenever I opened SQL Server 2008 Configuration manager I will face this issue. Luckily I also had SQL Server 2014 installed on my machine. So I tried enabling File Stream feature from configuration manager GUI of SQL Server 2014 but it started giving error mentioned in current post.

I simply installed Service pack 2 (SP2) patch of SQL Server 2008 R2 and everything started working for me. SQL Server Configuration manager for 2008 R2 also works fine and I'm able to enable File Stream feature also without any trouble. SQL Server 2008 R2 SP2 can be downloaded from here.

Community
  • 1
  • 1
RBT
  • 24,161
  • 21
  • 159
  • 240