Assertion failure

DonFerguson

Red Gate Support -- at this point this is just an FYI more than a problem.

ERROR - full backup [multiple databases] on ServerName\InstancName at 1/6/2010 12:14:29 AM

SQL Backup log file 6.3.0.48

-SQL "BACKUP DATABASES [*] TO DISK = 'BackupPath\<database>\<AUTO>.sqb' WITH ERASEFILES_ATSTART = 4, MAILTO_ONERROR = 'i.s.sqlserveralerts@domain.com;i.s.backupadmins@domain.com', DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COMPRESSION = 4, THREADCOUNT = 3, VERIFY "

---

ERRORS AND WARNINGS

---

1/6/2010 12:10:22 AM:
1/6/2010 12:10:22 AM: Verifying files:
1/6/2010 12:10:22 AM: (Backup Path removed)
1/6/2010 12:10:22 AM:
1/6/2010 12:12:22 AM: VDI error 1010: 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; or try increasing the value of the VDITimeout registry setting in HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName]
1/6/2010 12:12:22 AM: Assertion failure (D:\SQL Backup\Components\SDAC 4.10.0.10\Source\OLEDBAccess.pas, line 2183)1/6/2010 12:12:22 AM:
1/6/2010 12:12:22 AM: Memory profile
1/6/2010 12:12:22 AM: Type Maximum Minimum Average Blk count Total
1/6/2010 12:12:22 AM:

---

---

---

---

---

---

1/6/2010 12:12:22 AM: Commit 6544687104 4096 2932893 2400 7038943232
1/6/2010 12:12:22 AM: Reserve 61102555136 4096 375450642 163 61198454784
1/6/2010 12:12:22 AM: Free 6812856614912 4096 42574905164 205 8727855558656
1/6/2010 12:12:22 AM: Private 61102555136 4096 33509329 2033 68124467200
1/6/2010 12:12:22 AM: Mapped 1585152 4096 146090 66 9641984
1/6/2010 12:12:22 AM: Image 32071680 4096 222605 464 103288832
1/6/2010 12:12:22 AM:

Eddie D

Thank you for your post into the forum.

An assertion error is very rare with regards to SQL Backup. Are there any entries in the SQL Server Error Logs and SQL Server VDI Logs that help in identifying the cause of the issue?

Is this the first occurence? Or something you are experiencing intermittently?

What version of SQL Server and service pack level of the server that generated this error?

Many Thanks
Eddie

DonFerguson

I have seen in maybe a few times, but it's rare and doesn't seen to be a problem at this point. I have not seen anything in the logs that indicate a cause. The instance that produced this one is running on SQL 2005 SP2 build 9.0.3159 x64.

Like I stated in the initial post, this is more of an FYI.