Infinity wrote on Oct 9^th, 2007 at 2:47pm:


Then you've got something else going for you. Have you noted the CPU usage on the Server system when this happens? I need to know what the CPU usage is at this time and if it's possible what each user is doing.

-Ray

It worked pretty good today until about 3:00 pm and it started freezing up on exit again, still running without daemon, have no idea what causing it now. 

I had a shortcut in the startup folder to start sesame server when the m/c starts, it still had the daemon switch, maybe that was causing the problem after the session with hammer. I finally have a user besides myself and now I'm in and out of the office so I don't know whats happening when I'm out, she's not computer literate but she wants to learn.Today should tell. Its been a rough week thank you tech-support or all the help !!!  [size=14][/size]

What is the m/c?

The Server machine.

Infinity wrote on Oct 31^st, 2007 at 6:27pm:


Were the other four users able to move around Sesame still? What were they all doing? Did you happen to see if the Commands Processed counter on the Sesame Server window was increasing?

Quote:


The failed to Create a Local Socket erorr message, which I'm betting is the one you got, will appear if Sesame Server is already running and you try to start another one on the same ports. So the original server was still running when the second one was trying to start up.

Quote:


No.

Quote:


If the server is not busy running a Save or Load then it should take I think less than 10 seconds. and that is by killing the Sesame Process on the client. An actual client close frees up the License seat in under a second.

Quote:


No. Sesame Server will allow connections up to the point that the max number of Clients has been reached. Once it has been reached it will not allow connections again until a current client leaves, but once one of the current clients leave that seat is open and can be taken by a new client. So that is not possible.

-Ray

Quote:

Unfortunately, I do not know the answer to either of these questions.  The urgency of the situation was such that I had to bump everyone off immediately; I had no time for investigation.
Quote:

Sorry, I did not notice; I did not look to see.  I've barely noticed that part of the interface, as I do not know what it does or what it means beyond what is explained on page 489.  I still have much to learn.  Mostly I keep an eye on the Open Applications box.  If the situation happens again I'll be sure to take a look and report what I see.
Quote:

Well, not to argue, but I'm almost sure this is not the case.  When I shut down Sesame Server I used Server Administration.  It ran its notification routine, shut down my client, and then shut down SS.  It was only then that I tried starting it up again.  But again, we were in rush mode so who can say?  It shut down when I acknowledged its error message, and then I started it up again, after which all was well.  I'm pretty sure the "socket" error said something about "available", but in my haste I did not write it down and my memory sucks since the ECT. In any event, I'll be sure to try to take my time in the future, just in case. 
Quote:

Good to know, thank you.  I'll keep an eye on this.  I'm tempted to buy more licenses but I know this won't help, as my users will just keep banging their icon until it maxes again (besides which, once Sesame has settled in as an invisible service with no application running, clients are unable to connect until the Server is rebooted, so it doesn't matter if the licenses are maxed out or not.)