Hi,

At October 19, 2005, 2:34 AM, Adam wrote:

> I am a bit puzzled on this one.

> Windows 2003 Server
> Firebird 1.5

> I don't seem to be able to make a local connection. There is no other
> user connected to this database, I have just renamed it to prove that.

> isql c:\test.fdb -u sysdba -p masterke
> Returns the following error:
> Statement failed, SQLCODE = -904

> unavailable database

> Just to prove I am not going nuts

> isql localhost:c:\test.fdb -u sysdba -p masterke
> connects without any problem

> I have confirmed this behaviour across two different win2003 machines,
> however it works perfectly on XP SP2. I have full control access to
> the file from both my own account and also the Firebird user.

> Any thoughts on what could cause this?

None. I just can say that my customers using Windows 2003 are seeing
the same behavior. They can only create a backup using the TCP/IP
protocol. I'm just wondering if it's not a default security setting
that is causing this. I haven't had the time to thoroughly research
it, and I'm not sure when I'll really have the time.

--
Best regards,
Daniel Rail
Senior Software Developer
ACCRA Consultants Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)