Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

NOTICE! We are upgrading our support telephone services, implementing Genesys, starting the week of May 19, 2025

StoragePoint 6.3 - 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 Metalogix Archive Adapter 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

About Us

Contacting Quest Technical Support Resources

Using a semi-colon when providing a password for SQL server authentication results in failed login error

When a user uses SQL Server authentication for the "Access Credentials and Database Creation Login Credentials wizards during configuration and provides a password that uses a semi-colon at the end, clicking the Test Connection button to validate the account results in StoragePoint raising an error, stating An error occurred: Login failed for user sqluser.

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

StoragePoint 6.3 - Known Issues

Using a semi-colon when providing a password for SQL server authentication results in failed login error