FORUM NOTE: if using AyaNova version 4 or higher, do note that the configuration file is called config.txt not AyaNova.exe.config Other than that, the same steps above would apply if you receive this error.
When configuring AyaNova version 3 for network Firebird use, if you receive the message “Unavailable database” or “unable to open database” at the command prompt when running GSEC (to edit the default SYSDBA password) and/or when running GBAK (snapshot for backup purposes), perform the following:
Just as you were logged in when you installed Firebird, make sure you are logged in as the computer/network administrator with full access while physically at the computer (not via remote). Try again
Open Control Panel -> Firebird Manager. Make sure Firebird is running. Try again
Open Services and make sure both the Firebird Guardian Service and the Firebird Service are running. Try again
Confirm that your aliases.conf file is correctly edited to point to the AyaNova database
Reboot the computer, log in as computer/network administrator with full access. Open Services and make sure both the Firebird Guardian Service and the Firebird Service are running. Open Control Panel -> Firebird Manager. Make sure Firebird is running. Try again.
If you continue to receive the message “Unavailable database”, make sure no one is accessing AyaNova (all AyaNova products shut down) and un-install Firebird. Reboot and perform the steps to install Firebird again.
Do not perform any installation via remote - Firebird developers have stated this is known to affect the registry entries resulting in what you see.
If you continue to experience the same error, send the following to firstname.lastname@example.org:
Confirmation if you are or are not able to run the AyaNova program itself
If so, select menu Help -> About AyaNova -> copy all text to a Notepad document, save and attach to your email
Attach a copy of your AyaNova.exe.config file if using AyaNova 3, else your config.txt if using AyaNova 4
Attach a copy of your ayalog.txt
Zip up a copy of your edited networkFirebirdsnapshot.bat using WinZip and attach to your email
Attach a copy of the aliases.conf file from the Firebird Server
If the AyaNova database is not located on the same hard drive as where Firebird is installed, identify if it is an external harddrive, anotehr computer’s harddrive, etc
Confirmation of the each of the above having been performed - identify each in your email specifically and the result
Provide specifically what you are doing that results in “database unavailable” or “unavailable database” - be precise.
Provide the full text of any message
Identify if you can log into AyaNova, or if the issue is just with backing up the database, or with changing the Firebird Server username and password