Bernd, Hello...
Yes, we are aware that this is potentially network related, but try explaining that to a customer and not have them think your pointing fingers, or passing the blame. The biggest issue is we are getting these errors from a Client that is running on the Server. Steve ********************************************* Stephen J. Orth The Aquila Group, Inc. Office: (608) 834-9213 P.O. Box 690 Mobile: (608) 347-6447 Sun Prairie, WI 53590 E-Mail: [email protected] ********************************************* -----Original Message----- From: 4D_Tech <[email protected]> On Behalf Of Bernd Fröhlich via 4D_Tech Sent: Tuesday, April 9, 2019 1:44 AM To: [email protected] Cc: Bernd Fröhlich <[email protected]> Subject: RE: Error connecting to 4D Server Stephen J. Orth: > What we get are the multiple errors that started this thread, where already > connected clients simply can no longer talk to the server. Either you get > the -10002/3/4 error message, or the one that is happening mostly is the > "non-blocking" error. I encounter those from time to time. Usually that means, there are network related problems. (Bad/broken cable, too much load on the network, flaky VPN connection, etc...) Nothing much on the 4D side that you can do about that. Greetings from Germany, Bernd Fröhlich ********************************************************************** 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] **********************************************************************
