none
Remote Blob Storage - Additional Webapplication

    Question

  • Hello,

    we have a SharePoint 2010 Farm running with an existing Web Application configured to use RBS - works fine.

    now that we tried to configure a second Web Application to use RBS too (oh yes ... we tried and tried and tried) the configuration & activation of RBS works fine.

    But when we try to upload a document we get the error on the web interface:

    The URL <<URL>> 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.

    checking the event logs we see:

    Level: Error, Source: RBS, Event ID: 4

    An error occurred while reading extension file C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Provider Libraries\Filestream Provider\\Microsoft.Data.BlobStores.FilestreamBlobStore.dll. System.TypeLoadException: Failure has occurred while loading a type.   at Microsoft.Data.SqlRemoteBlobs.ProviderClass.Initialize()Operation: AssemblyLoadBlobStoreId: 0Log Time: 22.02.2012 15:56:15

    Level: Error, Source: RBS, Event ID: 0

    Blob store <FilestreamProvider_1> threw this exception:

    Operation: Unknown

    BlobStoreId: 1

    Log Time: 23.02.2012 11:55:18

    Exception: Microsoft.Data.SqlRemoteBlobs.BlobStoreException: There was a generic database error. For more information, see the included exception. --->

    System.Data.SqlClient.SqlException: 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: Named Pipes

    Provider, error: 40 - Could not open a connection to SQL Server)   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean

    breakConnection)   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)  

    at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire,

    Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)  

    at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64

    timerExpire, SqlConnection owningObject)   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean

    redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)  

    at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject,

    SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)  

    at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo,

    String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)  

    at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool,

    DbConnection owningConnection)   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection,

    DbConnectionPool pool, DbConnectionOptions options)   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)  

    at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)  

    at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)  

    at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)  

    at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)  

    at System.Data.SqlClient.SqlConnection.Open()  

    at Microsoft.Data.BlobStores.FilestreamBlobStore.FilestreamStoreLibrary.Initialize(ConfigItemList commonConfiguration,

    ConfigItemList coreConfiguration, ConfigItemList extendedConfiguration, BlobStoreCredentials[] credentials)   --- End of inner exception stack trace ---  

    at Microsoft.Data.BlobStores.FilestreamBlobStore.FilestreamStoreLibrary.Initialize(ConfigItemList commonConfiguration, ConfigItemList coreConfiguration,

    ConfigItemList extendedConfiguration, BlobStoreCredentials[] credentials)  

    at Microsoft.Data.BlobStores.BlobStore.InitializeInternal(Request request)BlobStoreException Code: OperationFailedAuthoritative

    BUT THE RBS CONFIGURATION IS OK. The mssqlrbs-tables are created, I see the GUID-folders beeing created in the Blobstore-folder when running the CMD commands on the WFEs .. everything works fine .. until we try to upload.

    who configured RBS for several Web Applications already? Is there something special? ...already frustrated -_-"

    Thanks & BR,J

    Thursday, February 23, 2012 12:18 PM

Answers

  • After opening a MS Case it seems like the problem is that the old RBS used a pre-RTM Remote Blob Store binary (wrong link in the old technet-article). This has negative affect on the new, correct one.

    Solution suggested by MS (basics):

    1. Migrating Content back to DB
    2. Deleting Remote Blob Storage
    3. Install & configure new Remote Blob Storage
    • Marked as answer by JHohensinn Tuesday, April 17, 2012 8:18 AM
    • Unmarked as answer by JHohensinn Friday, November 02, 2012 11:34 AM
    • Marked as answer by JHohensinn Friday, November 02, 2012 11:34 AM
    Tuesday, March 06, 2012 1:05 PM

All replies

  • Check that your server allows TCP/IP connections (in SQL Server Configuration Manager for your instance server protocols).

    Marek Chmel, WBI Systems (MCTS, MCITP, MCT, CCNA)
    Please Mark As Answer if my post solves your problem or Vote As Helpful if a post has been helpful for you.

    Thursday, February 23, 2012 12:49 PM
  • Hello,

    yes .. we tried (both) - but it did not resolve anything ..

    The funny thing is: we already have a web application using RBS perfectly fine! It's just the second one that has this strange issue!

    Monday, February 27, 2012 9:43 AM
  • hmm.. how can I remove an existing RBS Provider? I cannot find any hints on the internet? I'd like to remove the existing one and configure the RBS completely new. Is this possible at all?

    Monday, February 27, 2012 2:11 PM
  • After opening a MS Case it seems like the problem is that the old RBS used a pre-RTM Remote Blob Store binary (wrong link in the old technet-article). This has negative affect on the new, correct one.

    Solution suggested by MS (basics):

    1. Migrating Content back to DB
    2. Deleting Remote Blob Storage
    3. Install & configure new Remote Blob Storage
    • Marked as answer by JHohensinn Tuesday, April 17, 2012 8:18 AM
    • Unmarked as answer by JHohensinn Friday, November 02, 2012 11:34 AM
    • Marked as answer by JHohensinn Friday, November 02, 2012 11:34 AM
    Tuesday, March 06, 2012 1:05 PM