Job Log Errors

When viewing the Job Log report, items with error activity will identify the error category and list a more detailed error message about the error that occurred during the transfer. Learn more about errors and possible causes below.

 

Category

Error Description(s)

Remediation Suggestions

Category

Error Description(s)

Remediation Suggestions

Item Not Found

  • The item could not be located within the storage platform

  • The item could not be located within the storage platform due to an invalid path

  • The item could not be located within the storage platform, a Forbidden status code was returned

  • The item could not be located within the storage platform, a Gone status code was returned

  • The item could not be located within the storage platform, a NotFound status code was returned

  • The item could not be located within the storage platform, an InternalServerError status code was returned

  • The item could not be located within the storage platform, an Unauthorized status code was returned

  • The item could not be located within the storage platform, it may have been deleted

  • The item has a platform ID that is invalid

  • The item or associated account could not be located within the storage platform

  • The item or associated version could not be located within the storage platform

  • The item type was unexpected within the storage platform

  • The item's parent is invalid

Metadata Import
If a metadata import file is being used, verify the formatting.

  • Special characters may need to be properly escaped.

  • Additional formatting may depend on the file type. For example, a CSV metadata import file will need to have empty values represented as "" instead of just being blank.

Impersonation
If you are using impersonation, verify that each account has adequate permissions for migration operations. To troubleshoot, create separate connections for each user instead of using impersonation.

Connection Pooling
If the connection is using connection pooling, verify that each account has adequate permissions for migration operations. To troubleshoot, use a single account instead of connection pooling.

User Mapping
If user mapping was used for the job, verify that all mappings are resolved. To troubleshoot automatic mapping, try a different matching rule type; further troubleshooting may require the use of a manually-created user map.

 

DryvIQ Migrate Version: 5.9.2
Release Date: December 17, 2024