❗ Important

This feature has limited availability. To know more about limited availability and sign up for this feature, contact your Account Manager.

This topic lists the errors that you may encounter during backup and restore of Azure SQL resources.

Error Message: Internal Error

Error Description: This is an internal error.

Error Solution: Contact Support.

Error Message: Unknown Error

Error Description: Unknown Error.

Error Solution: Contact Support.

Error Message: Unsupported Operation

Error Description: Unsupported Operation.

Error Solution: Contact Support.

Error Message: Invalid Argument

Error Description: Invalid Argument.

Error Solution: Contact Support.

Error Message: Context Canceled

Error Description: Context Canceled.

Error Solution: Contact Support.

Error Message: Failed to validate job

Error Description: Failed to validate job.

Error Solution: Contact Support.

Error Message: Failed to get job config

Error Description: Failed to get job config.

Error Solution: Contact Support.

Error Message: Failed to get credentials

Error Description: Failed to get credentials.

Error Solution: Contact Support.

Error Message: Failed to create DT session

Error Description: Failed to create DT session.

Error Solution: Contact Support.

Error Message: Failed to initialize Azure FS

Error Description: Failed to initialize Azure FS.

Error Solution: Contact Support.

Error Message: Failed to initialize shuttle

Error Description: Failed to initialize shuttle.

Error Solution: Contact Support.

Error Message: Failed to get metadata

Error Description: Failed to get metadata.

Error Solution: Contact Support.

Error Message: Failed to validate metadata

Error Description: Failed to validate metadata.

Error Solution: Contact Support.

Error Message: No available databases eligible for backup

Error Description: This error might occur due to various reasons such as:

See the logs for exact cause.

Error Solution: Depending on the cause, fix the issue and retrigger backup. For example, if the backup fails cause there’s no data available, make sure data exists in the database and then take trigger backup.

Error Message: Failed to start schema dump

Error Description: Failed to start schema dump.

Error Solution: Contact Support.

Error Message: Failed to process schema dump

Error Description: Failed to process schema dump.

Error Solution: Contact Support.

Error Message: Failed to init fsets

Error Description: Failed to init fsets.

Error Solution: Contact Support.

Error Message: Failed to put metadata

Error Description: Failed to put metadata.

Error Solution: Contact Support.

Error Message: Failed to set snapshot attributes

Error Description: Failed to set snapshot attributes.

Error Solution: Contact Support.

Error Message: Failed to commit snapshot

Error Description: Failed to commit snapshot.

Error Solution: Contact Support.

Error Message: Failed to poll status

Error Description: Failed to poll status.

Error Solution: Contact Support.

Error Message: Failed to start fset backup

Error Description: Failed to start fset backup.

Error Solution: Contact Support.

Error Message: Failed to execute SQL command

Error Description: Failed to execute SQL command.

Error Solution: Contact Support.

Error Message: Failed operation on metadata

Error Description: Failed operation on metadata.

Error Solution: Contact Support.

Error Message: Failed to start upload

Error Description: Failed to start upload.

Error Solution: Contact Support.

Error Message: Failed to start table dump

Error Description: Failed to start table dump.

Error Solution: Contact Support.

Error Message: Failed to start CDC dump

Error Description: Failed to start CDC dump.

Error Solution: Contact Support.

Error Message: Failed to create Azure credentials

Error Description: Failed to create Azure credentials.

Error Solution: Contact Support.

Error Message: Failed to initialize Azure SDKs

Error Description: Failed to initialize Azure SDKs.

Error Solution: Contact Support.

Error Message: Failed to convert backup to full

Error Description: Failed to convert backup to full.

Error Solution: Contact Support.

Error Message: Failed to get hash key

Error Description: Failed to get hash key.

Error Solution: Contact Support.

Error Message: Failed to start schema restore

Error Description: Failed to start schema restore.

Error Solution: Contact Support.

Error Message: Failed to start table restore

Error Description: Failed to start table restore.

Error Solution: Contact Support.

Error Message: Failed to create restore view

Error Description: Failed to create restore view.

Error Solution: Contact Support.

Error Message: Failed to set restore view

Error Description: Failed to set restore view.

Error Solution: Contact Support.

Error Message: Failed to create write IO handler

Error Description: Failed to create write IO handler.

Error Solution: Contact Support.

Error Message: Failed to initialize IO Server

Error Description: Failed to initialize IO Server.

Error Solution: Contact Support.

Error Message: Failed to spawn IO Server

Error Description: Failed to spawn IO Server.

Error Solution: Contact Support.

Error Message: Failed to download data

Error Description: Failed to download data.

Error Solution: Contact Support.

Error Message: Failed to preprocess CDC data

Error Description: Failed to preprocess CDC data.

Error Solution: Contact Support.

Error Message: Failed to replay CDC data

Error Description: Failed to replay CDC data.

Error Solution: Contact Support.

Error Message: Failed to restore database

Error Description: Failed to restore database.

Error Solution: Contact Support.

Error Message: No available databases eligible for restore

Error Description: You may get this error if you do not select a database for restore.

Error Solution: Select a database and trigger restore.

Error Message: Database(s) skipped

Error Description: Some databases might be skipped from backup due to reasons such as:

See the logs for exact cause.

Error Solution: Depending on the cause, fix the issue and retrigger backup. For example, if the database was skipped because there’s no data available, make sure data exists in the database and then take trigger backup.

Error Message: Failed to check cdc status

Error Description: Failed to check cdc status.

Error Solution: Contact Support.

Error Message: Invalid Job ID

Error Description: You may get this error if another job is running in parallel.

Error Solution: No action needed.

Error Message: Login failed

Error Description: You may get this error if server authentication fails.

Error Solution: Check the authentication type and correct correct authentication.

Error Message: Failed to start CDC capture job

Error Description: You may get this error if there are reused database IDs that lead to stale data in the capture job details.

Error Solution: Disable and enable CDC and try again.