StoragePoint 6.0 - Known Issues

Upgrade Support from Previous Versions of StoragePoint

While Quest supports the latest two releases of StoragePoint as well as upgrades to the current release from the last two releases, often customers find themselves upgrading from versions that are no longer supported. Below is a chart of upgrade scenarios that will work. For versions older than those listed, an interim upgrade to version 5.5 will be required.

Deprecated Data Types

Ntext, text, and image data types should not be used with StoragePoint as future versions of SQL server may remove them.

Modern UI for SharePoint 2019

SharePoint 2019 introduced a new look and feel for the user interface. StoragePoint links will work on this new user interface, but some additional configuration is necessary.

A Site Collection Feature will be deployed to SharePoint 2019 farms as of the 5.9.1 release. This feature should be enabled on the site collection for full StoragePoint user interface functionality.

Before activating the Site Collection Feature, an App Catalog must be configured for the web application, as well as an App Management service application.

Please reference the following articles for provisioning these resources.

https://docs.microsoft.com/en-us/sharepoint/administration/configure-an-environment-for-apps-for-sharepoint#configure-the-subscription-settings-and-app-management-service-applications

https://docs.microsoft.com/en-us/sharepoint/administration/manage-the-app-catalog

When these steps are done, open the Site Collection Features (Gear Icon>Site Info>View All Site Settings), scroll to StoragePoint Custom Actions and SPFx Extension for SharePoint 2019 and click Activate.

BLOBS Not Being Removed by UBC

Sometimes it may seem that BLOBS that should be removed by UBC are not getting removed. This may happen when items are removed from SharePoint, both recycle bins, but it is still stored in the content database. After the Database is cleared, the UBC will remove those BLOBs.

Use this script to check that items are still in the content database, and therefore not in scope for the UBC job.

*SQL

SELECT AD.Id,DS.Content BlobRef, DS.Size,AD.TimeCreated,AD.Extension,DS.RbsId,AD.Level,AD.WebId,AD.ListId FROM DocStreams DS with(NOLOCK)

INNER JOIN DocsToStreams DTS with (NOLOCK) ON DTS.SiteId = DS.SiteId AND DTS.DocId = DS.DocId AND DTS.Partition = DS.Partition AND DTS.BSN = DS.BSN

INNER JOIN AllDocs AD with (NOLOCK) ON DTS.SiteId = AD.SiteId AND DTS.DocId = AD.Id AND DTS.Level = AD.Level

WHERE DTS.HistVersion = 0 AND DS.RbsId IS NOT NULL AND AD.Id IN ('GUID(s)')

In some cases, if the profile is set up to run synchronously, and the UBC job is run before the Recycle Bin Timer Job (web app SharePoint timer job), some blobs may be left behind, but these will be picked up on the next run of the UBC Timer Job. Optionally, the Recycle Bin Timer Job can be run manually before running the UBC Timer Job to alleviate this situation.