Hi, Thanks for the replies.
I’ve checked the console logs but couldn’t make much sense of it. The user’s encounter is such….. On a normal work day, the app, both client and server works fine. Then randomly, the client side might quit on its own, without the user having to do anything. The client connects again with any major mishap. Occasionally, the server would quit on it own. In this case, the data file is usually corrupted and a repair of the data file and rebuild of indices is required. The version deployed is v15.2 while the OS is 10.11.5. Wonder why these stability issues are occurring when v15 is supposed to be certified on El Capitan. Would an upgrade of either or both help alleviate the uncertainty? Regards, Ronnie > On 8 Sep 2016, at 3:00 am, [email protected] wrote: > > I suppose you've looked at your OS X crash logs already, and turned on > client-side debugging to find out at what line(s) of code the application > crashes? Any clues there? > >> On Sep 6, 2016, at 10:53 PM, Ronnie Teo <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi All, >> >> I had a client who recently upgraded a long standing application from v13 to >> v15.2 running in a pure Mac environment. >> What used to be a very stable application, now crashes almost every >> alternate day under El Capitan, Mac OS 10.11.5. >> Both the server and all workstations are running the same OS. >> >> I wonder if anyone has experienced this and what remedies, if any are >> available? ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
