Installing And Configuring RBS On SharePoint 2013 No Content Database Tables Fix

I got called into a laundry, dry cleaning, coin laundry, equipment and supplies company this morning to aid their enterprise architect with a problem that he was running into when attempting to install/configure RBS on SharePoint 2013. Following the procedures detailed on the Microsoft website, located here:

everything during his intallation appeared to complete correctly. From a farm architecture standpoint, nothing fantastic, just a WFE and a dedicated SQL box.

However he recieved this error:

Remote Blob Storage on the database has failed with error message:


A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 25 – Connection string is not valid)Setup will continue the installation.MSI (s) (7C:50) [18:38:02:100]: Executing op: CustomActionSchedule(Action=RunFSSetupScripts,ActionType=1025,Source=BinaryData,Target=FilestreamInstall,CustomActionData=MYSERVERNAME\MSSQLSERVER;WSS_Content;C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Provider Libraries\Filestream Provider\FilestreamProviderSetup.sql;1;username;defaultPassword;MYSERVERNAME\MSSQLSERVER;WSS_Content;RBSFilestreamProvider;PRIMARY;;C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Provider Libraries\Filestream Provider\RegisterFilestreamProvider.sql;FilestreamProvider_1;x=@FILEGROUPNAME@=RBSFilestreamProvider;x=@DATAFILEGROUPNAME@=PRIMARY;s=@STORENAME@=FilestreamProvider_1;x=




The fix for this particular error is not too bad, however there a bunch of different things that you are going to have to check:

  1. Check that FILESTREAM is enabled on the SQL server
  2. Ensure that the BLOB store has been provisioned correctly (make sure that the directory is created)
  3. Make sure that the named pipes is enabled and that SQL Server browsing is enabled.
  4. The last step is the most common, and DEFINITLY the one I see the most. When you are settings up RBS, in the instructions you will see within the instructions the directions that reference RBS_amd64.msi as a package to run in between the installations. In fact, you need to use the x64 bit library, not the AMD, which you can find here: Once you download this, DO NOT RUN THE FILE.  Once downloaded, execute the following command, replacing the relevant values to match your environment:

msiexec /qn /lvx* rbs_install_log.txt /i RBS.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME=”WSS_Content” DBINSTANCE=”InstanceName” FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1