Hi ,

After configuring the content database for RBS as per the MSDN article (

http://technet.microsoft.com/en-us/library/ee748631(v=office.15).aspx#library). we are getting the below error when we try to upload any file to document library. 

The URL '<filename> is invalid.  It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web.

The sharepoint log has the following details:

Microsoft.Data.SqlRemoteBlobs.RemoteBlobConfigurationException: No provider of type <Filestream> found. Check the server configuration or install the provider on the client.

System.Runtime.InteropServices.COMException: The URL '<filename>' is invalid.  It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web.    at Microsoft.SharePoint.Library.SPRequestInternalClass.PutFile(String bstrUrl, String bstrWebRelativeUrl, Object punkFile, Int64 cbFile, Object punkSPFileMgr, Object

punkFFM, Int64 PutFileOpt, String bstrCreatedBy, String bstrModifiedBy, Int32 iCreatedByID, Int32 iModifiedByID, Object varTimeCreated, Object varTimeLastModified, Object varProperties, String bstrCheckinComment, String bstrLockIdMatch, String bstEtagToMatch, Int32 lockType, String lockId, Int32 minutes, Int32 fRefreshLock, Int32 bValidateReqFields, Guid gNewDocId, SPFileSaveParams sfsp, SPFileInfo& pFileProps, UInt32& pdwVirusCheckStatus, String& pVirusCheckMessage, String& pEtagReturn, Byte& piLevel, Int32& pbIgnoredReqProps)    at Microsoft.SharePoint.Library.SPRequest.PutFile(String bstrUrl, String bstrWebRelativeUrl, Object punkFile, Int64 cbFile, Object punkSPFileMgr, Object punkFFM, Int64 PutFileOpt, String bstrCreatedBy, String bstrModifiedBy, Int32 iCreatedByID, Int32 iModifiedByID, Object varTimeCreated, Object varTimeLastModified, Object varProperties, String bstrCheckinComment, String bstrLockIdMatch, String bstEtagToMatch, Int32 lockType, String lockId, Int32 minutes, Int32 fRefreshLock, Int32 bValidateReqFields, Guid gNewDocId, SPFileSaveParams sfsp, SPFileInfo& pFileProps, UInt32& pdwVirusCheckStatus, String& pVirusCheckMessage, String& pEtagReturn, Byte& piLevel, Int32& pbIgnoredReqProps)

I tried both 2008 sever RBS.msi and RBS_amd64.msi, but did not work.

Thanks,

Pat

Why are you using RBS? In 2013 it is mostly a bad choice. There are a few areas where it makes sense but in the vast majority of cases it is no longer relevant or useful.

Hi Alex,

Do you have any reference article from Microsoft which says that RBS is not recommended in SharePoint-2013? So that I can provide the same to management here?

 We are upgrading a SharePoint-2010 application which is currently using RBS(it has got around 6 content databases with each one has around 150 GB of data). When I do a upgrade to SP-2013 using database attachment method, I get an error saying I need to enable Filestream in target database environment because source content database is using RBS. So I have to enable Filestream/RBS in my target environment as well, unless I disable in my source database before taking the production backup

Thanks,

Pat

• Edited by patnikP Sunday, December 07, 2014 6:48 AM edited

Can some please confirm whats the right RBS client library for SharePoint 2013(Enterprise) and SQL Server 2014(Enterprise).

I have configured RBS as per the below MSDN document but its not working

http://technet.microsoft.com/en-us/library/ee748631(v=office.15).aspx#library

No reference article, it's something that's still being debated by various people. The default position of any install of SharePoint should be to stay as close to stock as possible and to avoid complications unless they bring real value to the business.

What do you think that you will get out of RBS?

Hi Pat,

To migrate RBS enabled Content DB, you first need to backup site collection (which will take backup of content db + files on drive via RBS). Once done, restore to another SP 2010 farm. Now at third level, follow attach / deattach method for migration. Lastly, when you are done with migration, enable the RBS on SQL Server 2014.