January 12, 2011 at 10:26 am
I've been trying to install SQL Server 2008 R2 and enable FILESTREAM on a workstation running Windows XP SP3.
If I try to enable it during setup, I get the error: 2114 – The Server service is not started
If I try to enable it after installation, I get: There was an unknown error applying the FILESTREAM settings.
If I try to enable it via the command line, using the filestream_enable.vbs script, I get: Method failed: Hr = -2147022782 (Duplicate share name)
The common denominator appears to be that the Server service is not running on my machine, in fact, when I try to start it via: Comupter Management>Services and Applications>Services, the Server does not show up in the Name list!
Searching deeper, I find ( http://support.microsoft.com/kb/128167 ) that the key is the Lanman Server, and that if it has been “Hidden” (likely, given corporate security protocols) then you can only change it via the registry. And sure enough, the registry parameters to enable auto-configuration of the Server service are all missing!
Before I attempt to edit the registry (I'd rather not), I want to make sure that a) the Server service is indeed required to enable FILESTREAM, and b) There is no other way if LanmanServer configuration is "hidden" on my machine."
Thanks,
eberg
January 12, 2011 at 10:47 am
If you go into configuration manager for the instance in question and open the properties for that instance, you can't enable FILESTREAM on the appropriate tab? It sounds like it wasn't installed to me. You may need to try doing a repair on the install.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 12, 2011 at 11:32 am
Grant Fritchey (1/12/2011)
If you go into configuration manager for the instance in question and open the properties for that instance, you can't enable FILESTREAM on the appropriate tab? It sounds like it wasn't installed to me. You may need to try doing a repair on the install.
Tried that, that's when I get the "...unknown error applying the FILESTREAM settings." Incidentally, there is a Microsoft KB, and some blog entries on this, and a HotFix from Microsoft for Windows Server 2003. This related to the problem of updating to SQL Server 2008 from an earlier version, and incompatibility with NT file paths. I'm doing a clean install. Either way, there is no HotFix for Windows XP SP3, and if this were the root cause I should have been able to enable FILESTREAM during setup (similar dialog) or using the CMD line script, both fail. From what I gather is that the common theme is for of these errors is that the Server service handles naming functions of the share name instance.
January 12, 2011 at 1:13 pm
berg.ec (1/12/2011)
Grant Fritchey (1/12/2011)
If you go into configuration manager for the instance in question and open the properties for that instance, you can't enable FILESTREAM on the appropriate tab? It sounds like it wasn't installed to me. You may need to try doing a repair on the install.Tried that, that's when I get the "...unknown error applying the FILESTREAM settings." Incidentally, there is a Microsoft KB, and some blog entries on this, and a HotFix from Microsoft for Windows Server 2003. This related to the problem of updating to SQL Server 2008 from an earlier version, and incompatibility with NT file paths. I'm doing a clean install. Either way, there is no HotFix for Windows XP SP3, and if this were the root cause I should have been able to enable FILESTREAM during setup (similar dialog) or using the CMD line script, both fail. From what I gather is that the common theme is for of these errors is that the Server service handles naming functions of the share name instance.
Sorry. Not one I've run into.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 13, 2011 at 1:59 pm
ANSWER: Yes
Caveat: Unless you don't need to enable FILESTREAM for fle I/O streaming access
The Server service (Lanman Server in Registry) handles functions associated with the Windows share, e.g., SQLEXPRESSLOCAL. So the Server service must be running to check the Enable FILESTREAM for fle I/O streaming access box. However, if you dont need I/O streaming, and check only the Enable FILESTREAM for Transact-SQL access box, you can enable FILESTREAM without the Server service running.
In my case, I only needed Enable FILESTREAM for Transact-SQL access, so I only checked the first box and installation proceeded without error. I can also change this option post-install.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply