Error code reference - SQL Backup

Warning code

Description

110

Failed to save primary log file: <value>

The primary log file records details of backup and restore operations.

Check that the startup account for the SQL Backup Agent service has rights to create files in the reported directory. Also check that the directory has sufficient free space. By default, the log files will be stored in %ALLUSERSPROFILE%\Application Data\Red Gate\SQL Backup\Log\ on the machine on which the SQL Backup server components are installed.

You can change the location of the log file using the file management options.

115

LOGTO error: Failed to save log file: <value>

This log file, specified by the LOGTO option, records details of backup and restore operations.

Check that the startup account for the SQL Backup Agent service has rights to create files in the listed directory. Also check that the directory has sufficient free space.

120

LOGTO error: Folder does not exist: <value>

The LOGTO option specifies a log file for recording details of backup and restore operations. SQL Backup couldn't create the directory for this log file.

Check that the startup account for the SQL Backup Agent service has rights to create the directory.

121

LOGTO error: Default log file folder does not exist: <value>. Log file will be saved in folder: <value>.

The LOGTO option specifies a log file for recording details of backup and restore operations. SQL Backup couldn't create the log file in the default directory, but has successfully created the log file in the reported directory.

Check that the startup account for the SQL Backup Agent service has rights to create files in the default directory.

130

MOVETO error: Failed to move file: <value>

SQL Backup failed to move a file to the specified directory. Check the error message for the cause of the failure.

In most cases, this problem occurs when the startup account for the SQL Backup Agent service does not have appropriate rights. The startup account must be able to write to the specified directory, and delete the source file.

If this error arises during log shipping, it is often because the MOVETO parameter is not moving files out of the network share. Edit the Log Restore job so that the restored log files are moved to a different folder. You will need to do this via a SQL application such as SSMS. See Configuring log shipping for more information.

131

MOVETO error: Failed to execute MOVETO command.

SQL Backup failed to move the file as specified by the MOVETO command. Check the error message for the cause of the failure.

132

MOVETO error: Folder does not exist: <value>

SQL Backup failed to move the file as specified by the MOVETO command, because the specified directory does not exist.

133

MOVETO error: Folder does not exist: <value>

140

COPYTO error: Destination file already exists. Will not overwrite: <value>

SQL Backup failed to copy the file to the directory specified by the COPYTO command. The file already exists in this directory.

To force the file to be overwritten, specify a FILEOPTIONS parameter that includes the bit-masked value "4".

141

COPYTO error: Unable to copy <source> to <target>

SQL Backup failed to copy the file to the target directory specified by the COPYTO command.

In most cases, this problem occurs when the startup account for the SQL Backup Agent service does not have appropriate rights. The startup account must be able to write to the target directory.

142

COPYTO error: Unable to copy <source> to <target>. Error message: <value>

SQL Backup failed to copy the file to the target directory specified by the COPYTO command. Check the error message for the cause of the failure.

143

COPYTO error: Failed to copy file: <value>

SQL Backup could not process the files to be copied. Check the error message for the cause of the failure.

145

COPYTO error: Failed to create folder: <value>

146

COPYTO error: Source file does not exist: <value>

147

COPYTO made multiple attempts to copy the file: <value>

SQL Backup made multiple attempts to copy the file specified by the COPYTO command.

The error message shows the number of copy attempts, and the reason why each copy attempt failed.

148

COPYTO error: failed to delete temporary file: <value>

149

COPYTO error: failed to rename temp file <source> to <target>

150

MAILTO error: SMTP host name not defined.

SQL Backup could not send an email notification because the SMTP host name was not defined.

To specify an SMTP host name for this SQL Server instance, use the SQL Backup GUI (Tools > Server Options > Email Settings).

151

MAILTO error: Failed to send mail.

SQL Backup failed to send an email notification. Check the error message for the cause of the failure.

160

ERASEFILES error: Failed to delete file: <value>

SQL Backup could not delete the file that was marked for deletion.

