Unexpected Quitting - Crash Log
Hi guys,
I have a client whose 4D database started "unexpectedly quitting" after
over a year of problem free running on 4D Server/Client v2003.5. It
happened immediately after he took it upon himself to upgrade to 4D
Server/Client v2003.7. It started quitting, so he then tried to go back
to v2003.5 but, in the process, he opened it up with several mixed
Server and Client versions, .res and .rex all over the place, etc...
Anyway, it's quitting frequently now, particularly in one area of the
database. The code has not changed in a year, and like I said, it has
been running fine. I "rejuvenated" the structure and datafile (Tools,
export/import data into new fresh unindexed datafile, opened with
indexed structure to rebuild indexes and relations, SanityCheck,
DataCheck, trash .res and .rex, new versions of Server and Client,
blah, blah), and none of that had any effect.
We found a 4D Client Crash Log, which has been logging the crashes, but
I don't know what to make of it. I'm wondering if someone can lend some
insight as to the cause of the quitting and/or what the crash log is
pointing to.
Here is one of the crashes, from the log. What's it mean?
Mac OS 10.2.8
TIA,
Sam
(Continue reading)