SQLVDI errors in application event logs during SQL backups

[LarryT]

We are receiving 5 errors every day during Retrospect 7.5 (version 7.5.387) backups of SQL. The errors only occur on databases within the default instance. Databases in a separate instance backup without error.

 

Our server is running SBS2003 SP1 and SQL Server 2005. The server name is "sbs".

 

Error:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQL$SBS. ErrorCode=(1060)The specified service does not exist as an installed service.

. Process=228. Thread=9776. Client. Instance=SBS. VD=.

 

After the error (within 1-2 seconds), we receive an information message:

Database backed up. Database: master, creation date(time): 2007/08/09(13:07:54), pages dumped: 371, first LSN: 234:376:37, last LSN: 234:400:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'dantz_retrospect_vd_master'}). This is an informational message only. No user action is required.

 

It appears that the databases are being backup up but we would like to fix the errors. We have found only 1 other post on this topic and no resolution was given.

 

Any troubleshooting ideas will be greatly appreciated.

[leachdb1]

We are experiencing the same problem. After each SQL database in the server in which Retrospect 7.5.387 is installed is backed up by Retrospect, this same err msg is logged.

 

I searched MS TechNet and there are many hits for keyword 'SQLVDI' (http://search.technet.microsoft.com/Search/Default.aspx?query=SQLVDI&brand=technet&locale=en-US&refinement=00&lang=en-us). Searching through the hits, I noticed that there is one hotpatch available for SQL Server 2005 (SQL vers. that is installed in our servers) but the err msg is different and SQL Server 2005 SP2 is required to be installed and we have only SQL Server 2005 SP1 installed (http://support.microsoft.com/kb/934396).

 

I believe that this err msg is due to a SQL Server Agent call that Retrospect v7.5 makes that either Windows 2003 Server SP1 or SQL Server 2005 SP1 (that we have installed) does not like. Note: we previously had Retrospect v7.0 and SQL Server 2000 installed in this same server and it was backing up the same databases w/o incurring this err. We recently upgraded to Win2003 Server SP1, Retrospect 7.5.387, and SQL Server 2005 SP1 all at the same time in this server, so am not sure which upgrade caused this err msg to appear.