161

ERASEFILES error: Failed to delete file: <value>. Error code: <value>

SQL Backup could not delete the file that was marked for deletion. Check the error message for the cause of the failure.

162

Failed to delete log file: <value>. Error code: <value>

The log file records details of backup and restore operations.

SQL Backup could not delete the log file that was marked for deletion. Check the error message for the cause of the failure.

164

Failed to delete backup entries in msdb tables: <value>

SQL Backup could not delete old backup and restore records from the msdb history tables. Check the error message for the cause of the failure.

166

Failed to delete old entries in local history tables: <value>

SQL Backup could not delete backup and restore records from the local SQL Server Compact database. Check the error message for the cause of the failure.

167

Failed to get database size from server.

While calculating the compression ratio for a database, SQL Backup could not retrieve the current database size from SQL Server. Check the error message for the cause of the failure.

168

Failed to identify filestream files.

While calculating the current database size, SQL Backup could not retrieve the details of files used to store filestream data. Check the error message for the cause of the failure.

170

Validation error when processing the list of transaction log backups.

SQL Backup could not process the list of transaction log backups required to restore a database. Check the error message for further details.

If the error message reports that the log files are not in sequence, this may be because the Log Sequence Numbers cannot be read or are missing from the header file. You can manually restore the log files, specifying WITH NORECOVERY or WITH STANDBY, using the extended stored procedure. See Using the extended store procedure and The RESTORE command for more information.

In a log shipping scenario, this error may be due to a large log backup taking a long time to copy to the network share, allowing later (smaller) log files to be copied to the network share before it, and a restore of these attempted. This problem should sort itself out over time. You can avoid the problem by increasing the log restore job interval so that it is at least the transfer time of the largest backup.

175

Another process might be locking this file: <value> (attempt <value>) (<value>)

This is an informational message. The backup file was locked, preventing SQL Backup from updating the file at the first attempt. SQL Backup succeeded in updating the file after further attempts.

Other applications may be accessing backup files. This may cause errors in the future if those applications maintain locks on the backup files.

195

Failed to update backup history table (BACKUPMEDIAFAMILY).

SQL Backup could not update details of the backup process in the BACKUPMEDIAFAMILY table in the msdb database. Check the error message for the cause of the failure.

200

Error creating backup file: <value>

SQL Backup could not create the backup file. Check the error message for the cause of the failure.

202

Multiple attempts were made to create the backup file.

This is an informational message. SQL Backup could not create the backup file at the first attempt, but succeeded after further attempts.

This indicates potential problems with storing backup files at the specified locations.

204

Multiple attempts were made to restore from the backup file.

210

Error writing to backup file: <value>

This is an informational message. SQL Backup could not write backup data to disk at the first attempt, but succeeded after further attempts.

This indicates potential problems with storing backup files at the specified locations.

213

Error setting file pointer position: <value>

This is an informational message. SQL Backup could not continue to write backup data to disk following a previous failure, but succeeded after further attempts.

This indicates potential problems with storing backup files at the specified locations.

215

Error flushing buffer contents to file: <value>

218

Insufficient disk space <value>: required <value>; available <value>

There was insufficient disk space to create the backup file. Before attempting the backup process again, create more free space on the disk, or back up to a different location.

220

No log files found to be restored.

SQL Backup could not find any relevant transaction log files to restore from the locations you specified.

Check that you have specified the files correctly (including any wild cards in file names).

Also check that the startup account for the SQL Backup Agent service has permission to read the transaction log files.

225

Files missing from backup history.

One or more of the backup files required for the restore process is missing. Check the error message for details of the missing files.

226

Files missing from search folder.

One or more of the backup files required for the restore process is missing. Check the error message for details of the missing files.

280

Failed to open file.

300

Backup failed. Retry attempt: <value>

This is an informational message. SQL Backup could not back up the database at the first attempt, but succeeded after further attempts.

Check the error message for information about why each attempt failed.

320

Validation failed.

330

