Hello,

I'm having a problem, where over a long period of time, say 2-4 weeks, one client will appear to be logged on to the Sesame Server as different occurrences. Example:

Host:

Andrea-PC
Andrea-PC
Andrea-PC

And since, this is a 3-user license, then no one else can log in, so it becomes a problem.

If anyone could help that would be greatly appreciated.

I have a similar issue with 2.6.2. I am running a client-server model. 18 licenses. This morning I was notified that no one could connect. I remoted into the server and noticed all 18 licenses were consumed mostly by one user who apparently had tried to connect over and over again.

So I figured, "Easy fix, I'll just kill all of his client processes."

I did that...brought the connections down to about 6 on the server. But still, no one could connect! Even myself so I couldn't even enter Server Administrator and do an orderly shutdown. My only option was to risk database corruption and do an Emergency Shutdown and then unlock all the applications.

This is hardly an improvement over 2.5!! Sesame is no longer self correcting. Now it will require someone who has access to the server (myself) to take action!

Guess my vacation plans are cancelled.   

jacker wrote on Jan 4^th, 2017 at 5:25pm:


It is self correcting in regards to network communication in the same way that 2.5 was, and has even more network self correcting(It can reconnect after a drop in communication)  You'll see the client connection count decrease after a short amount of time(<2 minutes) after killing a client process.

A few questions that may narrow down what was happening:
Was the Sesame process on the Server computer using CPU and Memory at the time that no body could connect?
Was the Sesame Server processing commands? This can be seen on the Server window.

-Ray

Sorry, I mean by "crash" is the program just hangs, then I click on it again and it becomes non-responsive and whites-out then Windows prompts me if I want to close the program and I try that then it doesn't work. So, I open task manager and end the process.

I unchecked "Allow the computer to turn off this device to save power" in Device Manager > Network Adapter > Power Management, for the Andrea-PC.

Firewall/Ports stuff has already been taken care of.

I'll wait and see if there are any problems and report back.

Already checked, all is good with ports and program in firewall settings. Thanks.

Sesame Server Error Notes

Sesame Server - Shows two instances of the same client logged on.



Client - Sesame is not open but is trying to open. Task Manager. Two instances of sesame.exe (32 bit) running.



Client - Close one instance.

Sesame Server - One less instance is running.



Client - Sesame still not open with one instance running. Close the other process sesame.exe (32 bit). Re-open sesame.exe from shortcut. Loads to 60, goes back to 59, and stays stuck on the screen at 59.



Sesame Server - Shows a new instance running. Each time trying to open the client again, shows a new instance. (e.g. clicking the icon) However, Sesame never actually opens on the screen. The instances (processes) can then be closed from the task manager.

Sesame Server - Not being able to properly shutdown from the administration menu in Sesame, I resort to Emergency Shutdown. This time the server fully shuts down, but times in the past it's froze, and I had to end the process completely from task maanger. Also, it's froze, if I was successful in opening a new instance of Sesame on the Server Computer, when attempting to do a proper shutdown.

Sesame Server - I re-open the Server. I am able to connect my client on the Server Computer. I unlock, backup, and am able to reconnect on my client from Client Computer.

1. I can't remember completely, but I think if Sesame (DB Manager) is already open on the Server-PC when the crash occurs on the other computer (e.g. Owner-PC, Jenny-PC), it will continue to work. So it seems to be running on one computer but will no longer allow another one to connect.

2. It seems to happen at random times, maybe once a month. Haven't been able to correlate it to anything yet.

3. Both 20000 and 20001 are established on Server computer and Client computer. I'll try and check Netstat again if/when the crash occurs again.

Thank you, I'll send that right away.