How can we help you today? How can we help you today?

Error: Device index out of range: 191

I'm encountering an error restoring a database. The restore from this file has worked multiple times before, suddenly, I'm getting failures 5 minutes and 50 seconds into the restore process. Any insight would be appreciated. Here is the log file:

SQL Backup log file
5/23/2008 12:20:50 AM: Restoring MyDB (database) from:
5/23/2008 12:20:50 AM: E:\SQLBackups\MyDB\FULL_(local)_MyDB_20080514_123704.sqb

5/23/2008 12:20:50 AM: RESTORE DATABASE [MyDB] FROM DISK = 'E:\SQLBackups\MyDB\FULL_(local)_MyDB_20080514_123704.sqb' WITH RECOVERY, MOVE 'MyDB' TO 'E:\SQL_DATA\MyDB_1.MDF', MOVE 'MyDB_log' TO 'G:\SQL_DATA\MyDB_2.LDF', REPLACE

5/23/2008 12:25:16 AM: Thread 0 error:
Process terminated unexpectedly. Error code: -2139684860

Device index out of range: 191
5/23/2008 12:25:16 AM: Thread 1 error:
Failed to service command. Error code: -2139684860
Process terminated unexpectedly. Error code: -2139684860

Device index out of range: 191
5/23/2008 12:25:16 AM: Thread 2 error:
Failed to service command. Error code: -2139684860
Process terminated unexpectedly. Error code: -2139684860

Device index out of range: 191

SQL error 3013: SQL error 3013: RESTORE DATABASE is terminating abnormally.
SQL error 3203: SQL error 3203: Read on 'SQLBACKUP_4B0CE1ED-61D2-4FA3-AC57-F064F49EB3FA02' failed, status = 995. See the SQL Server error log for more details.

Thanks,
dKK
dakaratekid
0

Comments

1 comment

Sort by
  • Brian Donahue
    Hi DKK,

    This problem had appeared in SQL Backup 5.2 when restoring a multithreaded backup with verification. It has been addressed in 5.3, so you may want to right-click your server in the SQL Backup console and check the server components properties for the server you are restoring to. If it's 5.2, then you can use the check for updates function on the help menu and get the latest version and copy SQBServerSetup.exe to the server and run it to upgrade the server components.

    If this doesn't solve the problem, please let us know.
    Brian Donahue
    0

Add comment

Please sign in to leave a comment.