|Subject||Re: [firebird-support] Re: Cannot open database file in local hard disk|
In every computers I tried there is exactly
the same version of Firebird installed: 184.108.40.20693 32 bits.
The databases where generated with the same version of Firebird. And remember that if I use an alias, I can open the database. The problem is when I try to open it using the path of the database file C:\Test\... .FDB.
I can even generate the database in the same computer (using an alias) and then I cannot open it using the path of the database file.
Asunto: Re: [firebird-support] Re: Cannot open database file in local hard disk
De: 'Neil Pickles' neil.pickles@... [firebird-support] <firstname.lastname@example.org>
Fecha: 20/02/2018 14:04
You’re not switching between 32 bit and 64 bit versions of Firebird are you?
I’m not sure exactly when the change occurred but I remember similar issues trying to open a 32 bit generated database with a 64 bit version of Firebird or vice versa. It’s definitely okay with v2.5 but not sure about v2.1 as it’s been some time since I use v2.1 for anything.
When you open it successfully on another computer, is it the same bitness of Firebird, 32 bit or 64 bit?
Just a little correction to my message. Where I wrote firebird.conf, I should have written aliases.conf.
I use Firebird 2.1 and in some computers I cannot open a database file which is in the local hard disk.
For example, let's suppose I have the database C:\Test\MYDATABASE.FDB and I try to open it with IB_SQL (from IBObjects).
If I use C:\Test\MYDATABASE.FDB I get "unavailable database".
If I use SERVERNAME:C:\Test\MYDATABASE.FDB I get "unavailable database".
If I use \\SERVERNAME\C:\Test\MYDATABASE.FDB I get "unavailable database".
If I modify firebird.conf creating the alias MYDATABASE=C:\Test\MYDATABASE.FDB, then using MYDATABASE I can open the database.
In almost every computer with any Windows version (XP, 7, 10, 2003, 2008, 2012, 2016) I can open the database using every one of the four methods, but in some computers the first three methods return "unavailable database" and I can open the database only using an alias. Now I am having the problem in a computer with Windows Server 2008 R2 Standard with Service Pack 1, but I remember having this problem in other computers from time to time.
Any ideas of which may be the reason? ... and the solution?
Thanks in advance. Regards
Libre de virus. www.avast.com