MIKEMCENROE Posted May 2, 2008 Report Share Posted May 2, 2008 I'm getting an error on Retrospect startup, the splash screen comes up and then I get Assertion Failure at "tsynch.cpp-127" I'm running retrospect 7.5.324 on Windows NT4 SP6 I've removed retrospect, rebooted and reinstalled and still get the error? any ideas? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted May 2, 2008 Report Share Posted May 2, 2008 Sounds like you have corrupt preferences. You may need to remove the config75.dat file and try again. Quote Link to comment Share on other sites More sharing options...
MIKEMCENROE Posted May 2, 2008 Author Report Share Posted May 2, 2008 Hi Robin thanks for replying, I've removed config75.dat and bak and I still get the same message as the splash screen appears. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted May 2, 2008 Report Share Posted May 2, 2008 How much RAM do you have on the computer? How much free space on the C drive? Quote Link to comment Share on other sites More sharing options...
MIKEMCENROE Posted May 9, 2008 Author Report Share Posted May 9, 2008 There is 700Mb free on drive C, and 240Mb free RAM. Quote Link to comment Share on other sites More sharing options...
MIKEMCENROE Posted May 9, 2008 Author Report Share Posted May 9, 2008 i've removed 7.5.324 off the server, and reinstalled it, there also appears to be remenants of 5.6 still on the server/registry I am unable to uninstall the other bits of 5.6, is there a install cleaner tool that can clear any scraps of the previous installs, I'm hoping to clear the machine of any trace of Retrospect and start again. though reinstalled NT is a non-starter for various reasons. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted May 9, 2008 Report Share Posted May 9, 2008 You can not run Retrospect on a computer with only 700 MB free on the C drive. Retrospect 7.5 requires between 5 and 10 GB of free space on the C drive for each execution unit you are running. Registry keys are not a factor in any way. Quote Link to comment Share on other sites More sharing options...
MIKEMCENROE Posted May 9, 2008 Author Report Share Posted May 9, 2008 Thanks for that Robin, has that always been the case? as they have been running retrospect 7.x for the last few months with that amount of free space and it had been backing up fine , the NT server is around 7 years old and has always had a 4gb c: drive Quote Link to comment Share on other sites More sharing options...
Mayoff Posted May 9, 2008 Report Share Posted May 9, 2008 These guidelines came about with Retrospect 7.5. Retrospect 7.5 uses temporary disk space to cache memory during different operations. The more files and the more execution units, the more disk space you will need. The best configurations are 2 GB of RAM and 5 to 10 GB of free space on the C drive for each execution unit you are running. Quote Link to comment Share on other sites More sharing options...
MIKEMCENROE Posted May 9, 2008 Author Report Share Posted May 9, 2008 robin, the problem appears on startup of the application , before anything is happening, as soon as the splash screen appears I get; Assertion Failure at "tsynch.cpp-127" Quote Link to comment Share on other sites More sharing options...
Mayoff Posted May 9, 2008 Report Share Posted May 9, 2008 Have you tried removing the entire Retrospect folder under Application Data? It could fix this. Quote Link to comment Share on other sites More sharing options...
MIKEMCENROE Posted May 9, 2008 Author Report Share Posted May 9, 2008 There doesnt appear to be a application data folder under Windows NT Quote Link to comment Share on other sites More sharing options...
Mayoff Posted May 9, 2008 Report Share Posted May 9, 2008 Try to locate the RtrExec.dir folder and delete it. It should be in the same folder with config75.dat, in your case it will probably be the Retrospect application folder. Also, make sure you do not have 2 different RDU.rpx files (one that has been renamed to something like rdu.old.rpx) Quote Link to comment Share on other sites More sharing options...
MIKEMCENROE Posted May 9, 2008 Author Report Share Posted May 9, 2008 thanks for your efforts robin, still no luck I'm afraid. Quote Link to comment Share on other sites More sharing options...
MRIS Posted May 10, 2008 Report Share Posted May 10, 2008 You would be better advised to move retrospect to a more "modern" computer and simply install the retrospect client agent onto the server. Quote Link to comment Share on other sites More sharing options...
MIKEMCENROE Posted May 12, 2008 Author Report Share Posted May 12, 2008 MRIS, unfortunately its a customer of ours who owns the machine, not my own, i've just been tasked with fixing the problem. Quote Link to comment Share on other sites More sharing options...
MRIS Posted May 15, 2008 Report Share Posted May 15, 2008 has it ever worked? Quote Link to comment Share on other sites More sharing options...
MIKEMCENROE Posted May 16, 2008 Author Report Share Posted May 16, 2008 yes, it has worked for many years, from version 5.6 upwards. Quote Link to comment Share on other sites More sharing options...
MRIS Posted May 16, 2008 Report Share Posted May 16, 2008 Please try version 7.5.508 of Retrospect, download available via "Retrospect Updates" at the top of this page. I've fired up my trusty NT4 virtual machine to give this a try myself I have attached a screenshot showing the error I get. Turns out this is because (there is a bug in retrospect) that can be worked around by installing the desktop update with IE4 before upgrading IE to version 5.5.... Quote Link to comment Share on other sites More sharing options...
Mayoff Posted May 16, 2008 Report Share Posted May 16, 2008 Please try the latest beta, it has better support for NT4 as a client. I don't think we have tested it running the application itself. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.