Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About LarryT

  • Rank
    Occasional forum poster
  1. Thanks for the fast reply Robin! If anyone else can confirm that this was in fact a bug in version 6.5, it would be very helpful and also a little discouraging.
  2. I am attempting a disaster recovery for a customer using a disk which was created using their Retrospect 6.5 Disaster Recovery wizard. All goes well at first...the system boots from the disk, does some Windows preparation & starts Retrospect - Disaster Recovery. At that point a prompt appears saying: 'Insufficient license -- The current license code does not allow Retrospect to run under this OS. Please enter a new license code or click Purchase for information on obtaining license codes.'. I don't understand. The disaster recovery .iso was created using a licensed copy of Retrospect running on this OS (Windows SBS 2003 Standard SP2). The Disaster Recovery Add-on license was also applied. I have tried entering both of these license codes at the prompt to no avail. When I select 'Quit', the system reboots and the same prompt appears again. Has anyone else encountered this problem? If so, can someone please tell me how to get around this prompt?
  3. 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.