Quote:Mark -
Bob Hansen was trying to help me with this problem and here is what we did.
1) First - he uploaded a copy of his program (in case the version of 1.1.3 HF 1 I was using was "corrupted").
That should rule out a problem with the copy of the program itself.
2) We opened the Sesame program using my short cut. (I was unable to open Server Administration)
He created a new shortcut and the same thing happened.
That should rule out a problem with the short cut itself - although perhaps this distinction provides a "clue".
3) Using Windows Explorer, we opened Sesame.
Starting Sesame this way, we were able to access Server Administration (which is how I was able to see the log info); however, I was in the C:\Sesame\Program directory and was unable to change it to C:\Sesame\Data (where my programs reside).
Double check the "Start In" setting on the icon's property dialog. Make sure that it is pointing to where your s_conf.cnf file actually resides. Look for additional sesame log files. Are they in the places you would expect?
In general, some setting or directory arrangement must have changed. Possibly a file permission? There are only two thing Sesame does at that juncture: it writes to the log file (check if that has permission) and it reads the licences file. If there is no log file, Sesame will make one. If there is no s_conf.cnf file, Sesame will assume a single user license and default the admin password. But if the log file exists, but for some unknown reason cannot be written to, or if the s_conf.cnf file has been corrupted (you wouldn't believe how many people try to open/edit either file in MSWord!), I suppose there might be trouble.
We have tested here with read only settings and with corrupted files, and have not been able to produce a lock up. But it is impossible to produce exactly identical corruption as might be found in the field
Ray has been investigating a similar sounding problem - on the forum under the thread "Help with Help". We have not been able to reproduce the problem here at all.
Quote:He did point out sunlock.exe (which I found in C:\Sesame\Utilities\Lantica); however, when I click on it to execute, I see a "flash" and nothing happens.
It is a command line utility and must be provided with the filename (and path) of the application file (.db) that you want to unlock. You cannot run it successfully from explorer - because explorer will not allow you to specify the application filename argument.
Quote:I hope this provides sufficient information to identify the cause of the problem.
Thanks!
GEE - IT'S GOOD TO BE "BACK"!
Its nice to have you back. We, here at Hammer, were all saddened to hear why you were taking a "leave of absence".