Migration Errors

This wiki is still under construction

Infrequent instances of errors may arise throughout the migration process, and these occurrences will be documented in the error log. Within this log, you will find a compilation of such errors, along with detailed explanations regarding their origins and instructions for resolving them.

Errors

Error=Value=CobaltBlockOfLeadingZerosDetected indicates an error resulting from a corrupt file at the source. To resolve this issue, you should take one of the following actions:

Delete the corrupt file at the source.
Replace the corrupt file with a valid one at the source site.
Attempt to recover the corrupted file at the source.
After resolving the source file issue, you can either manually copy the file to the destination or initiate a re-migration process.

Exception from HRESULT: 0x80131904 CallStack -- at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx) may occur due to various internal factors. One possible reason is the presence of duplicate internal Unique IDs. By default, ShareMaster uses the same Unique ID as the source item. If you copy the same items within the same site collection, even if the item was previously deleted and is in the recycling bin, this migration error can happen. To resolve this, you can disable the "Maintain Unique guid" option in the settings to ensure that Unique IDs always remain distinct.

Note: Unique IDs and SharePoint's "Id field" are distinct.

Access Denied If this issue arises while duplicating site pages through the "Files" clone section, it could indicate that "Custom scripts" are disabled. When duplicating entire lists and sites, ShareMaster will automatically activate Custom scripts to migrate site pages. However, when copying specific site pages, you might need to enable this feature manually. You can do so by navigating to Explore Master - Settings - Site Settings - Enable Custom Script / Pages.