Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About leachdb1

  • Rank
    Occasional forum poster
  1. 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.