If you are developing a custom RBS provider or using the MSFT sample provider available here , chances are you will be encountered with the following error
The URL ‘Library/Document’ 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
Since the above guide is more related to the FILESTREAM provider, the troubleshooting steps are not that helpful. However, you do get an idea of how to debug this. Looking at the ULS logs you may find the following entry
No provider of type <File> found. Check the server configuration or install the provider on the client
Still not very helpful, but looking at the event log you find “Could not load file or assembly ‘<ProviderAssembly>’ or one of its dependencies. Failed to grant permission to execute.” Surely, this is a Code Access Security issue since the Provider Assembly was not deployed in GAC during installation.
There are two possible resolutions of this issue
- Set the WSS_Minimum trust level of your SharePoint web.config to Full (Not recommended for Production environments)
- Install your Provider assembly in the GAC.
You fix the above error only to find that it still exists
This time around it is because the RBS Client Library executes and loads the custom Provider in the context of SharePoint application pool (with default impersonate=false). You need to make sure that the user account configured in the application pool has rights to read and write on the folder (Local or Network) which is designated as the external blob store.
Hopefully, this will get you going with your new RBS configuration.http://download.microsoft.com/download/9/5/2/9521D8DA-5D3C-4817-BB9D-B5B1BD293365/SQL_Server_2008_R2_Remote_Blob_Storage.doc.