Robert Ros Posted September 13, 2005 Report Share Posted September 13, 2005 Hello, I have tried to find information on the Dantz Website in regard to the "assert_elem817" error but the most relevant info I could find was that "Dantz had identified an issue", but I could not find the solution to that "issue". I have been using Retrospect since v2 and I have installed v5.1.177 on an older Mac8600/200MHz to run as a backup server for my SOHO laptops (R v6 clients). In the past Retrospect has never caused me any headache but I am plagued with the "assert_elem817" error and I hardly get a back-up to complete. According to the log the errror has been caused by a mismatch of the computer clock and the processor ticks. I know what this means, but can I do ? I have deleted config files, I have checked the integrity of the catalog files, all in vain. Does anybody know what the final solution is - except dumping the old 8600PowerMac and run R v6 on OS X? Thank you, Robert Link to comment Share on other sites More sharing options...
natew Posted September 14, 2005 Report Share Posted September 14, 2005 Hi Assert errors are generally caused by memory errors and ocassionally caused by problems in the software. With an older backup machine stability of the OS and RAM are big factors. What is Retrospect doing when the error occurs? How much RAM do you have on the 8600? Are you backing up OSX machines? Thanks Nate Link to comment Share on other sites More sharing options...
terryj Posted April 7, 2006 Report Share Posted April 7, 2006 I post a similar post in the os 9/express forum...Can anyone help me with this error? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.