Subject RE: [firebird-support] Re: Cannot open database file in local hard disk
Author Neil Pickles
Post date 2018-02-20T17:04:49Z

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?

 

Cheers,

 

Neil Pickles

 

From: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com]
Sent: 20 February 2018 14:05
To: firebird-support@yahoogroups.com
Subject: [firebird-support] Re: Cannot open database file in local hard disk

 

 

Just a little correction to my message. Where I wrote firebird.conf, I should have written aliases.conf.

 

-------- Mensaje original --------
Asunto: Cannot open database file in local hard disk
De: Eduardo <gusedum@...>
A: firebird-support@yahoogroups.com
Fecha: 20/02/2018 10:57

Hello:

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

Eduardo

 

 

Libre de virus. www.avast.com