At 12:36 PM 21/12/2004 +0000, you wrote:

>Hi Helen,
>
> >
> > The sequence of messages you provided showed that the restore
>completed, so
> > you *know* that the server was running up till then. Next, IBE
>made a
> > request that caused the server to crash.
>
>I agree.
>
> >
> > It makes me wonder whether you are running IBE with some old client
>library
> > that doesn't belong to Fb 1.5. Did you run the Win32 Fb 1.5 client-
>only
> > install on the machine where IBE is, and take the compatibility
>options?
> >
>
>Yes I did, furthermore, in IBE's database registration info, you can
>explicitly set Client library file, which I did, and I set it to
>fbclient.dll
>
>AFAIK, there's only one version of that file (fbclient.dll), correct ?

Use the version with the right build number for your server, though. In
theory, it shouldn't matter, but Fb 1.5 wasn't bug-free.

>I'm definitely willing to remove all FB/IB related stuff on my
>machine and reinstall FB 1.5 client-only install.

As a reality check, reboot the client machine, connect to the server over
on Red Hat, then go to fbclient.dll and try to rename it. If it is
actually loaded, you won't be able to.

>But as said, I
>thought that it was gds32.dll before FB 1.5 and fbclient.dll since FB
>1.5

Yes, that's right. But lots of legacy tools and apps need the
compatibility client install. You might be encountering a bug in IBE,
where it can't find fbclient.dll in its path, so defaults to an old
gds32.dll either in its own directory or in the system dir.

>Moreover, to exclude the possibility (because I did have IB 4.2,
>IB5.5, and FB 1.0 installed before) that IBE doesn't correctly use
>the client-library setting I'll start by removing all gds32.dll, and
>fbclient.dll stuff and do that reinstall anyhow.

Yup, but try the reality check first. It's quicker. :-)

cheers,
./heLen