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.