Warning code

Description

110

Failed to save primary log file: <value>

115

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

120

LOGTO error: Folder does not exist: <value>

121

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

130

MOVETO error: Failed to move file: <value>

131

MOVETO error: Failed to execute MOVETO command.

132

MOVETO error: Folder does not exist: <value>

140

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

141

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

142

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

143

COPYTO error: Failed to copy file: <value>

144

COPYTO error: Folder does not exist: <value>

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>

150

MAILTO error: SMTP host name not defined.

151

MAILTO error: Failed to send mail.

160

ERASEFILES error: Failed to delete file: <value>

161

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

162

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

164

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

166

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

167

Failed to get database size from server.

168

Failed to identify filestream files.

170

Validation error when processing the list of transaction log backups.

175

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

195

Failed to update backup history table (BACKUPMEDIAFAMILY).

200

Error creating backup file: <value>

202

Multiple attempts were made to create the backup file.

210

Error writing to backup file: <value>

213

Error setting file pointer position: <value>

215

Error flushing buffer contents to file: <value>

218

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

220

No log files found to be restored.

225

Files missing from backup history.

226

Files missing from search folder.

300

Backup failed. Retry attempt: <value>

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.

400

Failed to initialize local data store: <value>

402

Failed to open local data store: <value>

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 in your log shipping restore job are available.

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

435

Get exclusive local data store access failed - timeout.

436

Get exclusive local data store access failed - abandoned.

438

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

440

Invalid DB handle.

442

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

445

Local data store error: <value>

450

Local data store SQL error: <value>

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.

471

Failed to run sp_change_users_login report while checking for orphaned users.

Error code

Description

500

General SQL Backup error.

505

No 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 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 Using SQL Backup to back up to 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 The BACKUP command and File location tags.

If you want to overwrite the 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. You use the <AUTO>, <DATABASE>, or <DATETIME> tags to do this. See The BACKUP command and Toolkit syntax examples.

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 Toolkit 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 (32-bit) or
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Red Gate\SQL Backup\BackupSettings (64-bit)

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 Toolkit 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.

585

Cannot use multiple file names with the SINGLEFILE 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.

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.

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.

650

File already flushed to disk; cannot service another flush request.

651

File already flushed to disk; cannot process additional backup data.

653

File already flushed to disk, but buffer not empty.

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.

700

No process type entered.

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.

730

Command line gateway not defined.

740

Failed to get LSN data from server.

742

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

750

No LSN data returned 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.

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 (32-bit) or
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Red Gate\SQL Backup\BackupSettings (64-bit)

820

Validation of all backup files failed.

830

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

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.

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).

980

Your license does not allow restoring files encrypted with 256-bit keys.

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>

1040

Error during backup / restore process.

1050

Failed to close VDI.

1060

Error cancelling command: <value>

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>

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>