Your license does not allow email notification to be performed.

The MAILTO, MAILTO_ONERROR, or MAILTO_ONERRORONLY keyword was specified, but has been ignored due to licensing restrictions.

SQL Backup failed to send an email notification because you are using SQL Backup Lite edition, or a read-only licensed edition of SQL Backup. To send email notifications, you must use the Pro edition of SQL Backup.

Note that from version 6.5, SQL Backup is only available in the Pro edition. SQL Backup Lite has been retired.

If you are currently using SQL Backup Lite and have not yet been contacted by Red Gate about a free upgrade, please go to the SQL Backup product page and download it from there. You can use your existing serial key to license the Pro version.

400

Failed to initialize local data store: <value>

SQL Backup could not initialize the SQL Server Compact database it uses to store details of backup and restore processes. The SQL Server Compact database is created when the SQL Backup server components are installed and is used to improve the performance of the GUI.

Check the error message for the cause of the failure.

If the error message reports that access to the database file is not allowed, you need to ensure that the SQL Backup Agent Service startup account has permissions

402

Failed to open local data store: <value>

SQL Backup could not connect to the SQL Server Compact database it uses to store details of backup and restore processes.

Check the error message for the cause of the failure.

405

Failed to acquire handle for local data store lock (<value>): <value>

410

Failed to start transaction on local data store: <value>

425

Folder does not exist: <folder name>.

Check that all the log file locations you have specified for your log shipping restore job are available.

If necessary, create the missing directories, or alter your log shipping restore job so that it refers to the correct directories.

Also, check that the startup account for the SQL Backup Agent service has permission to read the directories.

435

Get exclusive local data store access failed - timeout.

SQL Backup could not acquire a lock on the SQL Server Compact database it uses to store details of backup and restore processes. Another process was accessing the database for more than 15 seconds.

The SQL Server Compact database may be too large. Review your backup history deletion policy (Tools > Server Options > File Management > SQL Server backup history) and consider reducing the amount of backup history you retain.

436

Get exclusive local data store access failed - abandoned.

SQL Backup could not acquire a lock on the SQL Server Compact database it uses to store details of backup and restore processes. This was due to a termination request.

This usually happens because the SQL Backup Agent service is in the process of shutting down.

438

Get exclusive local data store access failed - invalid lock handle.

SQL Backup could not acquire a lock on the SQL Server Compact database it uses to store details of backup and restore processes. This was probably caused by an internal error.

Try restarting the SQL Backup Agent service.

440

Invalid DB handle.

SQL Backup could not write data to the SQL Server Compact database it uses to store details of backup and restore processes. The database was not available.

Try restarting the SQL Backup Agent service.

442

Get exclusive local data store access failed - invalid lock handle.

SQL Backup could not release a lock on the SQL Server Compact database it uses to store details of backup and restore processes. This was probably caused by an internal error.

Try restarting the SQL Backup Agent service.

445

Local data store error: <value>

SQL Backup could not write data to the SQL Server Compact database it uses to store details of backup and restore processes.

Check the error message for the cause of the failure.

450

Local data store SQL error: <value>

SQL Backup could not write data to the SQL Server Compact database it uses to store details of backup and restore processes. There was an error preparing the SQL command used to write the data.

Check the error message for the cause of the failure.

460

Encryption key size is specified, but password is empty.

The KEYSIZE keyword has been specified, but the PASSWORD keyword has not been specified, or it is specified with a zero-length password.

462

Short passwords may not be secure.

The KEYSIZE keyword has been specified, but the supplied PASSWORD is seven characters or fewer.

470

Transaction log has already been restored.

This is an informational message. One or more transaction log backup files has already been restored, and will not be restored again.

This may indicate that the MOVETO option is not moving restored transaction log files to the specified directory.

Alternatively, another process may be copying old transaction log backup files to the directory SQL Backup is using for newly created transaction log backup files.

471

Failed to run sp_change_users_login report while checking for orphaned users.

