An application error log is written to '%LocalAppData%\MacroView\MigrationTool\Logs'. The Migration.log file contains details of any application-level exceptions that occur outside of a migration operation.
Important: After running a migration package, refer to the package logs for any errors that occur when processing items or provisioning objects in SharePoint.
Common Migration Log Messages
|Workflow did not assign a ProvisionObject for the SourceItem||The item was not migrated because the workflow logic did not specify a 'Provision' activity for the SourceItem.|
|Parent ObjectType is Unknown||The item was not migrated because there was no parent available. This condition can be expected when the parent item was not migrated because the 'Workflow did not assign a ProvisionObject for the SourceItem'. It can also occur when an unexpected SharePoint error prevented the parent from being migrated.|
|Adding a [X] to [Y] is unsupported||The item was not migrated because the workflow logic specified a 'Provision' activity that was not valid for the parent (e.g. Adding a [File] to [Web] is unsupported).|
|Unable to load content type 'Email'||The ProvisionFile workflow activity was assigned the 'Email' content type but it was not found in the destination. This can occur when using a 'Basic Package' template because the workflow will attempt to assign an email content type by default, so that email metadata attributes can be automatically captured. Ensure an 'Email' content type is present in the destination library or update the workflow to specify a different content type.|
|One or more errors occurred||An exception occurred and the item was not migrated. See Exception column for further details.|
|Network problems are preventing connection to Microsoft Exchange||Outlook lost connection with the Exchange server and the item could not be retrieved so it was not migrated. This can occur when the user is throttled by an Exchange policy. See User workload management in Exchange Server for information on how to apply a less restrictive policy to the migration user.|
Common Migration Log Exceptions
|Microsoft.SharePoint.Client.ServerException: File Not Found||Unable to open the requested path. Often caused by an incorrectly formatted destination path in the migration package. Verify that the destination path is not encoded (e.g. spaces should not be specified as %20).|
|Microsoft.SharePoint.Client.ServerException: Invalid text value||A single line of text field has an invalid value. This can occur if the field is not set to 'Allow unlimited length in document libraries' and the value exceeds 255 characters. Email 'To' and 'Cc' properties are often longer than 255 characters.|
|Microsoft.SharePoint.Client.ServerException: Invalid data has been used to update the list item. The field you are trying to update may be read only.||An ItemProperty value's type is not valid for the specified field. When adding items to the ProvisionFile, ProvisionFolder or ProvisionDocumentSet 'Properties' collection ensure the ItemProperty.Value object type is valid for the specified field name.|
|System.Runtime.InteropServices.COMException (0x80090020): Your Digital ID name cannot be found by the underlying security system||An S/MIME encrypted email couldn't be opened because a required certificate was not available in Outlook. When migrating older emails you must still have the corresponding certificates present, even if they are no longer valid. See S/MIME for message signing and encryption for further details.|
|System.Net.WebException: The remote server returned an error: (429)||SharePoint Online throttled the request to protect the reliability and availability of the service. You should run your migrations during evening and weekend hours for the region. See General migration performance guidance for more information.|