Subject Re: [firebird-support] Local Connection Unavailable under W2K3?
Author Helen Borrie
At 09:31 PM 25/01/2005 +0000, you wrote:

>I have added the ability to use a local connection type, which
>provides a 10-15% performance improvement (Firebird resides on the
>same machine) in my testing on a Windows XP SP1 machine. When we
>configure our production servers (W2K3 Server) to use a local database
>connection method, it comes back with the following error:
>'Unavailable database'

IPServer local connection only works with Superserver. Check whether you
are running'll need to use local loopback if so.

>The Firebird server resides on the same machine as does the database.
>Any ideas?
>The CreateWindowInternal should be the default installation setting,
>so I don't believe this is the problem. It uses XNET now anyway right?

No. In Firebird2, XNET replaces the IPServer but in 1.5.x you still have
these limitations.

Also don't overlook the possibility that you're trying to connect before
the OS has actually started the Firebird service.