Firebird Documentation IndexFirebird 3.0.2 Release NotesCompatibility Issues → Local Connections to Superserver on Windows
Firebird Home Firebird Home Prev: Upgrading a v.2.x Security DatabaseFirebird Documentation IndexUp: Compatibility IssuesNext: Configuration Parameters

Local Connections to Superserver on Windows

In previous Firebird versions, a serverless protocol known as “Windows Local” was available to local clients connecting to Superserver on a Windows platform, using the XNET subsystem. A typical connection string looked like this:

  c:\Program Files\Firebird_2_5\examples\empbuild\employee.fdb
        

Under the new unified server, that form of connection is no longer valid for a serverless client connection to Superserver. It attempts to load an embedded server. If you try whilst Superserver is connected to your database, you will get a refusal message to the effect “File is in use by another process”.

This is not a bug. Since Superserver clients share resources, another server (in this case, an embedded server) cannot attach a client to the same database that Superserver has any clients attached to.

However, all is not lost. The XNET subsystem can still do local client sessions for Superserver. You just need a more elaborate connection string now:

  xnet://alias-or-path-to-database
        

So, for our connection to the employee database:

  xnet://c:\Program Files\Firebird_3_0\examples\empbuild\employee.fdb
          

or using an alias:

  xnet://employee
        

Note

New connection strings are available as alternatives for other local connection protocols, too. For more information, see New Connection Formats for Local Clients on Windows.

Prev: Upgrading a v.2.x Security DatabaseFirebird Documentation IndexUp: Compatibility IssuesNext: Configuration Parameters
Firebird Documentation IndexFirebird 3.0.2 Release NotesCompatibility Issues → Local Connections to Superserver on Windows