Subject Re: [firebird-support] ISC ERROR CODE:335544375 unavailable database
Author Ivan Prenosil
> I've had to reinstall Firebird because I forgot
> the sysdba password.

Next time just replace security database file with fresh one (from installation).


> Now when I try to use ib_sql or
> IBQuery I get the above error message "ISC ERROR CODE:335544375
> unavailable database" (yes the database definitely exists, I browsed

The message"unavailable database" does not mean that database file can' be found,
but that database server does not run.


> Oh - also noticed that when I tried "SELECT * FROM RDB$RELATIONS" in
> isql it came back blank.

If you are not connected into database, isql does not report any error
when you try to execute any statement ! If you try to execute
"SELEXT * FROG RDB$RELAMPIONS"
isql will come back blank too, no error message!


Ivan


----- Original Message -----
From: "james_t_mcneill" <james_t_mcneill@...>
To: <firebird-support@yahoogroups.com>
Sent: Wednesday, August 31, 2005 9:58 PM
Subject: [firebird-support] ISC ERROR CODE:335544375 unavailable database


> Sorry to be a pain. I've had to reinstall Firebird because I forgot
> the sysdba password. Guardian says it's version 1.5.2.4731, on
> Windows XP Home Edition 2002 SP 2. Now when I try to use ib_sql or
> IBQuery I get the above error message "ISC ERROR CODE:335544375
> unavailable database" (yes the database definitely exists, I browsed
> to get the path). Using Superserver. I deleted the firebird folder
> before the reinstall, and took all standard options.
>
> I used GSEC to change the sysdba password, then created a database,
> but I just cannot connect to it using either of ib_sql or ibquery,
> although both worked before the reinstall. Following a hint in
> another posting I tried replacing gds32.dll with gds32_previous.dll
> in the same folder.
>
> Oh - also noticed that when I tried "SELECT * FROM RDB$RELATIONS" in
> isql it came back blank.
>
> Obviously I'm doing something dumb. Anyone care to put me out of my
> misery?
>
> Thanks,
> Jim