SQLVDI errors on SQL Server 2008 R2
Question
Wednesday, November 27, 2013 2:28 PM
Several days ago the Veeam backup for my SQL Server 2008 R2 server started to fail with SQLVDI errors. I originally thought it was a Veeam issue, but last night I tried running Windows Server Backup and had the same issue. I get multiple of the below errors. I've rebooted the server to no avail.
EventId = 1
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=1652. Thread=2192. Client. Instance=. VD=Global\C39D4780-8F22-494D-9CDA-E13918B97E24}1_SQLVDIMemoryName_0.
And one of the below for each of the databases.
EventId = 3041
BACKUP failed to complete the command BACKUP DATABASE msdb. Check the backup application log for detailed messages.
Then one of these for each of the databases.
EventId = 24583
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14.
SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0 Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0 Error message: A nonrecoverable I/O error occurred on file "{6113DC44-3BF4-4B61-828F-00A46365B33A}23:" 995(The I/O operation has been aborted because of either a thread exit or an application request.).
SQLSTATE: 01000, Native Error: 4035
Error state: 1, Severity: 0
Source: Microsoft SQL Server Native Client 10.0 Error message: Processed 0 pages for database 'master', file 'master' on file 1.
All replies (9)
Wednesday, November 27, 2013 3:05 PM ✅Answered
Hello,
Please go through below links and see if this helps.I will surely not uninstall SQL server as mentioned in link provided by RSINGH
Following MS articles will be of help too
http://support.microsoft.com/kb/2615182
http://support.microsoft.com/kb/919023
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers
Friday, November 29, 2013 5:04 PM ✅Answered
Registering SQLVDI.DLL seems to have resolved this issue.
Wednesday, November 27, 2013 2:35 PM
Here we have a solution for SQL 2005.
Regards, RSingh
Wednesday, November 27, 2013 3:47 PM
I checked out the links, but none of the suggestions seem to have addressed my issue. And I definitely will NOT be uninstalling SQL server.
Wednesday, November 27, 2013 5:22 PM
Hi,
Check whether the backup medium has enough space to take the backups. Also, check if there is any resource limitation on the server.
Thanks & Regards RAJUKIRAN L Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers.
Wednesday, November 27, 2013 7:24 PM
The first thing to do is install the latest SQL 2008 R2 Service Pack and cumulative update to see if the problem is resolved. MS is horrible at documenting fixes in patches.
Please see:
http://support.microsoft.com/kb/321185
Wednesday, November 27, 2013 8:14 PM
I'm at SP1 right now. I'll download SP2 and install it in the next day or so. Something to do while I digest the turkey and other goodies.
Monday, July 27, 2015 4:55 PM | 2 votes
WARNING, the sql-blogs link appears to be infected
Burke
Thursday, August 31, 2017 12:07 AM
I know this thread is quite old, but some people might still land here when researching the problem.
One of the possible solutions is to set a higher value then the default 0 (automatic) for the "Maximum Worker Threads". see more at: https://technet.microsoft.com/en-us/library/ms187024(v=sql.105).aspx
The reason is that there are not enough free threads while creating the volume shadow copy with large number of databases.
SelfMan