|Subject||Re: "Firebird/interbase client dll is not installed" error|
The computer I'm working on had a totally clean install of WinXp. There were no client dlls installed. It should be using the client on the server from a mapped drive. In fact, based on the results of the process monitor program, it does find the gds32.dll. This setup works for almost all of our client computers. The server is 64bit Win2008 and 64bit Interbase XE is installed on it. I'm now wondering if some hardward or OS issue is preventing the 32bit client computer from accessing the presumedly 64bit client dll on the server. The problem with that is that the majority of our client computers are 32bit and they are accessed the server client with no problems.
--- In IBObjects@yahoogroups.com, "IBO Support List" <supportlist@...> wrote:
> It is not locating the library DLL file.
> I recommend that you do a thorough scan of the machines for all DLL files
> associated with InterBase/Firebird and look at your path setup, etc.
> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com] On Behalf
> Of staniwalker
> Sent: 09 November 2012 01:25 PM
> To: IBObjects@yahoogroups.com
> Subject: [IBO] Re: "Firebird/interbase client dll is not installed" error
> --- In IBObjects@yahoogroups.com, "staniwalker" <staniwalker@> wrote:
> > This error we get on about 4 of 45 computers (WinXP and Win7). We have
> Interbase XE (upd 4) installed on a Win2008 R2 server. The client software
> (gds32.dll) is installed in the same directory as our application program,
> also on that server. The client computers are mapped to the server so that
> they all run the same application and same gds32.dll.
> > The computers that get this error are all XP. Most XP computers work, only
> a few don't. A process monitor utility program shows that the failing
> computers have found gds32.dll on the server like they are supposed to. I'm
> running XP, and have no problems. We just did a clean WinXP install on a
> computer with all the updates and it still gets the error (it also had the
> error before the clean install). The failing computers were working with
> Interbase 7.5 and the client version for that interbase installed locally,
> but after we converted to IB XE with the client on the server, the failures
> happened. It seems to be some hardware issue related to the new client that
> IBObjects doesn't like. Even with the client file local, the error still
> > We are using IBO 4.8.7 with Delphi 2007. The actual error is apparently in
> the ib_session.pas file in the HandleException procedure:
> > if not Assigned( isc_interprete ) then
> > raise EIB_Error.Create( E_IB_Client_Not_Installed );
> > What is causing this error? What doesn't IBObjects like? Why is it only
> happening on a few computers?
> > Thanks for any help,
> > Stan Walker
> Can't you give me any idea what to look for? What condition is triggering
> this error to happen on a few computers?
> IB Objects - direct, complete, custom connectivity to Firebird or InterBase
> without the need for BDE, ODBC or any other layer.
> http://www.ibobjects.com - your IBO community resource for Tech Info papers,
> keyword-searchable FAQ, community code contributions and more !
> Yahoo! Groups Links