Hello Bob,
You will have an e-mail with the document in just a few minutes.
Quote:After Sesame Server goes away, I start it again, and get message about ports not connecting.
How soon afterwards do you try to restart it? Depending on the OS and setup, the computer may take a few seconds or maybe a few minutes to release the ports after Sesame closes them. I know that there are a few versions of Linux that take roughly 5-10 minutes to release the ports.
Quote:So it sounds like I am seeing a Client connection being dropped across the network somehow?
That is what this sounds like unless the application is first being loaded by an X command.
Quote:That is why Sesame Server still shows DB file in use? But I also see that the count is down to 0 of 2.
Seat count is different then reference count. Reference count is internal and can not be seen. It is the number of people in a given application at a time. Seat Count is how many people are on the entire Sesame Server. The 0 of 2 is the Seat Count.
Quote:If I try to reconcile now, I get message that file is in use, this is due to Sesame Server status. So I must need to close the Sesame Server vs unlocking the DB file. Then restart it, and then Reconcile.
Yes shutdown the server using Server Admin. Do not unlock the file. Too many people have got in the habit of unlocking far more often then they need to, which leaves the file open to another Sesame Process, which is bad.
Quote:What can be causing a phantom Sesame Server?
Not sure if you even have a phantom server. It could just be the OS taking a few second to release the ports.
Quote:Can the Client disconnect be causing this?
Once again it depends on what you actually have. Whether it be a phantom server or a port's not being release problem has yet to be seen.
Quote:If that is the case, then maybe I only have one problem, the Client workstation disconnecting from the Sesame Server. And if that is happening why does the count go down but the file stays locked?
The file stays locked because the Server believes it to still be in use. The Seat count which is the number of connections is completely separate from the reference count. Seat count is per server. Reference count is per Application. So the file stays loaded into memory as the files reference count is greater than 0.
I can not stress this enough. You should never ever ever have to unlock an application in order to reconcile to it. If you get an error when reconciling that the application is being served, the first thing you should do is figure out who is using it. You should not immediately unlock it. Unlocking a file allows two separate Sesame Processes to access the same file at the same time which can have catastrophic results.
Here is some more info in addition to the document that I sent you from Bill earlier.
Unlocking is a very serious process that should not be taken lightly. It should only ever need to be done after a power outage or computer failure. When you need to unlock a file, unlock only that one file, not every file that is listed.
Reconciling is another very serious process. Reconcile makes permanent changes to your DB file and when combined with unlock the results can be disastrous. To properly reconcile follow these steps
First create a Backup using Sesame.
Open the Application you are going to be reconciling.
Expand the Application Utilities Folder
Click Backup Application
Save the file under a new name
At this point you can also open your backup to be sure that it is a good backup.
Second shut down the Sesame Server so no one can access the files while you are reconciling.
From a client Click File->Server Administration
The first tab has the options for shutting down the server
This is how you properly shut down the Sesame Server. You should never click Emergency Shutdown except in the case of an actual emergency.
Once the Server is shut down then you can reconcile. Once you are done reconciling, start the Sesame Server back up and connect a client. Open the file you just reconciled and verify that everything is functioning properly.
-Ray