VSS Provider SQLVDI Errors

The error is typically caused by a problem with one of the SQL instances. In order to troubleshoot the problem you must first figure out which SQL instance has the problem. Usually, the problematic SQL instance will be named in the first recorded SQLVDI error.

For Example:

Log Name: Application
Source: SQLVDI
Event ID: 1
Level: Error
Description:
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=4772. Thread=10300. Client. Instance=SBSMONITORING. VD=Global\{3AB8F080-950C-4EF9-B637-0F37B2428F17}1_SQLVDIMemoryName_0. 

In this example, the SQL instance named SBSMONITORING is failing the snapshot.

There may also be an error message from source SQLWRITER that occurs at about the same time as the first SQLVDI error. The SQLWRITER error message may identify the database name that is having a problem with the snapshot.

For Example:

Log Name:      Application
Source:        SQLWRITER
Event ID:      24583
Description:
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: 945
Error state: 2, Severity: 14
Source: Microsoft SQL Server Native Client 10.0
Error message: Database 'SBSMonitoring' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.

In this example, the database named SBSMonitoring is having a problem.

Once you have identified the SQL instance that is having a problem, the first step would be to test the backup with that SQL instance stopped. In our example of the SBSMonitoring instance, you would stop the following service on the server:

SQL Server (SBSMonitoring)

You would then run the backup job with the affected SQL Server instance stopped. If the backup completes then you know the failure is caused by the SQL instance that is not running. Youwould then examine the SQL errorlog files and the event logs to see if we can determine what is wrong with that particular instance of SQL server.

If youcan't determine the problematic SQL instance from the event logs, you can always stop all the SQL instances on the server and try to run backup with SQL stopped. If all the SQL instances are stopped, the SQL VSS writer will not be used.

On a default installation of Small Business Server 2008 you would stop the following services:

SQL Server (SBSMonitoring)
Windows Internal Database

On a default installation of Small Business Server 2011 Standard you would stop the following services:

SQL Server (SharePoint)
SQL Server (SBSMonitoring)
Windows Internal Database

Hello Jacob,

I already checked the VDI errors. The first VDI error is attached on top (first message)

SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=12072. Thread=14784. Client. Instance=. VD=Global\{58216286-8A1C-4A6E-B44C-B3E546C33469}1_SQLVDIMemoryName_0. 

The error Instance = .

All VDI errors are pointing to =.

If the backup fails and I start it again it is working most times, so it has nothing to do with a specific maschine

Hello Jacob,

I already checked the VDI errors. The first VDI error is attached on top (first message)

SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=12072. Thread=14784. Client. Instance=. VD=Global\{58216286-8A1C-4A6E-B44C-B3E546C33469}1_SQLVDIMemoryName_0. 

The error Instance = .

All VDI errors are pointing to =.

If the backup fails and I start it again it is working most times, so it has nothing to do with a specific maschine