Sharepoint RBS.msi idoes not run/install on BLOB storage server
Article ID: SP0001 When deploying CommVault RBS provider, the RBS.msi is does not run / install on BLOB storage server.
1. Upon successfully enabling SharePoint Content Management Components within SharePoint Central Admin, the RSB cache location automatically changed.
2. Attempting to enable RBS on multiple web servers via the ‘Enable RBS’ button within Sharepoint Central Admin, results in one success and the others in failure.
### ### Installrbs --- Exception Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SPContentDatabase Name= was updated by , in the OWSTIMER (1320) process, on machine . View the tracing log for more information about the conflict.
### UpdateStatus --- Update Status for DB Web Server status Failed. 1
From Sharepoint trace log:
UpdatedConcurrencyException: The object SPContentDatabase Name= was updated by another user. Determine if these changes will conflict, resolve any differences, and reapply the second change. This error may also indicate a programming error caused by obtaining two copies of the same object in a single thread. Previous update information: User: Process:OWSTIMER (1320) Machine: Time: Current update information: User: Process:OWSTIMER (1880) Machine: Time:
- Older 3rd party RBS settings/binaries - even though they were removed - may still be conflicting with the current web app and content DB and causing unexpected results.
- When one front end web server completes the RBS configuration, internally SharePoint API updates a persistent farm object behind the scenes. The same persistent object is shared by all front end web servers. Once one of the front end web servers RBS configuration is completed, Commvault attempts to install RBS on remaining front end webservers. As the first front end server is still busy updating persistent objects, this causes an update conflict error.
- User Provided a wrong BLOB location which doesn’t exist.
- No permissions to access the BLOB location.
- Timer service isn’t started on the other WFE servers.
- Configured SharePoint timer service in the Farm on multiple WFE’s with different accounts .
- Completely remove the 3rd party RBS provider and reinstall Commvault’s RBS provider.
- Install Sevice Pack 9 which includes updates 15646 to correct other unexpected behaviour.