| Subject | Local Connection Unavailable under W2K3? |
|---|---|
| Author | Larry Hengen |
| Post date | 2005-01-25T21:31Z |
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'
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?
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'
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?