Subject | Re: [firebird-support] Re: unavaliable database |
---|---|
Author | Uwe Grauer |
Post date | 2005-02-11T19:20:58Z |
Helen Borrie wrote:
when is there realy a need to use local protocol?
I never got into these traps as i never do anything else than tcp/ip.
Thanks,
Uwe
> At 01:10 PM 11/02/2005 +0000, you wrote:Helen,
> > > >
> > > > I've just installed Firebird 1.5.2 in a windowns environement
> > > > (Windows XP SP2 and Windows 2003). I have the problem in both
> > > > installations.
> > > >
> > > > When I try to connect to the database from a remote pc (with
> > > > IBexpert or our own application) everything is fine, but when I
> try to
> > > > do any of the following comands from the local server (isql, gsec,
> >gbak)
> > > > I get always the same error message : unavailable database.
> > > >
> >C:\Archivos de programa\Firebird\bin>isql -user sysdba -password
> ><mypassword>
> >Use CONNECT or CREATE DATABASE to specify a database
> >SQL> connect 'c:\temp\scg2.ibp';
> >Statement failed, SQLCODE = -904
> >unavailable database
> >
> >I get the same error whatever database file I try.
> >
> > > What about connecting with IBExpert from the local machine?
> >
> >There is something strange with it. If I register a database as remote
> >specifying my IP it works allright, but if I register my database as
> >local specifying only the path to the database file it doesn't works.
>
> Which model of Firebird did you install - Superserver or Classic? Check
> the name of the executable in Firebird's bin directory - Classic is
> fb_inet_server.exe, while SS is fbserver.exe.
>
> The IPServer local protocol isn't available to connect to Classic...
>
> ./heLen
when is there realy a need to use local protocol?
I never got into these traps as i never do anything else than tcp/ip.
Thanks,
Uwe