So let's say you deployed Remote Blob Storage for SharePoint. Then later you decided you didn't want to deploy it for a particular content database and retracted the data from the blob back into the SQL content database.
Then later....maybe much later....uploads to your SharePoint site start failing. Maybe it's after a Cumulative Update. Maybe it's after a SQL upgrade. You see the following in your ULS logs:
System.Runtime.InteropServices.COMException: The URL 'Documents/somedoc.docx' 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.
Failed in GetStreamInfo: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Data.SqlRemoteBlobs.RemoteBlobUsageException: The specified blob store <1> could not be found in the current database.
What do you do?
There are a couple solutions that work for other people, then there's the solution that worked for us:
1. Ensure Remote Blob Storage is set up correctly. https://technet.microsoft.com/en-us/library/ee748631.aspx
2. Ensure the Application Pool account that hosts the Web App where your Content Database lives has the correct RBS permissions.
For us, the fix was actually ensuring the Content Database that was no longer using RBS was ACTUALLY not using RBS. It got confused, and we had to straighten it out with Powershell. The script for the fix was fairly straightforward:
add-pssnapin Microsoft.SharePoint.Powershell
$cdb=get-SPContentDatabase some_content_database
$rbs=$cdb.RemoteBlobStorageSettings
$rbs.SetActiveProviderName("")
***
Using this, the Active Provider for RBS was disabled. As soon as we ran this, we were then able to upload files without trouble to the SharePoint sites that were operating in that Content Database.
Hope this helps someone!
