At 04:31 PM 17/02/2009, you wrote:

>Any idea if the new installed software plunders the FB used TCPIP port(s) ?

Is this a new question? or a theory about why fbEmbedded stopped working?

If the latter, the TCP/IP port is irrelevant for embedded.

>----- Original Message -----
>From: "eddressel" <eddressel@...>
>To: <firebird-support@yahoogroups.com>
>Sent: Monday, February 16, 2009 8:18 PM
>Subject: [firebird-support] unavailable database
>
>
>> D2007, FB 1.5 embedded, IBO 4.8.6
>>
>> (I posted this in the IBO ng but have not heard anything and this is a
>> good client of mine so I did not want to wait).
>>
>> I have a customer that cannot connect to a FB database when the
>> application start-up. The database is there, the gds32.dll is there--I
>> just can't get it to connect to the database.
>>
>> The IBO Monitor gives me this message (from FB, I believe):
>>
>> //*******************
>> FB Log Msg from TIB_Monitor = '/*---
>> INTERPRET BUFFER = unavailable database
>> ERRCODE = -1
>> ----*/'
>> //*******************
>>
>> just before raising the exception.
>>
>> In talking with the user (I logged into his machine) he uninstalled
>> his video conferencing software just before he saw the problem--but I
>> need to know how to fix this, not just the cause of the problem.

My guess would be the uninstallation of the video conferencing software might have removed the MSVC runtimes (msvcr71.dll and msvcp71.dll for Fb 1.5, AFAIR) from system dir if it was responsible for putting them there.

Another possibility is that your fbclient.dll (presumably a renamed fbembed.dll) has actually been playing as a client-only client all along, attaching to a Fb server that was installed by the video conf software. Maybe a reboot will do the trick and the app will load the embedded server.

./hb