You used the ORPHAN_CHECK option, but SQL Backup could not run the sp_change_users_login stored procedure.

Check the error message for the cause of the failure.

472

Orphaned users have been detected during a RESTORE operation. Check the log file for the list of orphaned users and associated SIDs.

474

A full database backup was performed for the database <database name>.

This warning arises if WITH FULLIFREQUIRED is included in the BACKUP DATABASES or BACKUP LOGS command and a full backup is taken. For more information, see The BACKUP command.

480

Failed to create output folder: <value>

481

The file name (<file name>) contains an invalid character (<invalid character>).

This warning arises if the <DATABASE> tag is used, either directly or via the <AUTO> tag, to generate a backup file name from the database name, and the database name includes an invalid character. If no backups are created, error code 505 is also returned.

For information on using tags to generate file names, see File location tags. For information on the <AUTO> tag see File management options.

483

The FULLIFREQUIRED option is not available when taking differential|transaction log backups on SQL Server 2005|2000. SQL Backup was unable to create any full database backups that may be required to restore a differential|transaction log backup.

This warning arises when using WITH FULLIFREQUIRED to:
- take differential backups on SQL Server 2005, or

- take transaction log backups on SQL Server 2000 or 2005

and SQL Server has not returned SQL error 3035 or 4214 (current database backup does not exist).

In these cases, SQL Backup is unable to identify whether any full database backups should be taken before taking differential or transaction log backups. The differential or transaction log backups are created, but may not be usable.

For more information about the FULLIFREQUIRED option, see The BACKUP command.

485

File does not exist: <Filename .sqb>

This warning may arise during a restore operation. The Restore process will perform a check on the file to enure it is accessible before the restore begins. If there is a temporary network interruption or a delay in the initial response being received, this warning will occur, but the second attempt to check the file will succeed. The warning can be ignored in these circumstances.

Error code

Description

500

General SQL Backup error.

505

No valid SQL Backup file name entered.

Check that the length of the path name does not exceed the number of characters for your operating system.

If you are generating a backup file name using the <DATABASE> or <AUTO> tags, check that the database name does not contain invalid characters. See File location tags for more information.

If you are backing up directly to a network share (not recommended), ensure the network share already exists, and that the startup user for the SQL Backup Agent Service has full permissions for the network share (see Backing up and restoring on a network share).
To check the SQL Backup Agent Service permissions, run the following command:

execute master..sqbutility 999, 'RWE', '\\testsrv\backup'

If the agent has read (R), write (W), and execute (E) permissions, the command returns 1; 0 indicates failure.

506

No valid backup sets found from backup history.

507

No valid backup sets found from provided folder(s).

508

No valid full backup sets found from provided folder(s) for latest differential backup.

510

Backup file exists. Will not overwrite. File name: <value>

Try specifying a file name format that does not result in identical file names. See File location tags and The BACKUP command.

To overwrite existing backup files, use the INIT argument.

512

Backup file name (<value>) contains an invalid character (<value>)

515

Multi database backup file names must contain the <AUTO>, <DATABASE> or <DATETIME> tags.

If you are backing up multiple databases, the backup file names must be unique. Use the <AUTO>, <DATABASE>, or <DATETIME> tags to achieve this. See File location tags and The BACKUP command.

516

Multi database operations cannot use MIRRORFILE option.

If you are backing up multiple databases, you cannot use the MIRRORFILE argument. See The BACKUP command.

517

Cannot use MAXDATABLOCK parameter with local files.

518

File name exceeds limit of 259 characters: <value>

519

Multi-database undo file names must contain the <DATABASE> tag.

If you are backing up logs for multiple databases and have specified the STANDBY keyword, the undo file names must be unique. You must use the <DATABASE> tag to do this. You can use other tags too, but the <DATABASE> tag must be present.
See The BACKUP command and Syntax examples.

520

Output file exists. Will not overwrite. File name: <value>

When you use the CONVERT command, you must specify a unique file name for the destination file.

