SSDO Patch Release Notes v2.1.1

Last modified


Part no. - 765-0001-0300-B

Document attachment - SSDO v2.1.1 Release Notes

Thank you for deploying the StorSimple SharePoint Database Optimizer v2.1.1.  This document provides release notes identifying open issues with this product.

This document is broken into following sections:

Release Notes for Version 2.1.1

The following are the release notes for v2.1.1 of the StorSimple SharePoint Database Optimizer.




Comments and/or Workarounds

CSC-4343* When enabling RBS on a deployment with 200 or more databases, the web UI may time out while the operation is in progress. A refresh of the web page will result in the page loading with database checkboxes unchecked and no progress indication will be provided. Progress can be monitored via the w3wp process log under c:\programdata\storsimple. Once the operations completes, the user can refresh the web page and all enabled databases will be displayed with their checkboxes checked properly.
The log file name would be <timestamp>_w3wp.txt. To verify completion, look for the following entry: "Successfully completed updating RBS configuration."
CSC-1727 The use of a SQL Database Alias can cause the SSDO installation to fail.

When a SQL Server Alias ( is used in the SharePoint configuration instead of the database server name itself, the check to see if the database server is online fails.

Workaround- To work around this issue, create an entry in the <BootDrive>\Windows\system32\drivers\etc\hosts file specifying the name of the SQL Alias used and the IP address of the database server.

Example:            sssp1   

CSC-765 The StorSimple SharePoint Database Optimizer install may  incorrectly identify a WFE to be offline due to the firewall configuration.

The StorSimple SharePoint database optimizer installer has a built-in check to verify that all the WFEs are online during the install process.  The installer performs this check by pinging the WFEs in the SharePoint server farm. This check has been introduced to make sure that the installation process updates all the WFEs and leaves the farm in a consistent state.  Due to this check the installation may fail when the WFEs have a firewall enabled and cannot be pinged, or the user account under which the installation is being performed is not a member of the Administrators group.

Workaround– If you encounter this issue it is recommended that you retry the operation while logged in as a user with Administration privileges.  Ensure that the firewall on the WFEs is disabled, at least for the duration of the install.

CSC-558 SharePoint Content database  can get into an out of sync state if a pre-RBS enabled database backup is restored onto it.

The SharePoint database can get into an out of sync state if a pre-RBS database backup is restored onto it.

Workaround- To avoid this problem once RBS has been enabled on a SharePoint Content database, a full database backup, or cloud clone, should be taken. This backup can be used in the event a restore operation is required to be performed.

CSC-429 The StorSimple SharePoint Database Optimizer fails to install and reports an RBS install error on one of the WFEs and Application servers.

For the StorSimple SharePoint Database Optimizer installation to succeed, the SharePoint Timer service and Central Administration IIS Application Pool should be running with an account that has Administrative privileges on each of the SharePoint WFEs and Application servers.

Workaround- You can verify and change the privileges as follows:
Navigate to Start  → Administrative Tools → Services.
Scroll down to the SharePoint 2010 Timer service in SharePoint 2010, or SharePoint 2007 Timer if using SharePoint 2007.
Right click on the service name and select ‘Properties’.
In the 'Log On' tab, make sure that the account specified under 'This Account' has Administrator privileges.
If you make a change, make sure and restart the service.

To verify and change the privileges of the account for the Central Administration IIS application pool:
Navigate to Start → Administrative Tools  IIS Manager.
Access Application Pools  the 'Central Administration application pool' (e.g. SharePoint Central Administration v4).
Right click and select ‘Advanced Settings...’
Verify/change the Identity to an account that has Administrative privileges.
If you make a change, make sure to restart the service.



The SharePoint stsadm or Central Administration will not completely retract the StorSimple SharePoint Database Optimizer.

If the StorSimple SharePoint Database Optimizer needs to be uninstalled, do not use stsadm or the SharePoint Central Administration to Retract and Remove the solution because this will not disable BLOB externalization.

Workaround- Uninstall of the StorSimple SharePoint Database Optimizer should always be performed by re-running install package or from Windows Add/Remove Programs. Either method will ensure BLOB externalization is disabled and remove all files originally deployed by the install package.

CSC-372 BLOB store share validation may fail when Internet Explorer Enhanced Security is enabled.

When the user clicks the Update button on the StorSimple SharePoint Database optimizer (EBS) or StorSimple SharePoint Database optimizer (RBS) configuration in Central Administration, the following error message may be displayed even if the remote share is present and accessible on the remote server.

The specified BLOB store directory (\\ServerName\ShareName) does not exist, or you may not have permission to access it. Please correct this issue before continuing.

We have found this error to primarily be linked to the IE ESC (Internet Explorer Enhance Security Configuration) setting being on.

Workaround- To manage EBS or RBS on the server we recommend turning off the IE ESC using the procedure explained below.  Once the EBS or RBS configuration is complete you can re-enable IE ESC if you wish, however please note that you will have to disable it again the next time you have to make any modifications to the EBS or RBS settings. For instruction on how to configure ESC, please reference the following link:


EBS Maintainer may encounter a deadlock when executed under heavy SharePoint load.

The EBS Maintainer (StorSimple.SharePoint.EBSMaintainer.exe) task can encounter a deadlock when executed during periods of heavy SharePoint transaction load on the farm.  The following message is displayed on the console window or the StorSimple log file (under C:\ProgramData\StorSimple\).

ERROR: The program terminated with an exception (Exception: Transaction (Process ID 117) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.)

Workaround- This behavior is expected under heavy load. Rerunning the Maintainer task once the transaction load lessens will result in successful completion.

NOTE: The success or failure status of the EBS Maintainer is logged in StorSimple log file and not displayed in the Windows Task Scheduler.




Contacting Technical Support

Should you encounter any issues with your appliance, please do not hesitate to contact StorSimple Technical Support at:

  • Telephone: 1-800-642-7676
  • Web:
    • In the page presented, click on plus icon to expand the 'Get Technical Support' node. In the expanded pane, click on 'Get Microsoft Technical Support'.



Page statistics
437 view(s) and 3 edit(s)
Social share
Share this page?


This page has no custom tags.
This page has no classifications.