10 happens when the server tries to send an update or something to the client and the update fails. It will consider it disconnected and through error 10.
51 happens as part of FileMaker Pro or Go every 60 seconds or so "tickling" the server to see if it's still there. If the server doesn't receive a tickle after about two minutes, it assumes the client is gone and disconnects the session.
Do you know were I can get further info?
What kind of further info are you after?
These errors could be anything from users closing the lid on their laptop to spotty wifi, to bad cabling or a bad port on a switch or on the machine or the server. Or the user's FM crashing or them force quitting.
So there is a wide range of potential issues that would lead to these symptoms.
Your answer pretty much covers it. Can a screen saver on activation create such an error?
The screensaver itself wouldn't but any power-saving settings on the client machine or server could.
Obviously you don't want any of that enabled on the server but on the client you may not be able to avoid it.
I'm trying to eliminate all possible causes to a recurrent crash where users are unable to work and clients are not released. Error 701 WPE is the primary suspect but I need to understand every event in the admin console.
The other useful place to look is the FMS stats.log. It's not on by default so toggle it on. Watch for any spikes especially in the elapsed time per call / wait time per call around the time if the server becomes unresponsive.
The WPE error would not typically affect any Pro / Go clients.
That was my theory, also. When using FMS 12 I had this 701 error and it did not affect Pro users. IWP didn't, but I don't have much info on WebD so I don't know if this is still true.
Now when I have a crash, only by rebooting the server I can reset the DBs.
I have FileMaker testing trying to figure it out but with no luck up to now.
This weekend I'm reinstalling FileMaker Server (and Java) hoping to solve the problem.