Hello Bob,

Did you have to unlock the DB in order to reconcile to it? Never ever ever unlock an application in order to reconcile to it. It is one of the fastest ways you can get your self in a bad spot.

Quote:

This means that the ports are in use by another Sesame Server. The exact message says "Error: Failed to create a local socket: unknown".

Quote:

No need to unlock the file if you shut the Sesame Server down properly. You should only EVER need to unlock an application if the Server Computer went down suddenly as if from a power outage. Under normal operation unlock should never be used. It's use is to tell the file that Sesame no longer has it open, and the only time you should have to do that is if the Server went down suddenly.


Quote:
No the file is not bad.

If a DB file is loaded by an X command into memory on the Server, or if a DB is used for Extractor(with the open flag) or ODBC, the DB will remain loaded into the Sesame server when the command finishes. This is to allow the next command to be faster. Now you can also get an application to stay loaded into memory on the server if you have a ghost client or a Sesame client suddenly dropped connection. The Server will release the seat under circumstances where it can determine that the client is truly gone but it will not lower the reference count in the DB file. This means that even if no clients are connected that DB file still has a reference count of 1 which keeps it loaded on the Sesame Server.

I think Bill passed out a document at the User's Conference about how to properly Reconcile an Application on the Network. If you need a copy let me know and I will see if I can find it for you.

-Ray

Hello Bob,

You will have an e-mail with the document in just a few minutes.

Quote:

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:

That is what this sounds like unless the application is first being loaded by an X command.

Quote:

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:

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:

Not sure if you even have a phantom server. It could just be the OS taking a few second to release the ports.

Quote:

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:

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