525

Folder does not exist. Folder name: <value>

526

Cannot find saved setting.

Check that the SQL Backup Agent Service startup user has read access to the following registry key and its values: HKEY_LOCAL_MACHINE\Software\Red Gate\SQL Backup\BackupSettings

527

None of the specified folders exist.

Check the transaction log folder locations you have specified for this log shipping restore job.

530

Non-existent backup file.

Check the path of the backup file.

If you are restoring from a backup file on a network share, ensure the startup user for the SQL Backup Agent Service has permissions for the network share.

540

No file name entered for the Microsoft Tape Format (MTF) file.

When you use the CONVERT command, you must specify the path for the SQL Backup files (.sqb) and the path for the MTF file. See The CONVERT command and Syntax examples.

550

Cannot have the same file names for the SQL Backup file and the converted file.

560

File does not exist: <value>

Check the path of the backup file in the RESTORE SQBHEADERONLY command.

If the backup file is on a network share, ensure the startup user for the SQL Backup Agent Service has permissions for the network share.

562

Object is a folder, not a file: <value>

564

Error reading file.

566

Error reading files not in SQB path.

570

File is not a SQL Backup file.

Check the file you are restoring from is not a log file or native backup file.

580

Failed to open file. Message: <value>

The file may be in use or there may be a permissions problem; ensure the startup user for the SQL Backup Agent Service application has been granted the necessary permissions. See Security Model.

581

Failed to disconnect existing connections to database.

584

System databases must be restored with full recovery using the RECOVERY option.

585

Cannot use multiple file names with the THREADCOUNT option.

586

Failed to connect to SQL Server instance: <value>

587

Backup and restore operations are not allowed on database tempdb.

588

You can only perform a full backup of the master database.
Use BACKUP DATABASE to back up the entire master database.

589

Cannot back up the log of the master database.
Use BACKUP DATABASE to back up the entire master database.

590

Insufficient space to perform process. Space required: <value>

591

Cannot disconnect existing users from the model database.

592

The REPLACE option must be used when using the DISCONNECT_EXISTING option on an active database.

595

Failed to create MTF file: <value>

Ensure the startup user for the SQL Backup Agent Service application has been granted the necessary permissions. See Security Model.

596

File is a native SQL Server backup file.

597

Failed to read MTF header data.

600

Multiple log file validation error for restore.

605

Error creating backup file(s). No files could be created.

Ensure the startup user for the SQL Backup Agent Service application has been granted the necessary permissions. See Security Model.

610

Error creating file handle for file: <value>

Ensure the startup user for the SQL Backup Agent Service application has been granted the necessary permissions. See Security Model.

612

Error reading file: unexpected end-of-file reached.

613

Compressed data block not found in file.

620

Error writing to backup file(s).

621

Error writing to backup file(s) due to insufficient disk space.

622

Error flushing contents of backup file(s).

623

Error setting file pointer position for backup file(s).

624

Error writing header (LSN data) to backup file (<value>): <value>.

625

Error writing header (backup size) to backup file (<value>): <value>.

627

Failed to set file pointer to beginning of file (<value>) to write backup size: <value>.

628

Failed to set file pointer to beginning of file (<value>) to read header data: <value>.

629

Failed to set file pointer to beginning of file (<value>) to write LSN data: <value>.

630

Cannot run a multi device backup with the MIRRORFILE option.

If you are backing up to multiple devices, you cannot use the MIRRORFILE argument. See The BACKUP command.

632

Failed to set file pointer to current position of file.

636

BACKUP WITH CONTINUE_AFTER_ERROR successfully generated a backup of the damaged database.

637

RESTORE WITH CONTINUE_AFTER_ERROR was successful but some damage was encountered.

638

The backup was written with damaged data by a BACKUP WITH CONTINUE_AFTER_ERROR.

640

Cannot specify more than 32 devices.

You can specify up to 32 devices in a backup or restore operation. See The BACKUP command and The RESTORE command.

