Possible conflict between version 2 and 3?

[sanoso...@gmail.com]

Hi,

I installed my application with firebird 3 on a computer that already has firebird 2 installed. When trying to establish an odbc connection to the database, the error "unavailable database" occurs. What can be the reason?

[Tomasz Tyrakowski]

Probably both servers try to bind to the local TCP port 3050 (that's the
default). If 2 has been installed earlier (and is up), it took the port
(so your app actually talks to 2, not 3). If you need both versions up
at the same time, you need to edit firebird.conf in one of them and
change (IIRC) RemoteServiceName and RemoteServicePort, but that would
also require corresponding changes on the client (app) side or in ODBC
data source config (I'm not an ODBC expert, can't tell exactly how you
set the server port number in the DS config).

regards
Tomasz

________________________________


Ta wiadomość zawiera poufne informacje przeznaczone tylko dla adresata. Jeżeli nie jesteście Państwo jej adresatem, bądź otrzymaliście ją przez pomyłkę, prosimy o powiadomienie o tym nadawcy oraz trwałe jej usunięcie.

[Thomas Steinmaurer]

> On 14.09.2021 at 08:11, sanoso...@gmail.com wrote:
>> I installed my application with firebird 3 on a computer that already
>> has
>> firebird 2 installed. When trying to establish an odbc connection to the
>> database, the error "unavailable database" occurs. What can be the
>> reason?
>
> Probably both servers try to bind to the local TCP port 3050 (that's the
> default). If 2 has been installed earlier (and is up), it took the port
> (so your app actually talks to 2, not 3). If you need both versions up
> at the same time, you need to edit firebird.conf in one of them and
> change (IIRC) RemoteServiceName and RemoteServicePort, but that would
> also require corresponding changes on the client (app) side or in ODBC
> data source config (I'm not an ODBC expert, can't tell exactly how you
> set the server port number in the DS config).

The port is typically part of connection URL then, e.g.:

localhost/4050:<path_or_db_alias>

Another reason could be that the ODBC driver picks up the wrong Firebird
client library, e.g. FB2 client library connecting to a Firebird 3 server.


--
With regards,
Thomas Steinmaurer
http://www.upscene.com/

Professional Tools and Services for Firebird
FB TraceManager, IB LogManager, Database Health Check, Tuning etc.

[sanoso...@gmail.com]

I solved the problem. You must enter the local path to the firebird client library in the field [Client] of the DSN settings.