My client has a strange, intermittent problem with Sesame. For weeks at a time things run suddenly, then on any given day they will suddenly get kicked off of Sesame if the client is idle for 2 or 3 minutes.

It does not matter if the client is remotely connect over the internet, on the local network, or running on the server console itself.

The client receives two error boxes and then exits:

Error: Cannot save changes the the current database. File permissions may be locked.

Error: Communications error - Sesame is no longer communication with this client.
Client will exit.

...and the server log displays many of the following error messages:

S_COM 510091      Communications error with socket set notice.

What do I suspect first? This intermittent problem has been haunting us for over a year now...

I've rebooted the server a couple of times...doesn't seem to make a difference. Does Automatic Updates cause a problem in itself or are you suggesting a particular Update is causing the problem?