rxlaw 0 Report post Posted December 18, 2009 What the heck is this error that shows up in the log for backups? Every time. And where is the procedure for the update ("Patch") that I've seen others post about here? 7.7, two "lucky numbers," have been anything but with respect to Retrospect. :angry2: Share this post Link to post Share on other sites
Mayoff 124 Report post Posted December 18, 2009 When you open Retrospect it should ask you if you want to install the driver update file. That update does contain a memory bug fix. Share this post Link to post Share on other sites
rxlaw 0 Report post Posted December 18, 2009 Robin, Thank you. Unfortunately, Retrospect did not offer to update itself. I found the update patch file on the website and manually applied it. The error doesn't appear in the logs anymore. Can you tell us if that memory problem caused any untoward effects on the integrity of the backups? Bob. Share this post Link to post Share on other sites
mauricev 0 Report post Posted December 22, 2009 I'm still seeing these messages. Share this post Link to post Share on other sites
mikek70 0 Report post Posted January 2, 2010 I am seeing the same errors, also with Driver Update Version 7.7.1.102 on Win7 x64 Retrospect also locked up in the first two attempts of a full backup... Share this post Link to post Share on other sites
sbillard 0 Report post Posted January 3, 2010 I am getting this as well, but only on a Transfer backup sets operation: version 7.7.203 (64-bit) Driver Update and Hot Fix, version 7.7.102(64-bit) Share this post Link to post Share on other sites
rcohen 0 Report post Posted January 4, 2010 I'm getting the same error: http://forums.dantz.com/showtopic.php?tid/32793/ Share this post Link to post Share on other sites
cfieldgate 8 Report post Posted January 19, 2010 Hi, Yes, I am getting this too, but not on every backup. I have Retrospect 7.7 64 on Win 7 x64. All patches up to date. Share this post Link to post Share on other sites
jtb1965 0 Report post Posted February 23, 2010 I too am getting exactly the same message and have created a new post called "TMemory::freeSpace: HeapValidate failed" Cheers Share this post Link to post Share on other sites