Hi,

Having a problem with Sesame server app crashing on different occassions. Trying to figure out what is causing it.

Running on Windows 2003 Server with SP2. Not sure if it is a coincidence, but has been starting to do so since upgrading to 2.5.2

Event viewer shows the following error:
Faulting application sesame.exe, version 0.0.0.0, faulting module sesame.exe, version 0.0.0.0, fault address 0x00143012.

Sesame server log shows:
server_error S_COM 510091 Communications error with socket set notice.
client_note S_COM 510106 Communications error while receiving a reply
client_error S_CLIENT 600600 Sesame server is no longer communicating with this client.

A restart of the Sesame server application and unlocking databases gets us up and running.

The only recent changes are:
Sesame server updated to 2.5.2
A few windows updates have been installed

Prior to this, we had no issues running 2.5.1
Most clients are running 2.5.2. We have a few users still running 2.5.1. Could this cause the server to crash?
Previously we had server running 2.5.1 and clients running 2.5 with no issues at all.

Any help appreciated.

Cheers
AJ

Hello AJ,

Like Carl said, you want to be sure that all clients are running the same version as the Server. If it still happens with all computers using 2.5.2, send your server log file and a few client log files to support@lantica.com and I'll have a look at them and we'll go from there.

-Ray