660

VDI library not registered.

This may be because the VDI library has become unregistered when other SQL Server components have been uninstalled. To register this library manually, first locate the sqlvdi.dll file (for 64-bit versions of SQL Server, you need to locate the 32-bit version of the file). You can then use the regsvr32 command, for example:

regsvr32 sqlvdi.dll

If you are using more than one version of SQL Server, locate the latest copy of the sqlvdi.dll file; later versions of this file are compatible with earlier versions of SQL Server.

662

The version of the VDI library used does not match the version of SQL Server. Please install the correct version of sqlvdi.dll on this server.

For example, this may occur if you have reinstalled SQL Server 2000, and you are attempting to back up a SQL Server 2005 database.

665

Beta trial period has expired.

667

Trial period has expired.

Contact licensing@red-gate.com and tell us you are evaluating SQL Backup.

668

64-bit servers require Professional license.

Please contact sales@red-gate.com for more information.

680

The media set for database '<value>' has <value> family members but only <value> are provided. All members must be provided.

The backup set that you are trying to restore is split across multiple files; the number of files you have specified does not match the number of files in the backup set.

If this error occurs when restoring transaction log backups, it may be because SQL Backup cannot put the files in the correct order because it cannot read the Log Sequence Numbers from the header files or the information is not there. You can restore these files one at a time in date order, specifying either WITH NORECOVERY or WITH STANDBY, using the extended stored procedure. This will negate the need for the SQL Backup header. See also SQL Backup warning code 170.

Alternatively, the SQBHeaderFix utility can be used to repair the files by recreating the SQL Backup header using information from the native SQL header. You can download the utility from: ftp://support.red-gate.com/Patches/SQL_Backup/SQBHeaderFix.zip

700

No process type entered.

705

When using the FULLIFREQUIRED option, the backup file name(s) must contain the dynamic tags, <DATABASE> and <TYPE>.

If you are using the FULLIFREQUIRED argument, the backup file name must include the <DATABASE> and <TYPE> tags. The <AUTO> tag may be used if the file name format includes the <DATABASE> and <TYPE> tags. See File locations tags and The BACKUP command.

710

Wrong password entered.

The RESTORE command contains an incorrect password, or if you are restoring from an encrypted backup file, the PASSWORD argument is missing.

715

Backup file is not encrypted.

You do not need to specify the PASSWORD argument in the RESTORE command.

716

None of the backup files are encrypted.

You do not need to specify the PASSWORD argument in the RESTORE LOG command.

720

No database name entered.

740

Failed to get LSN data from server.

742

Failed to get LSN data from server (0 rows returned).

743

Failed to get file position value from server.

760

LSN data from server is blank.

765

Failed to read file header (<value>): <value>. Read <value> bytes.

775

Failed to open file to write LSN data. Another process might be locking this file: <value>

SQL Backup writes a header block to each backup file upon completion of the backup. In some cases, antivirus applications may lock the backup file immediately after creation, denying SQL Backup access.

780

General conversion error.

782

Browse via SQL: registry value not set.

784

Browse via SQL: not sysadmin.

790

General thread error or SQL Server error.

Refer to your SQL Server documentation.

800

File requires SQL Backup version <value> or higher to restore. Current version is <value>.

810

Error retrieving SQL Server login name: <value>

Check that the SQL Backup Agent Service startup user has read access to the following registry key and its values: HKEY_LOCAL_MACHINE\Software\Red Gate\SQL Backup\BackupSettings.

820

Validation of all backup files failed.

821

DBCC CHECKDB: Database integrity check completed with errors.

822

Encrypted files require a password to be successfully restored.

825

To run database consistency checks, the database must be restored using the STANDBY or RECOVERY options. To recover the database after all checks have completed, include the RECOVERY parameter in the VERIFY option.

826

To run database consistency checks where multiple backup sets may be restored, the database must be restored using the STANDBY option. To recover the database after all checks have completed, include the RECOVERY parameter in the VERIFY option.

