For the complete documentation index, see llms.txt. This page is also available as Markdown.

Most common errors

A list of most common errors and how to fix them.

Xopero ONE may report errors when configuring integrations, running backup jobs, or performing recovery operations. Understanding the most common error types and their possible causes can help identify configuration issues, permission problems, connectivity failures, and other conditions that may prevent backup or recovery operations from completing successfully.


Common errors list

Below you can find the most common error codes, along with descriptions and information on how to resolve them.

The list is presented in alphabetical order.

Error message with code
Cause
Resolution

DV0231: Unable to create backup data writer

Insufficient memory to create the backup data writer.

Contact the Xopero support team.

Open a case

Alternatively, you can try splitting your repositories into smaller backup plans or decreasing the number of backups running simultaneously as workarounds.

DV0998: Unhandled exception (Assertion failed SchemeUtil.cs:18)

The personal access token (PAT) (or API token for Atlassian) used for authentication has expired.

Generate a new access token and replace the expired one. Password Manager

DV9021: Repository not found

A repository has been deleted or disabled, but remains a part of your backup scope.

The error will clear automatically after the backup scope is updated during the next organization sync.

To resolve the issue immediately, manually detach the licenses from the affected repositories.

DV9022: Access to repository is forbidden

Insufficient permissions to access the repository.

DV9030: Metadata download failure

Insufficient permissions to download the metadata.

DV9039: Failed to restore repository – push was rejected

The restore operation has failed due to security policies or organization-level restrictions that actively block push operations on the target repository.

DW0834: Your Branch Protection Rules blocked this action. Add your Personal Access Token (PAT) to complete the [process name].

Insufficient permissions to backup/restore the branch protection rules.

DW5001: Repository permissions are insufficient

Insufficient permissions to back up the repository.

DW5083: Git - GitHub App has insufficient rights to get branch protecting rules. Please provide Personal Access token in additional credentials.

Insufficient permissions to backup/restore the branch protection rules.

DW5205: Found [x] corrupted attachments

The backup has failed due to corrupted attachments, orphaned references, items in the trash, or missing permissions.

Last updated

Was this helpful?