Michael,

> I have a testserver currently running both Firebird 2.1 and 2.5.
> I need this to support and test various situations with different firebird
> versions.
>
> Now I would like to install Firebird 3.0 manually as well, so I can have 2.1,
> 2.5 and 3.0 on the same server.
> 2.1 listens on port 3050, 2.5 listens on 3060 and I have set 3.0 to listen on
> 3070.
>
> So far so good.
> I then executed the install_service.bat Firebird_3_0
> I can now see its running in process manager.
>
> But I'm having problems connecting to the server.
> Using Database Workbench to create a server entry I instantly get
>
> connection rejected by remote interface
>
> Sinse security is handled quite differently in Firebird 3.0 I suspect I am
> missing something here.
>
> Could someone either give me a step-by-step instructions to install Firebird
> 3.0 manually or point me to places where I can read some about it.
>
>
> On a difference machine I did run the installer, and I did get Firebird 3.0 up
> and running. But I need it on this server alongside the other firebird
> installations

For test purposes I tend to use Firebird 32-bit, because most/all of my client applications are 32-bit, thus I can easily point the client application to the targeted 32-bit fbclient.dll.

Step-by-step:

* Extract the FB 3 ZIP distribution
* Change the tcp port to 3070 in firebird.conf
* The security database is not initialized when installing from ZIP, thus we need a few additional steps
- We need an embedded connection with Firebird 3, thus stop ALL Firebird processes including 2.1, 2.5 etc.
- Go to FB 3 install directory, and type:

isql -u user sysdba employee

In isql:

create user sysdba password 'yoursecretpwd';
commit;
exit;

Your security database has now 1 user SYSDBA with the new SRP security/authentication in place

* Being still in FB 3 install directory, now install the FB 3 service (adapt service name properly. I tend to include the version, port and bitness in the service name):

install_service.bat Firebird_300_3070_x86

* Start all other Firebird processes (2.1, 2.5 etc.) again

* The new SRP authentication makes the usage of the 3.0 fbclient.dll mandatory! I guess in your case, DBW was simply using an older FB client library. So, in Database Workbench, upon server registration, explicitely provide the path to 32-bit fbclient.dll of Firebird 3.


You could also run the Firebird 3.0 server in some sort of legacy authentication mode where you can use an older fbclient.dll, but personally, for test purposes, I would like to try out the new stuff. ;-)

Hope this helps.




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

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

>
> Thank you
> Michael
>