Skip to main content

Error codes for Azure SQL

Updated today

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

AZURE_SQL1000

Error Message: Internal Error

Error Description: This is an internal error.

Error Solution: Download job logs and contact Support.

AZURE_SQL1013

Error Message: No available databases eligible for backup

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

  • CDC prechecks failed

  • DDL changes in the databases

  • No table exists in the database

  • Database has tables with no primary or unique key

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 trigger backup.

AZURE_SQL1020

Error Message: Failed to poll status

Error Description: Failed to poll status.

Error Solution: Download job logs and contact Support.

AZURE_SQL1022

Error Message: Failed to execute SQL command

Error Description: Failed to execute SQL command.

Error Solution: Download job logs and contact Support.

AZURE_SQL1041

Error Message: Failed to restore database

Error Description: Failed to restore database.

Error Solution: Download job logs and contact Support.

AZURE_SQL1042

Error Message: No available databases eligible for restore

Error Description: You may get this error if none of the databases is eligible for restore as a database with the same name already exists.

Error Solution: Delete the database or give a new name while restoring.

AZURE_SQL1043

Error Message: Database(s) skipped

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

  • CDC prechecks failed

  • DDL changes in the databases

  • No tables exist in the database

  • Database has tables with no primary or unique key

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 trigger backup.

AZURE_SQL1046

Error Message: Login failed

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

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

AZURE_SQL1047

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.

AZURE_SQL1048

Error Message: Failed to get SQL Server timezone and offset

Error Description: Failed to get SQL Server timezone and offset.

Error Solution: Execute the following T-SQL query and fix any errors encountered:

Use <dbname>
SELECT FORMAT(SYSDATETIMEOFFSET(), 'zzz') AS TimeZoneOffset,
DATEPART(TZOFFSET, SYSDATETIMEOFFSET()) * 60 AS TimeZoneOffsetInSeconds"

AZURE_SQL1049

Error Message: SQL Server Precheck failed

Error Description: You get this error if a SQL Server precheck fails.

Error Solution: Check if the SQL server agent is running. If not, start it.For more information, see Check and validate the required Services.

AZURE_SQL1050

Error Message: Failed to initialize job

Error Description: You get this error if initiating a backup or restore job fails.

Error Solution: Download job logs and contact support.

AZURE_SQL1051

Error Message: Post-processing of backup job failed.

Error Description: You get this error if the post-processing of a backup job fails.

Error Solution: Download job logs and contact support.

AZURE_SQL1052

Error Message: Failed to backup database(s).

Error Description: You get this error if the database backup job fails.

Error Solution: Download job logs and contact support.

Did this answer your question?