At 11:11 PM 4/02/2005 +0000, you wrote:

>--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
>wrote:
> > Get the Quick Start Guide from the Firebird website.
>
>oops _ actually I did that the first time, I just failed to mention
>it.
> >
> > To get things cleaned up, begin by shutting down any running server
>by
> > going to the command line and typing NET STOP
> > FirebirdGuardianDefaultInstance. If it doesn't find that service,
>then do
> > NET STOP FirebirdServerDefaultInstance.
> >
>
>this is the most interesting of your comments. Does this mean that
>shutting down the machine DOES NOT STOP Firebird correctly? Does
>this mean that using STOP in the Services panel DOES NOT STOP
>Firebird correctly? Does this mean I need to create a bat file to do
>the NET STOP and have it run whenever I need to shut down the server
>for any maintenance?

Grrr...no, in a proper installation, the Administrator should be able to
stop the services. But I think there is a level of uncertainty what you
have installed there.

> > Next time around, with the Quick Start Guide to hand, run the
>installer. I suggest taking all the defaults.
> >
> > Make sure that, during the installation, you make an informed
> > choice about which server model you are going to install. The
> > installer gives you the choice of Classic and Superserver.
>
>Superserver is what I have been selecting (I believe) all along.

OK.

> > If you need a client named gds32.dll and it has to be in the machines
> system32 directory, then make sure those two options are checked.
>
>I missed this the first time, but that just made the ODBC driver
>crazy. It wasn't causing the unavailable database error.

To make sure you have the right client, you should check the version string
in the property editor of the library that your driver is accessing. If it
doesn't match the version string of fbserver.exe (in the build number at
least) then there's a good chance it belongs to something else. Do I need
to say that remote clients should access the database from the correct
client library version as well?

> > Don't check off Use
> > Guardian unless you know how to configure services to restart
>automatically.
> >
>in the services panel, right? or -- in light of the NET STOP
>requirement -- does Firebird not work with standard windows services?

Bleh!! Firebird *is* a Windows service - it's not a question of "working
with". NET STOP will stop any service that can be stopped; NET START will
start (or restart) any that can be started.

> > Once the installation finishes, the service(s) -- Guardian and
>Server -- will be up and running. It won't hurt to run the Services
>applet to double-check.
> >
>the services (according to the Windows panel -- have come up every
>time. It's getting to the databases that doesn't work.

OK, if the services are running then that's cool. If you know how to check,
and you know that you might need to, then that's enough.

Since it's unclear (from another message) whether it was the MACHINE or the
SOFTWARE that was moved, it's kinda like crystal ball gazing to try to
identify your problem. For example, if you moved *the software* you could
well be looking at a firewall problem....if it was just the machine that
was moved, not the software, and connection worked before...then does the
machine still have the same node address? What's the environment - is
there a terminal server in the picture?

>I will follow your directions -- if I understand you correctly, I
>should follow the Quick Start Guide rather than the Release notes
>installation Notes.

They aren't inconsistent with one another; but neither anticipates every
possible physical error in the environment or deals with the 1001 problems
of improper installations; nor assumes anything about how your firewalls
and network are set up.

./heLen