Quite some time ago I started a topic on what i thought were phantom users and initial indications from the users were that nothing out of the ordinary was happening.

Well just yesterday, I witnessed an error on one of the users desktops.

The application was minimized for quite some time and when they maximized it, the following Sesame error message popped up:

Error: communications error - sesame server is no longer communicating with this client.  Client will exit. 

By clicking OK, it shuts down the application but indicates that they are still logged on the server.

When they re-open the application, certain programming does not run for them.

I think (?) the message assoicated with this from the sesame log indicates "server_warning S_ENG 510562 Error:  Cannot collect client information. 

Does this shed anymore light on the subject ? i.e. whether this is Sesame issue or Microsot operating system issue ?

I would definitely like it to go away as I am constantly have to shut down the particular server running this application and re-start it and un-lock the database.

Thanks,

Louis

Ray:

The server was definitely not shut down.

Some examples of programming that doesn't run in this case (that I know) of are: code associated with closing the menu tree upon form entry and @calendar feature.

How do I send the files to you ?  I don't see an attach feature here

Thanks,

Louis

Ray:

I actually sent them to erika@hammerdata.

Are you able to check her email or should I send them to you now ?

Thanks,

Louis

Louis,

possibly, DHCP lease time expired?

DHCP is a service, usually provided by a router, that tells each computer hooked up to and booted on your net what its IP address should be. There is a parameter that decides how long any one computer should get to keep its IP address before it is assigned a new one. This is called "lease time". Very often, the IP address assigned will be the same as the one that expired, but sometimes - not.

The DHCP client computer is meant to renew its lease on its IP address at 50% of the assigned lease time, thus avoiding this situation. But, if the client fails to renew its lease until after the lease has expired, the client may get assigned a new and different IP address.

Sesame is okay with DHCP, but since Sesame keeps a constant connection, changing the IP address suddenly (during the middle of a command, for instance) will look like a wire disconnect to Sesame server.

Ray:

I am going to guess around 11 ish.  It seems to lose the connection after a couple of hours of minimizing Sesame.

Are you trying to match up to the log ?

Thanks,

Louis

Mark/Ray:

It turns out the computer has a screensaver and has been setup with System Standby at 20 mins.  We have taken both these features off and will test to see if it still acts up.

However, I am not so certain this will resolve because my system is set with a screensaver and Standby is set to 1 hour.

I will keep you posted.

Thanks,

Louis

How about using a static IP address for those affected stations?