Subject Re: [firebird-support] ERROR!NONE OF THE DYNAMIC LIBRARIES CAN BE FOUND: FBCLIENT20.DLL, FBCLIENT.DLL REFdn6005800544
Author Helen Borrie
At 10:47 PM 10/08/2009, you wrote:

>I have a problem with a new installation on a specific new pc with windows
>xp home edition version 2002 no SPs!

Before proceeding, you should apply all the SPs.


>FB version 2.0.3.12981.
>
>The installation both of FB and of Application are done pretty well!
>
>The Problem: The Application trying to be connected with FB returns the
>follow error message:
>
>ERROR!NONE OF THE DYNAMIC LIBRARIES CAN BE FOUND: FBCLIENT20.DLL,
>FBCLIENT.DLL.
>
>The specific file not found by the system (or something like that).

There is no "FBCLIENT20.DLL" so goodness knows why it is being reported.

The most likely cause of DLL errors is that the Microsoft run-times are missing or too old. The files are mscvr71.dll and mscvp71.dll. You should be able to find them in the \bin\ directory of your Firebird installation. Copy them to \windows\system32.

>This error must came from Zeos database components.

The zeos component presumably is responsible for loading the Firebird client DLL.

>The installation has installed the files FBCLIENT.DLL & GDS32.DLL in
>c:\windows\system32.
>
>On other installation (other machine) I verified that these files are
>located on in c:\windows\system32 and not in the Application's
>folder/subfolder. The same is happening also on this "problematic" machine.

If you developed the application, surely you must know where your component will look for the client library, and by what name.

>The fact is that the same version of the FB and the same version of
>Application are working well on several machines, expect this one. Both
>versions of FB and of Application are old, they are working on other
>machines months now and I am thinking that the problem is restricted on FB
>installation or this version of FB have some incompatibility issues with
>this version of windows (I do first time installation on win xp home with no
>sps).
>
>Any suggestions?

At this stage, in this order:

1. Get the service packs aboard
2. Copy the MS runtimes across to system32.
N.B., also check that the ICU dlls are present in \bin\.
3. On following attempts to connect, copy down any error messages *exactly*.

./heLen