Subject Re: Unavailable database after installing on Windows 2003
Author dobedani
Dear Paul,

Thanks for taking the time to reply. I admit that I am new to Windows
2003 and also to using Remote Desktop Connection. The server with
Windows 2003 is actually a remote machine unreachable for common
mortals :-(

With regard to Remote Desktop Connection: until now VNC was standard
here but our system administrators changed this. I questioned one of
them whether it could be a Windows 2003 issue and then he came up
with this commandline:
C:\> mstsc -console

When I then logged on to the remote server with Window 2003,
everything worked perfectly. So: sorry to have worried you with my

Kind regards,

--- In, Paul Reeves <paul@f...>
> On Wednesday 25 August 2004 14:42, dobedani wrote:
> > I installed the same Firebird version there into dir
> > C:\Program Files\Firebird\, with Administrator rights. What I do
> > afterwards was this:
> >
> > C:\Program Files\Firebird\bin>gsec -user sysdba -password
> > unavailable database
> > unable to open database
> >
> > C:\Program Files\Firebird\bin>
> >
> > Other ways to connect - e.g. with isql also result in:
> > Statement failed, SQLCODE = -904
> > unavailable database
> >
> > What am I doing wrong??? I understand that Firebird 1.5.1 can
work on
> > Windows 2003 Server, isn't it? Please help!!! TIA
> >
> I just verified that my system was clean (no uninstalled debris
> around) and did a fresh default install of 1.5.1 on Win2k3. It
> entirely as expected.
> I don't know what you are doing wrong, but I suspect that if a
> click through install doesn't work for you then the answer will lie
> the way you have configured Win2K3.
> FWIW, my test was on a basic installation of Win2k3 with no
> apart from specifying an ip address and a dns server.
> Paul
> --
> Paul Reeves
> Supporting users of Firebird and InterBase