828

Failed to recover database.

829

Failed to drop database.

830

Cannot disconnect existing users when the log is not backed up with the NORECOVERY or STANDBY options.

840

File validation failed.

850

SQL Backup syntax error.

870

No command passed to SQL Backup.

The command is empty.

880

BACKUP DATABASE permission denied in database: <value>

Check that you have backup rights to the relevant database.

Check that the login account for the SQL Backup Agent Service is a Windows Authenticated account with sysadmin privileges on the SQL Server. For more information see Security Model.

If the error persists, turn off the user rights checks by creating a registry key called SkipChecks:

Locate HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\(local) or <instance name>

Create a new DWORD type registry key called SkipChecks and set the data value to 1.

Stop and restart the SQL Backup Agent Service.

To reinstate user rights checks, set the data value to 0 or delete the key.

890

RESTORE DATABASE permission denied for database: <value>

Check that you have the appropriate restore rights.

900

Failed to read backup file header (0 rows).

910

Failed to read file list details (0 rows).

915

Failed to update backup history table (BACKUPSET).

916

Failed to update restore history table (RESTOREHISTORY).

917

Failed to update backup history table (BACKUPSET). Media set ID is blank.

918

Failed to retrieve restore history id.

920

Failed to update backup history table (BACKUPMEDIAFAMILY).

930

File read error for compressed data. Backup file is incomplete or corrupted (FileBufferRemainingBytes: <value>)

932

File read error for compressed data size. Backup file is incomplete or corrupted (CompressedDataSize: <value>)

934

File read error for device index. Backup file is incomplete or corrupted (FileBufferRemainingBytes: <value>)

940

File read error for <value> bytes (balance <value> bytes). Backup file is incomplete or corrupted.

942

File read error for <value> padding bytes (balance <value> bytes). Backup file is incomplete.

950

Data decompression error: <value>

960

Failed to service command. Error code: <value>

970

Backup file does not exist. File name: <value> (for restores).

985

Error creating critical section: <value>.

990

Invalid number of virtual devices: <value>

995

Error creating event for virtual device: <value>

1000*

Failed to create virtual device. Error code: <value>

If the secondary error code is -2139684857, ensure that the SQL Backup Agent Service startup user has read access to the SQL Server service. You can do this using the sc sdset and sc sdshow commands, for example:

sc \\ServerName sdshow "sqlbackupagent"

For information about how to interpret the results, refer to your Windows® documentation.

1010*

Failed to get configuration from server. Check that the SQL Server instance is running and that you have the SQL Server System Administrator server role. Error code: <value>. [Also check that the database is not currently in use.]

For certain timeout conditions, a more detailed description may be presented with this error code:

Failed to get the configuration from the server because the timeout interval has elapsed. Check that the SQL Server instance is running, that you have the SQL Server System Administrator server role, and that no other processes are blocking the backup or restore process. If the problem recurs, try increasing the value of the VDITimeout registry setting in HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName].

or,

Failed to get the configuration from the server because the timeout interval has elapsed. SQL Backup required <bytes> bytes of free SQL Server memory, which was not available. You can reduce the memory requirements by reducing the number of backup files/threads used in the backup.

To configure the VDITimeout registry key, open the registry editor, locate the SQL Backup entries for the relevant SQL Server instance, and add a DWORD entry named "VDITimeout". Enter a duration that you feel is adequate for SQL Server to respond. The duration must be entered in seconds (in hexadecimal).

For more information, see this knowledge base article.

1020*

Failed to open virtual device. Error code: <value>

1030*

Failed to create VirtualDeviceSet component. Error code: <value>

SQL Backup uses the SQL Virtual Device Interface library to perform backups and restores. This library is contained in a file named sqlvdi.dll and is installed and registered when you install SQL Server. This error may arise when backing up and restoring databases for two reasons:

1. The sqlvdi.dll file is missing or has been unregistered, or an incorrect version of SQL Server has been installed. Check the version of the sqlvdi.dll file installed on your SQL Server.

