Skip to main content
Druva Documentation

SQL errors

This topic lists the SQL errors that you may encounter while working with Phoenix. 

SQL1

Error Message: The SQL agent encountered an internal error 

Error Solution: Contact Druva Support.

SQL3

Error Message: Metadata mismatched from the last backup.  The SQL Server instance was probably not backed up in the previous backup cycle.

Error Description: This error can occur if the metadata of the database selected for backup does not match with the database metadata when it was backed up earlier. 

Error Solution: Run a full backup through the Phoenix Management Console.

SQL4

Error Message: Specified instance not found on present application server.:[Attempting to restore to instance <logical path of instance> not found in server]

Error Description: This error can occur if the specified instance is not present on the target machine.

Error Solution:  To resolve the error:

  • Restore the database file to an alternate location. These files can be used to restore databases by attaching it to the other SQL instance.
  • Ensure that the instance is running on the target machine.

SQL5

Error Message:  Failed to get the SQL product version

Error Description:  This error can occur because of one of the following reasons:

  • sqlcmd is not configured.
  • There is an error with sqlcmd.

Error Solution:   To resolve this error:

  • On the command prompt, type "sqlcmd" to check if sqlcmd is configured.
  • Retry the operation.

Note: This error is applicable for SQL agent versions 4.6.5 and earlier. 

SQL6

Error Message:  Phoenix SQL agent found no instance/database on the server to backup or the SQL service is not running or the backup policy is set to exclude all the databases.

Error Description:  This error can occur because of one of the following reasons:

  • Log chain is broken for selected databases.
  • All databases in simple recovery mode for log backup.
  • All databases excluded from UI.

Error Solution:   To resolve this error:

  • Ensure at least one instance is online and in the working state.
  • Check backup policy and the excluded folder entries.
  • Trigger a full/differential backup.
  • Disable third-party backup tool.
  • At least one database should have FULL recovery mode.
  • Update excluded databases list.

SQL7

Error Message:  Phoenix agent encountered ODBC driver error

Error Description:   This error can occur because of one of the following reasons:

  • Connection with SQL server lost.
  • Meta information for database not available.
  • Not enough permission to access SQL server.

Error Solution:   To resolve this error:

  • Check if SQL server instance is up and running.
  • Permissions for local system account enabled as per documentation.

SQL8

Error Message:  Phoenix agent encountered VIDLIB application error

Error Description: This error can occur because of one of the following reasons:

  • Local network connection disabled
  • Unable to create virtual connection with SQL server
  • Not enough permissions to access SQL server
  • The point-in-time or transaction mark restore of the database fails when log chain for database breaks due to changed/replaced data files.

Error Solution:  This error can be resolved in the following ways:

  • It can be a transient issue and might be auto-resolved in the next log backup cycle.
  • Check the permissions for local system account enabled as per documentation.

SQL9

Error Message:  SQL Agent internal error occurred

Error Solution:   Contact Druva Support.

SQL10

Error Message:  Marked transaction timestamp not found. Insufficient transaction logs to restore marked transaction.

Error Description:  This error can occur due to:

  • Broken transaction log chain
  • Timestamp issues

Error Solution: Contact Druva Support.

SQL11

Error Message:  Invalid time-stamp for point-in-time restore

Error Description:  This error can occur due to:

  • Broken transaction log chain
  • Timestamp issues

Error Solution:   Contact Druva Support.

SQL12

Error Message:  Database is not compatible on a for target SQL server. Please check version compatibility level. 

Error Description:   This error can occur because of:

  • SQL Server restore instance is incompatible.

Error Solution:  To resolve this issue:

  • Try to restore your database on a compatible SQL server instance.

                                                      See ALTER DATABASE Compatibility level

Note: This issue is not applicable on SQL server agent 4.6.5 and earlier. 

SQL15

Error Message: SQL agent encountered an internal error

Error Solution: Contact Druva Support.

SQL16

Error Message: SQL Server backup node not healthy.

Error Description: This error occurs when the availability group node is not connected or not in the healthy state.

Error Solution: To resolve this issue, check the status of the cluster and availability group and identify whether there are nodes available based on the backup preference.

