Nov 3, 2010 at 9:42 PM
Edited Nov 3, 2010 at 9:42 PM
I believe you are using the wrong command to enable RBS in the second content database. It appears you are using a command that is designed to install the FILESTREAM provider on a second SharePoing WFE server.
I was able to successfully enable RBS using the FILESTREAM provider on a second content database by following this procedure:
1. I created a new content database (and site collection). The new content database is named
2. I executed this script in the context of the new database in SQL Management Studio (Note that I added a "2" to some of the values):
if not exists (select * from sys.symmetric_keys where name = N'##MS_DatabaseMasterKey##')create master key encryption by password = N'Admin Key Password !2#4'
if not exists (select groupname from sysfilegroups where groupname=N'RBSFilestreamProvider2')alter database WSS_RBSDemo2_Content
add filegroup RBSFilestreamProvider2 contains filestream
alter database WSS_RBSDemo2_Content add file (name = RBSFilestreamFile2, filename = 'c:\Blobstore2') to filegroup RBSFilestreamProvider2
3. I executed this command in a command prompt with "Run as Administrator":
C:\Users\spadmin>msiexec /qn /lvx* c:\software\rbs_install_log2.txt /i c:\software\rbs_x64.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME="WSS_RBSDemo2_Content" DBINSTANCE="SPX" FILESTREAMFILEGROUP=RBSFilestreamProvider2
NOTE: In the command above my c:\software folder probably won't apply to your environment. SPX is the name of my SQL Server and is used for DBINSTANCE. Notice that the value of FILESTREAMFILEGROUP matches the name of the FILESTREAM type filegroup
created in step 2 above. The FILESTREAMSTORENAME is FilestreamProvider_2 and not FilestreamProvider_1 to differentiate it from the first FILESTREAMSTORENAME that I created in the first site collection.
I was able to upload a file to the new site collection. The file was successfully streamed to the new BLOB store folder location (c:\Blobstore2).