Open Registry Editor and open HKEY_CLASSES_ROOT (32-bit edition of Windows) or HKEY_CLASSES_ROOT\Wow6432Node\CLSID (64-bit editition of Windows). Locate the key {40700425-0080-11d2-851f-00c04fc21759}. The key's value InprocServer32 contains the path to sqlvdi.dll. Ensure that the file exists and that the SQL Server startup account has access to it.

A 64-bit edition of SQL Server will have two copies of sqlvdi.dll, one for 32-bit installations and one for 64-bit installations. Because SQL Backup is a 32-bit application, the 32-bit VDI will be used by SQL Backup while SQL Server will use the 64-bit version. Therefore, it is important that the two copies of sqlvdi.dll are the same version. Using the file locations indicated by the InprocServer32 key, examine the properties on both sqlvdi.dll files to ensure the version numbers match.

2. A problem with permissions. The SQL Backup Agent Service startup account must be a member of the SQL Server sysadmin role in order to access VDI libraries. See Security Model for more information.

1040*

Process terminated unexpectedly.

1050

Failed to close VDI.

1100

SQL Server error.

Refer to your SQL Server documentation.

2010

Command exceeds permitted length.

5000

General inter-process communication (IPC) error.

5100

Error creating SQB service event: <value>

5102

Error creating SQB service event (already exists): <value>

5110

Error opening SQB service event: <value>

5120

Error setting SQB service event: <value>

5130

Error creating client event: <value>

5140

Error creating mutex: <value>

5142

Error creating mutex (already exists): <value>

5145

Failed to start SQL Backup Agent service.

5146

Inadequate rights to start SQL Backup Agent service. Please start the SQL Backup Agent service manually.

5148

SQL Backup cluster resource is stopped.

The SQL Backup Agent Service is stopped on the active node in the cluster. This may be because a failover is in progress (in which case the service should restart automatically within a few minutes), or because the service has failed, or has been deliberately stopped.

You can re-enable the service with the Windows Cluster Administrator tool (Windows Server 2003) or Failover Cluster Management tool (Windows Server 2008).

5150

Error opening mutex: <value>

5160

Error acquiring mutex: <value>

A mutex is a communication channel between SQL Backup and the SQL Server processes. In certain circumstances a mutex can become orphaned. When SQL Backup attempts to create a new mutex, the request will be rejected by Windows because a mutex of the same name already exists.

Rebooting the operating system should resolve this problem. Alternatively, use Process Explorer to identify the process which is causing the problem:

Download Process Explorer from http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx and run it.

On the Find menu click Find Handle or DLL to open the Process Explorer Search dialog box.

Type SQBMutex into the Handle or DLL substring box and click Search.

For a SQL Server instance that is functioning correctly, the handles \BaseNamedObjects\SQBMutex_ and \BaseNamedObjects\SQBMutex_data_ will exist as part of the process SQBCoreService.exe (the SQL Backup Agent). For instances other than the default, the instance name will be appended to the handle (e.g. \BaseNamedObjects\SQBMutex_SQL2005).

Select the problematic instance from the list to highlight the entry in the Process Explorer main window.

Right click this entry and select Close Handle. repeat this for the corresponding data handle.

You should now be able to start the SQL Backup Agent and connect to the server.

5170

Error releasing mutex: <value>

5200

Error creating memory mapped file: <value>

5202

Error creating memory mapped file (already exists): <value>

5210

Error opening memory mapped file: <value>

5220

Error mapping to memory mapped file: <value>

5230

Error creating named pipe: <value>

5240

SQB service did not acknowledge receipt of data: <value>

5250

Failed to connect to Service Control Manager: <value>

5260

Failed to connect to SQL Backup service: <value>

5270

Error: SQL Backup Agent service is no longer running.

5280

Error creating client event.

5290

Error creating local data store mutex (already exists): <value>

5292

Error creating local data store mutex: <value>