Chat now with support
Chat with Support

StoragePoint 6.4 - Known Issues

Known Issues
Introduction Installer May Not Always Rollback on Cancel Installer May Fail if Critical Updates Are Missing Uninstalling other Metalogix Products Applying CU or Updates Large File Support Large File Content Type FIPS Compliance Incorrect Endpoint Size and BLOB Count on Dashboard Using the Previous Version of SharePoint for the Look and Feel SharePoint 2013 Eval Sites Loading Files Outside of the UI Bulk Recall and Unused BLOB Cleanup Selecting Scope for a Profile goes to Central Admin Scheduling the Process Existing Jobs Customized or Unghosted Files Move-SPSite Upgrade Support from Previous Versions of StoragePoint Deprecated Data Types Modern UI for SharePoint 2019/SharePoint SE BLOBS Not Being Removed by UBC Upgrade from 5.9.0.74 to 6.1 is failing with a timeout error When Metadata Change Rule Condition is Content Property=Folder, blobs are not archived Masterkey error after migration (SharePoint 2013/SharePoint 2016) Not all missing blobs are repopulated when the option “Restore Missing blobs” in BLOB Health Analyzer is checked Unused BLOB Cleanup job counts unused BLOBs as backup BLOBs Number of BLOBs to migrate and size of migrated BLOBs are always 0 in BLOB Migrate Analyze and Estimate After completing the StoragePoint upgrade process from 5.x, the old logos are maintained. Analyze and Estimate for BLOB recall/externalize is not accurate if large file(s) exist(s) "TypeLoadException: Could not load file or assembly 'Bluethread.SharePoint.StoragePoint.Utilities" ULS error Free space is marked as N/A for endpoints BLOB Migrate displays free space as 0B There is an error “This page has encountered a critical error. Contact your system administrator if this problem persists.” when cataloging librarian from the Web Application or Content Database
About Us

Loading Files Outside of the UI

Content that is uploaded using PowerShell or some other third party tool will create extra BLOBs in the system cache. If this method is used, running the Unused BLOB cleanup will take care of the extra BLOBs.

Bulk Recall and Unused BLOB Cleanup

After performing a Bulk Recall, it may be necessary to run the Unused BLOB Cleanup job to remove BLOBs from the endpoint. The Bulk Recall no longer removes blobs if they have not passed the BLOB retention period.

Selecting Scope for a Profile goes to Central Admin

The issue occurs when selecting the scope of a profile. The change button is clicked which opens a window to show the SharePoint Farm structure. If a different Web Application is selected in the upper right corner, the new window that opens shows the Central Admin page instead of the list of Web Applications.

The root cause was that the Central Admin session that was opened to access StoragePoint was not using the default internal Alternate Access Mapping.

For example, to access Central Admin someone was using http://servername.fullyqualified:100 and not http://servername:100. The default internal AAM should be used.

Scheduling the Process Existing Jobs

When Archiving, Records or Holds are enabled on a profile, the Process Existing dialog is displayed when saving the profile. This allows those newly created rules to be applied to existing content, and categorically migrate the content to the correct endpoint.

If the job is to be scheduled for a later time (process existing content at a later time, such as when most users are not online) rather than immediately, the date and time pickers are displayed below, and scrolling down may be necessary.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating