No luck...

I did an uninstall/reinstall, using RC8 and the Windows installer. When I did the re-install, I installed to c:\firebird (not c:\firebird1.5). Everything in the registry looks OK to me, is there a specific key to check?

gsec still produces this:
C:\firebird\bin>gsec
unavailable database
unable to open database

I didn't have a firebird environment variable, so I tried the following, starting with a delibrately bad directory to verify the environment variable was picked up:

C:\firebird\bin>set FIREBIRD=c:\temp

C:\firebird\bin>gsec
unavailable database
can't format message 18:15 -- message file c:\temp\firebird.msg not found

C:\firebird\bin>set FIREBIRD=c:\firebird

C:\firebird\bin>gsec
unavailable database
unable to open database

the security.fdb file *is* there, as shown below:
11/10/2003 01:05a 2,560 security.fbk
12/29/2003 01:05a 643,072 security.fdb

-----Original Message-----
From: Helen Borrie [mailto:helebor@...]
Sent: Tuesday, January 13, 2004 4:25 PM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] gsec - unavailable database


At 10:36 AM 13/01/2004 -0500, you wrote:

>Hello,
>
>When I try to run gsec, I get the "unavailable database" message, see
>example below. Evidently firebird can't find the security.fdb file. When I
>specify the database on the command line, gsec works. I also can't connect
>using ISQL - I get the same message.
>
>I am running 1.5 RC8 on Windows 2000 Server SP3. I have this working on
>another (Windows XP) machine, so I am stumped.
>
>Thanks in advance for any help.
>
>
>
>C:\firebird1.5\bin>gsec -user sysdba -password masterkey unavailable
>database unable to open database

Should work if you have the correct version of gsec. Have you checked that?

If gsec version is correct, inspect your FIREBIRD environment variable and
make sure it is pointing at the Fb root directory (absolute path, server
name not part of string). Same check on the Registry entry.

-- Thought it was worth a mention because you have a non-default root
path. If you ran the install with the defaults and moved stuff *after*
inst*.exe scripts were run, your root directory will have been mislaid.

If you simply copied the files from the "good" machine, you won't have a
complete install.

>C:\firebird1.5\bin>
>C:\firebird1.5\bin>
>C:\firebird1.5\bin>gsec -database endure2:\firebird1.5\security.fdb
>-user
>sysdba
> -password masterkey
>GSEC> quit

Yup, this works because you used the -database switch (correctly) with a
remote path string.

This combination of conditions strongly suggests a messed-up
install. Everything is there but your environment hasn't been installed
properly. If you discover mismatches, try running instreg.exe. Of course,
you *must* run the correct version of instreg.

/heLen




Yahoo! Groups Links

To visit your group on the web, go to: http://groups.yahoo.com/group/firebird-support/

To unsubscribe from this group, send an email to: firebird-support-unsubscribe@yahoogroups.com

Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/