I had a similar problem on Windows 2003 Server today. I
got "Unavailable database" for just about everything I tried. I
happened onto this thread and tried adding localhost: anywhere I
specified a path and it did indeed work.

So...WHY??? What problem am I actually working around? This is the
only machine I've ever had to do this on.

-Jeff

--- In firebird-support@yahoogroups.com, Thomas Steinmaurer
<ts@i...> wrote:

> Paul,
>
> > I was talking a client through installing FB1.5 Classic. When

he tried to

> > log into GSEC with SYSDBA masterkey he got the

message 'Unavailable

> > database'. This was in WIN2000 in a command prompt in the

FB 'bin'

> > directory. He then reinstalled FB in SS mode and it worked

OK.

> >
> >
> >
> > Is there some problem with command line tools and CS, or are we

doing it

> > wrong?
>
> You need to specify the security database explicitly via a TCP/IP
> connection. For example:
>
> gsec -database localhost:c:\...\security.fdb ....
>
>
>
> --
> HTH,
> Thomas Steinmaurer
> LogManager Series - Logging/Auditing Suites supporting
> InterBase, Firebird, Advantage Database, MS SQL Server and
> NexusDB V2 (NEW!)
> Upscene Productions
> http://www.upscene.com