SQL Backup 5.2   

Errors

See Also

The errors that SQL Backup may return are listed below.

Warning codes

The following warning codes may be returned by SQL Backup.

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>

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>

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>

165

Failed to process file: <value>

166

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

170

Validation error when processing the list of transaction log backups.

175

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

180

Encountered a warning during the VDI process.

200

Error creating backup file: <value>

210

Error writing to backup file: <value>

220

No log files found to be restored.

300

Backup failed. Retry attempt: <value>

320

Validation failed.

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>

411

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

420

Failed to insert data into local data store: <value>

430

Failed to update local data store: <value>

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 four characters or fewer.

Error codes

The following error codes may be returned by SQL Backup.

Error code

Description

500

General SQL Backup error.

505

No SQL Backup file name entered.

510

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

512

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

515

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

516

Multi database operations cannot use MIRRORFILE option.

517

Cannot use MAXDATABLOCK parameter with local files: <value>

518

File name exceeds limit of 259 characters: <value>

520

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

525

Directory does not exist. Directory name: <value>

526

Cannot find saved setting.
Check that the SQL Backup 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)

530

Non-existent backup file.

540

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

550

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

560

File does not exist: <value>

562

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

570

File is not a SQL Backup file.

580

Failed to open file. Message: <value>

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

595

Failed to create MTF file: <value>

600

Multiple log file validation error for restore.

605

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

610

Error creating file handle for file: <value>

620

Error writing to backup file(s).

625

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

630

Cannot run a multi device backup with the MIRRORFILE option.

640

Cannot specify more than 32 devices.

660

VDI library not registered.

662

Cannot use SQL Server 2000 VDI library for a SQL Server 2005 instance. 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.

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.

700

No process type entered.

710

Wrong password entered.

715

Backup file is not encrypted.

716

None of the backup files are encrypted.

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.

770

Failed to write LSN data to file: <value>

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.

790

General thread error.

800

File creation error: <value>

810

Error retrieving SQL Server login name: <value>

820

Validation of all backup files failed.

850

SQL Backup syntax error.

870

No command passed to SQL Backup.

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

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

935

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

940

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

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>

1010

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

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.

1100

SQL Server error.

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.

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>

*VDI errors 1000, 1010, 1020, 1030, 1040

If SQL Backup encounters VDI errors 1000, 1010, 1020, 1030, or 1040, SQL Backup attempts the backup again, reducing the MAXTRANSFERSIZE parameter in case the error was caused by an insufficient amount of contiguous memory on the SQL Server. SQL Backup attempts the backup five times in total, using the MAXTRANSFERSIZE values 1048576, 524288, 262144, 131072, 65536 respectively.

 

 

 


© Red Gate Software Ltd 2007. All Rights Reserved.