Subject Re: [firebird-support] Re: GSEC WONT RUN
Author Helen Borrie
At 06:56 PM 25/09/2004 +0000, you wrote:
>Thomas and Helen:
>Thanks for the reply. I also had to change the installation
>directory because it did not recognize the "Program Files" directory.

For the record, this would have worked:

gsec -database "localhost:c:\program
files\firebird\firebird_1_5\security.fdb" -user sysdba -password masterkey

>It seems to be working now but I have another problem. Now it´s
>telling me this:
>C:\Firebird\Firebird_1_5\bin>gsec -database
>ecurity.fdb -user sysdba -password masterkey
>Your user name and password are not defined. Ask your database
>administrator to
>set up a Firebird login.
>unable to open database

Perhaps you inadvertently changed the password or deleted sysdba....if so,
then you are in a catch-22. You have a backup of security.fdb
(security.fbk) but no owner to restore it.

When you moved the installation directory, did you just file-copy things,
or did you reinstall? If the former, then there are more things to do,
that are not documented in the Quickstart Guide. And the uninstaller won't
work, either. The installation of a service and the way the server finds
things are a very complicated piece of knitting. Keep reading....

As a reality check, move on in the guide to the section where you test
connecting to the employee database using isql. The Windows example on
P.12 refers to Superserver. Remember that, with Classic, you always need
the server (localhost if you are connecting locally) in the connection
syntax. So, assuming that you actually *installed* Classic in its
non-default location (as opposed to *copied it*), try this from your bin

isql localhost:c:\firebird\firebird_1_5\examples\employee.fdb -user sysdba
-password masterkey

If you've still got the same problem, then you probably have broken the
security database. For your convenience and delight, I've uploaded a
pristine security.fdb to the Files area of the list. You can access the
file at the URL:

To make use of it, boot up your machine in safe mode (F8 when prompted
during the Win2K load). Once Windows is running, make a file-copy of your
existing security.fdb, then unzip this one directly over the top of the
existing one. Reboot the machine normally and start over.

This time, keep in mind that all local access with Classic on Windows
(except with gstat...another story....) must be with the full TCP/IP local
loopback server syntax. And we clearly have some additions to do the
Quickstart Guide regarding Classic on Windows.