Allan, Are you running SDI mode? Check if 4D is still running in the background with nothing visible (which should cause it to quit but you never can tell).
Regards, Wayne Regards, Wayne On Wed, 18 Sep 2019 at 08:27, Allan Udy via 4D_Tech <[email protected]> wrote: > > Hi all, > > Starting to get a bit desperate here, so wondering if anyone else has > come across this issue ..... one of our customers is running a built > server, v17R4. The Server is running on Windows Server 2019, upwards of > 15 clients running on Windows 10. > > The bulk of the clients are fine, but there's a couple who are regularly > having issues with the 64-bit client crashing with the standard error > message '4D Volume Desktop has stopped working', and so they revert to > using a 32-bit client which works perfectly fine for them. Quite often > the client user will attempt to restart 64-bit several times (after > having used it OK for an hour or so), and it simply will not start at > all (hence the reversion to 32-bit client). > > Customer is very reluctant to move to v17R5 (64-bit only) until this > issue is resolved, and I can understand why! > > Anyone have any suggestions as to what I could look at to solve this? > > > Cheers, > Allan Udy > > Golden Micro Solutions Ltd, Blenheim, New Zealand > http://www.golden.co.nz<http://www.golden.co.nz> > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
