SQL Backup Failing

UrsusHorribilis

Version 5.2.0.2807 I lowered SQL Mem & retsarted the Instance, no luck. Any help would be much appreciated, Thanks

Restoring Content (database) on SQLQA10 instance from:
G:\sqlrec\content_Refresh.sqb

VDI error 1010: Failed to get configuration from server. Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator server role. Error code: (-2139684861: The api was waiting and the timeout interval had
elapsed.)
Also check that the database is not currently in use.
SQL error 3013: RESTORE DATABASE is terminating abnormally.
SQL error 3201: Cannot open backup device 'SQLBACKUP_800160A3-D9DC-48C7-8C42-B591C24BD432'. Operating system error 0x80770006(error not found).

Memory profile
Type Maximum Minimum Average Blk count Total

---

---

---

---

---

---

Commit 35651584 4096 320720 884 283516928
Reserve 4261347328 4096 38924361 111 4320604160
Free 6876207382528 4096 65122139522 135 8791488835584
Private 4261347328 4096 7825732 575 4499795968
Mapped 1585152 4096 168090 53 8908800
Image 33271808 4096 259989 367 95416320


SQL Backup exit code: 1010
SQL error code: 3201

petey

Could you please post the contents of the SQL Backup log for that restore task? The default folder where the logs are stored is C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance name>.

UrsusHorribilis

SQL Backup log file
9/4/2008 3:15:33 PM: Restoring Content (database) on SQLQA10 instance from:
9/4/2008 3:15:33 PM: G:\sqlrec\content_Refresh.sqb

9/4/2008 3:15:33 PM: RESTORE DATABASE [Content] FROM DISK = 'G:\sqlrec\content_Refresh.sqb' WITH RECOVERY, MOVE 'Content_Data' TO 'F:\MSSQL.1\MSSQL\Data\Content_Data.mdf', MOVE 'Content_Log' TO 'G:\MSSQL.1\MSSQL\SQLLogs\Content_Log.ldf'

9/4/2008 3:16:03 PM: VDI error 1010: Failed to get configuration from server. Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator server role. Error code: (-2139684861: The api was waiting and the timeout interval had elapsed.)
9/4/2008 3:16:03 PM: Also check that the database is not currently in use.
9/4/2008 3:16:03 PM: SQL error 3013: RESTORE DATABASE is terminating abnormally.
9/4/2008 3:16:03 PM: SQL error 3201: Cannot open backup device 'SQLBACKUP_800160A3-D9DC-48C7-8C42-B591C24BD432'. Operating system error 0x80770006(error not found).
9/4/2008 3:16:03 PM:
9/4/2008 3:16:03 PM: Memory profile
9/4/2008 3:16:03 PM: Type Maximum Minimum Average Blk count Total
9/4/2008 3:16:03 PM:

---

---

---

---

---

---

9/4/2008 3:16:03 PM: Commit 35651584 4096 320720 884 283516928
9/4/2008 3:16:03 PM: Reserve 4261347328 4096 38924361 111 4320604160
9/4/2008 3:16:03 PM: Free 6876207382528 4096 65122139522 135 8791488835584
9/4/2008 3:16:03 PM: Private 4261347328 4096 7825732 575 4499795968
9/4/2008 3:16:03 PM: Mapped 1585152 4096 168090 53 8908800
9/4/2008 3:16:03 PM: Image 33271808 4096 259989 367 95416320
9/4/2008 3:16:03 PM:

petey

I would check the sqlvdi.dll versions.

In the registry, look for the key {40700425-0080-11d2-851f-00c04fc21759} in HKEY_CLASSES_ROOT. In the subkey InprocServer32, look for the copy of sqlvdi.dll that is used. Check the version number of this file. If you are running a 64-bit system (which I think you are), you should find another entry in HKEY_CLASSES_ROOT\Wow6432Node\CLSID. Again, check the version number of this file and ensure it matches the 64-bit copy.

If you are using SQL 2005, you must use the SQL 2005 versions, and if you are using a 64-bit SQL Server, the 32-bit and 64-bit versions of sqlvdi.dll must match. If you are using SQL 2000, you can use the SQL 2005 libraries.

Let us know the versions of the 32-bit and 64-bit sqlvdi.dll files that are registered on your system.

UrsusHorribilis

The system is x64, running both sql 2000 & 2005. I checked the sqldvi.dll version, it's 2000.85.2101.0. I looked at another x64 system running sql2005 only & the sqldvi.dll version is 2000.85.2004.0. Thanks

petey

Are both sqlvdi.dll files referenced in

HKEY_CLASSES_ROOT\CLSID\{40700425-0080-11d2-851f-00c04fc21759}

and

HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{40700425-0080-11d2-851f-00c04fc21759}

version 2000.85.2101.0?

UrsusHorribilis

yes

petey

Build 2101 was released specifically for SQL Server 2000: http://support.microsoft.com/default.as ... -us;935465, while build 2102 was a hotfix for SQL Server 2005: http://support.microsoft.com/default.as ... -us;934396.

Somewhere along the way, a service pack applied build 2101, ignoring the fact that SQL Server 2005 was also installed on the system. If possible, you should try installing the hotfix that contains build 2102.

UrsusHorribilis

Thanks, I'll give it a try.