SQL17

Error Message: SQL server discovery on the client failed

Error Description: This error occurs when Phoenix does not discover MS-SQL resources, such as instances and AGs.

Error Solution: To resolve this issue, check the Phoenix client log file for errors. Contact Druva Support.

SQL18

Error Message: Different client versions for AG nodes.

Error Description: This error occurs when the different Phoenix client versions are installed on the availability group nodes.

Error Solution: To resolve this issue, ensure that you install the same version of the Phoenix agent on all the availability group nodes.

SQL20

Error Message: Failed to trigger backup request due to unavailability of SQL node.

Error Description: This error occurs due to a failure of the Phoenix agent to trigger backup request caused by unavailability of a SQL node. Check the connection status of the SQL node.

Error Solution: To resolve this issue, check the status of the cluster and availability group and identify whether there are nodes available based on the backup preference.

SQL21

Error Message: Incorrect CLI parameter for schedule passed for triggering the backup job

Error Description: This error can occur if no backup schedule is found for a CLI-triggered backup job.

Error Solution: Cross-check the backup policy schedule parameter while triggering the SQL backup through CLI.

SQL22

Error Message: Incorrect CLI parameter for SQL resource passed for triggering the backup job

Error Description: This error can occur if you provide an invalid name for an instance or availability group for a CLI-triggered backup job.

Error Solution: Cross-check the resource parameter while triggering the SQL backup through CLI.

 

SQL23

Error Message: Incorrect CLI parameter for backup set or policy passed for triggering the backup job

Error Description: This error can occur for a CLI-triggered backup job, because of the following reasons:

  • A backup set is not configured
  • A backup set is disabled
  • A backup type is not configured in the backup set.

Error Solution: Cross-check the backup set parameter while triggering the SQL backup through CLI.

SQL24

Error Message: Backup job can't be triggered because 2 or more backup jobs are running. 

Error Description: This error can occur, if two or more CLI-triggered backup jobs are already running.

Error Solution:  To resolve this issue, wait until there are less than two CLI-triggered backup jobs running.

SQL25

Error Message: Triggered backup job for log backup is not created. 

Error Description: This error can occur if no full backup exists, or another full or differential backup is ongoing for the CLI-triggered backup job.

Error Solution:  To resolve this issue, ensure that you perform a full backup and then retry when no full or differential backup is ongoing.

SQL32

Error Message: No new backup job can be created until the first full backup is completed.   

Error Description: This error can occur if backup jobs are triggered from the command line before the first, full backup completes.

Error Solution:  To resolve this issue, ensure that you wait until the first, full backup completes.

SQL33

Error Message: Database not found during upload.

Error Description: This error can occur if the database on an instance is deleted during backup.

Error Solution: To resolve this issue, ensure that the database on the instance is not deleted during the backup operation.

SQL34

Error Message: Failed to get product version info for instance [instance_name]

Error Description: This error occurs when the Phoenix agent cannot identify the SQL Server version.  One of the reasons why the Phoenix agent cannot identify the SQL Server version is if TLS 1.0/1.1 is disabled.

Error Solution: If TLS 1.0/1.1 is disabled, install the SQL Server Native Client driver 11.0. You can download the SQL Server Native Client driver for the MS-SQL Server 2012 from the Microsoft Download Center. If the problem persists, contact Druva support.

SQL35

Error Message: Database state error. 

Error Description: This error can occur for the replace original database restore job if:

  • The database does not exist on the selected SQL Server instance
  • The database selected for replacement is running on a SQL Server instance that is a part of an Availability Group
  • The selected SQL Server instance is in No recovery mode

Error Solution: To resolve this issue, ensure that:

  • The database exists on the selected SQL Server instance
  • The SQL Server instance is not a part of an Availability Group
  • The SQL Server instance is not in the No-Recovery mode

SQL36 

Error Message: Failed to detach database.

Error Description: This error can occur if Phoenix cannot detach the database from its SQL Server instance during restore.

Error Solution: To resolve this issue, check:

  • If the database exists on the SQL Server instance
  • If any issue on the SQL Server instance is stopping the database from getting detached