Helen Borrie wrote:

>> I was doing all my testing on the
>> server, even in the bin directory. ISQL really tried to connect to
>> the employee.fdb sample database, but got the error, "the machine
>> actively refused the connection." That tells me it's more than just
>> a misplaced .DLL.
>
> Nevertheless, it's the message you get when you try to connect to a
> Fb 1.5 with a mismatched client.
>
> If you've checked the version strings on your DLLs and executables
> and have eliminated the possibility that the tools are finding the
> wrong client or server, then there's a configuration problem
> *somewhere*. It would be
> worth looking around the system for things like a bad Registry entry,
> wrong ISC_USER and ISC_PASSWORD settings, database in a directory
> that the
> DBAccess setting doesn't recognise, etc.
>
> You didn't say whether you used the Win installer or the zip kit for
> the install. If the latter, the possibility of a wrong install would
> be extremely high. It's not possible to install Fb 1.5 "over the top"
> of an old 1.0.x or IB installation without a very solid understanding of
> the Fb 1.5 setup.

I used the Win installer and installed it in a new directory (default). There
are no ISC_ environment variables defined. I had left everything at defaults
and had only one database I was using--extremely simple and default setup.
Also, I had uninstalled 1.0.3 (and rebooted) before installing 1.5.

So, here's what I've done now: Uninstalled completely and removed left-over
files. Reinstalled 1.5 and tested first with ISQL. It worked! (*finally*)

OK--so it looks like the problem may have been the left-over gds32.dll in the
system32 directory. That is one thing I noticed after your last message I
hadn't thought of checking before--figured the uninstall of 1.0.3 on a server
would've taken care of that.

Thanks for the heads up on checking for .DLLs--the error messages I was
receiving gave me no clue whatsoever.


Regards,

David.