Jump to content

Bug in Retrospect 4.3?

Recommended Posts

Hi all.




Posted a message a few hours ago about this, but it appears that it didn't make into the forum. I've discovered what appears to be a bug in Retrospect 4.3.




The computer in question originally had Retrospect 4.1, and has subsequently been updated to 4.2 and 4.3. This being the case, many of the 220 clients on the system still have specific license codes assigned to them (they pre-date the license manager).




I've found that if I remove a license from the computer that's being used by one of these clients and close Retrospect, the Retro.Config (4.2) file appears to corrupt. When trying to run Retrospect again, the main window comes up, but the computer hangs at this point and Retrospect cannot be force-quit.




Any ideas? I know that I could delete the clients in question and re-add them to the system, thereby removing their specified license code, but that's a lot of work. Shouldn't the license manager keep track of deleted licenses and reassign these computers new licenses (if they exist)?

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...