Earlier today my boss was trying to open Sesame, and nothing started up.  After clicking the icon several times the program finally opened.  I learned of this when I tried to get into Sesame myself, and was bounced out because there were too many users.  I checked the server admin and saw that his machine had 4 clients open.

I went to his system and shut down the open Sesame window, then opened Task Manager.  Sesame did not appear on the open app list, but Sesame.exe was listed 3 times on the services list.  I shut down each service with Task Manager and tested his system, and of course had no problem opening Sesame.  I've told him to alert me if it happens again, where he clicks on the startup icon and the program doesn't start.

Any idea what could cause this to happen, and advice on how to prevent it in the future?

It happened again today, with two more users, one of them being myself:  Click on Sesame icon, nothing happens, no interface, nothing in the taskbar or tray, nothing.  Open up Task Manager, no application on the list, but sesame.exe is running in services.  Sesame Server sees the workstation as connected, but the user is unable to interface the program at all.

Shut down all services, rebooted the machines.  Same situation.

Removed the -client switch from the startup icon, and Sesame starts up sweet as you please, but of course unable to connect to the server's apps.

So I kicked everybody off, shut down Sesame Server, ran the batch file which runs Sunlock on all my apps and starts up Sesame Server, and we're back in business, so far so good.

Something funky going on with Sesame Server, it seems, but I have no idea what.

Quote:

Will do.  This sounds like a possibility; network traffic has been heavy here today.

Quote:

I haven't seen that yet but will watch for it and I'll wait it out and see what happens if if it happens to me again.  If and when it happens to someone else here it's always a matter of life or death that it be fixed immediately.  I should bring a squirt gun in to shoot these folks, cool 'em down.

Thanks for your help Erika.

proudpoppy wrote on Oct 8^th, 2007 at 1:27pm:

Can you give us steps to duplicate it, so we can try to make it happen here?

Its now in that mode, click until your heart is content and no interface. I will be happy to let tech support do a remote session if needed to the machine that its happening on.

To create this problem I did  the following.

In client/Server mode::

First M/C is the server/client, server and client running application open.

On the client m/c open the application.

Then on the client m/c go to file and then exit.

The client m/c will freeze up.

Go to the Server/Client M/C and the client will be froze.

Ctl-Alt-Del

Then click Sesame client icon, no interface will appear, but it will be in processes.

No interface until server is shutdown, restarted and application unlocked.

FYI: We're looking into this. We got on Robert's system yesterday while it was happening, so we do have some information and are working on tracking this down.

Quote:

No sir, nor am I running 2.0.3 yet.

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.)

Infinity wrote on Nov 1^st, 2007 at 1:14pm:

Scott,

It can take a bit for the OS to release the ports. If you try to restart the server before the OS actually finishes releasing the ports, you can get this message.

 Is there a way to program Sesame so that if a user already has an instance
of it running some kind of message can appear to tell him so if he tries to start a
second (or third, or fourth) instance? Or is there any other way to enable only one
 instance of Sesame.exe to run on a client?


No.    

Yes, you could create a batch file to start Sesame and put controls in there to send a message if Sesame is already running on the local machine.

Hello Bob!
This Utility is very meaningful, programed practically and excellently.
You even have this personally for my purposes and compile with a German layout!
BRAVO!
MERCI!
THANKS and  thanks again Bob!

That is to be simply recommended.

Dr. Belhareth

Thanks for the bump of the topic guys.  I've been meaning to check back in about this because the problem occurred again last week, but I've been too busy with non-Sesame stuff to visit here much, and our app has been running perfectly otherwise.

I just downloaded your utility this morning, Bob, and it's just swell.  As for customization, I would prefer that it start Sesame silently if no other instances of it are running, otherwise the error message would come up.  And the error message would need to be tweaked as I am reluctant to call my users dummies.    Let me know what would be involved with fine-tuning that.

Thanks Bob, this is great!

Quote:

Thanks.  I'm in and out, mostly out.  Wish I had more time to read the boards.
Quote:

Ping!

Thanks again, Bob.

Thanks Bob.  Unfortunately, our firewall chumped it as dangerous.  Probably an .exe, right?  The firewall chumps .exe's in email.  Can you zip it or change the extension and resend?  Thanks!

Sorry Bob, it's just not getting through.  Let's see...you could send it to Infinity@captaininfinity.us or maybe upload it to your website and send me the link to download?  Sorry to put you through so much trouble.

Got it!  Thanks.  Will test and let you know.  Future comments will go to email, unless it's something other Sesame users can use.  Thanks again, Bob!