Subject Odp: [firebird-support] Re: Firebird 2.52 gbak f ails to do a restore - error trigger (3)

Look into firebird.log about errors and into windows events. First check port number and check if Interbase is not running and block Firebird port.
Remember that Firebird 3 is in beta stege, and is not for production db

Karol Bieniaszewski

----- Reply message -----
Od: "Jack Mason jackmason@... [firebird-support]" <>
Do: <>
Temat: [firebird-support] Re: Firebird 2.52 gbak fails to do a restore - error trigger (3)
Data: śr., cze 24, 2015 23:57


Yes, thank you very much.  I believe you correctly identified the problem.

 It turns out we did not have FIrebird running on our Win7 machine, we just thought we did.  Even though we were running Firebird gbak on the Win7 machine, it appears gbak was going out through the network and coming back in to the machine using TCP and connecting via the Interbase server.  I believe that because after I shut down the Interbase server, gbak would no longer even start to restore the backup file.

So, then I checked to see why the Firebird server was not running.  It appeared to start and then died.  The guardian died as well.  Something was not well.  Instead of trouble shooting 2.5.2, I downloaded 3.0 to have the latest. 

I uninstalled 2.5.2 using the Win7 Control Panel and then installed 64 bit 3.0.  Everything seemed to go correctly using the install_super batch file.  However, neither the server nor the guardian would start correctly.  That was last evening. 

I will be out of the office for about a week and when I return I will try to figure out why FIrebird will not start on my Win7 machine.  The only thing unusual about it is that it runs on a solid state drive. 

I am hoping that when I finally get the Firebird server to run on the Win7 machine it will restore the databases correctly from the backup files.  We do have Firebird running on an XP machine (I will check that) and the application that uses the database is still working correctly.

We are using Delphi 7 for the applications, Database Workbench 4 for a support tool, and Firebird as the database engine on almost all machines except for one, which is still on Interbase. 

Again, thank you for your suggestion.  I believe it will be the solution to our problem.  We only need the Interbase server running on the Win7 machine when we are working on improving or correcting the applications still on Interbase.


On 6/24/2015 11:38 AM, hvlad@... [firebird-support] wrote:

---In, <jackmason@...> wrote :

> Thanks.  We do have both Interbase and Firebird running on our Win7 machine because we have to access > both types of databases.  I will try your suggestion.

  Any news on this issue ?