At 07:36 PM 21/02/2005 +0000, you wrote:

>I just installed Firebird 1.5.2 (in SuperServer mode) on a Windows
>2003 server (where I have ICF enabled). It appeared to install
>correctly. Immediately after the install process was finished I
>attempted to change the SYSDBA password with
>
>gsec â€"user SYSDBA â€"pa masterkey â€"modify SYSDBA
>â€"pw <new password>

Actually, you need the parameters in the right order:

gsec -modify sysdba -pw collywob -user sysdba -password masterkey

>I got an "unavailable database, unable to open database" error.
>
>I also intalled the FBconfigmanager and when I attempted to run it I
>got the message - "Firebird Server is not installed on your computer."

Don't use FBConfigManager - AFAIK, it was never updated for the final
release of Fb 1.5 and supports only some earlier betas, before the Registry
key was properly sorted out. Use Notepad. It's more useful, because
firebird.conf contains some useful documentation.

>I went to the Services dialog and "Firebird Guardian" and "Firebird
>Server - Default Instance" are both listed as started. I restarted
>them just in case.

Of course, you must stop and restart the server to have firebird.conf
settings take effect.

>I also installed EMS IBManager and registered the example EMPLOYEE.FDB
>database. When I attempted to connect to it I got - "unsuccesful
>execution caused by an unavailable resource. Unavailable database"
>
>I'm currently using the ICF Firewall and I haven't done anything
>regarding its configuration.

Port 3050 must be open. I don't know anything about ICF but, if it has a
port scanner, check to see what (if anything) is happening on port 3050.
You should also open another port if your applications use events, and bind
to it using the RemoteAuxPort parameter in firebird.conf.

Also check in your ..\firebird_1_5\bin directory, to see whether you are
running Classic (fb_inet_server.exe) or Superserver (fbserver.exe).

>If I'm just using Firebird on the server
>and not accessing it through the internet (at least not yet) then I
>was assuming that I wouldn't need to do anything with ICF.

Firebird is client/server software, designed for network use. On Windows
you have three choices: TCP/IP, Named Pipes or IPServer ("local
connect"). Forget Named Pipes (too noisy) and IPServer (flaky; not
recommended for anything except the single-user Embedded version of SS; not
available for Classic at all).

>Can anyone help me with this? What am I overlooking?

Can't tell. The first reality check is to find out whether you installed
Classic or Superserver.

The next is to ensure that you are not trying to connect to a share.

The next is to find out whether TCP/IP is working.

Make a ..\system32\drivers\etc\Hosts entry for the server (use the server's
actual node name, NEVER a mapping; or just make up a name; and the IP
address that the server is broadcasting to the network):

nnn.nnn.nnn.nnn MyServer

Make sure Localhost is there too:

127.0.0.1 localhost

When that's done, go to a command window and type

ping localhost

If that doesn't get a response, then TCP/IP is not configured for the local
network.

If it does, then go to Firebird's bin directory and try this:

isql "localhost:c:\Program
Files\Firebird\Firebird_1_5\examples\employee.fdb" -user sysdba -password
masterkey

(Note the double quotes, needed because of spaces in the path).

If you see this, then you are in business:

SQL>

Also make sure that tools like IBExpert have a copy of the client library
fbclient.dll, renamed to gds32.dll, located in the windows\system32 directory.

Do you have the Quick Start Guide, from the Novices section of the Firebird
website? Once you've sorted out the firewall, get that and Simon's how-to
beside you, and walk through the steps.

./heLen