Hello NickUpson,
Just saw you response now after I resolved the matter. Thanks for your input, will give you the credit.
The problem was a DLL "gds32.dll" - the version was still Interbase 7.5 (left over "footprint"). Apparently, the Firebird installer detected this file and opted not to clobber over it, but when used, this version of the DLL would start referencing the prevous product installation paths. Firebird errors out due to dependencies it does not find. I copied over the Firebird version of this DLL to the server's "c:\winnt\system32\" path and the Firebird server behaved fine since.
Again thanks for your responses, I will try out that method the next time I face this problem again.
Main Topics
Browse All Topics





by: NickUpsonPosted on 2006-02-25 at 08:53:04ID: 16045818
first the name is firebird, not "firebird interbase",
second is that you may well need to update your version of ibexpert as well, Version 2005.09.22 came out about a month ago.
I haven't used this program for a while, I think you will need to re-register the database server as it is now firebird
also your theory may be correct that IB has left stuff that is interfearing. I would do the following:
remove/rename the folder c:\Program Files\Borland\Interbase
remove all references to interbase from the registry
uninstall firebird
reboot
install firebird (make sure you have the latest version, 1.5.3 was only recently released) server
install firebird client (part of same file but not installed unless you pick it)
reboot
try it now