[DUG] Firebird 2.0 on Windows Server 2003 64 bit

John Bird johnkbird at paradise.net.nz
Thu Apr 24 16:40:44 NZST 2008


Hi guys - hope someone can shed some light, as my head is hurting after a
daying trying lots of permutations!

I am investigating upgrading from Firebird 1.5 to V2.0, so running tests on
a clean server with no other Firebird stuff installed.

Installing Firebird Classic V2.0 on a vanilla Windows 2003 server 64 bit is
no problem, and can connect to the database locally using tools like EMS SQL
Manager which is installed locally on the server.

But no connections from other PC's are working, either from EMS SQL Manager
or BDE installed on the client PC

The task manager shows Firebird is listening on port 3050,
The error on connecting is

"error 335544375 wrong client DLL version or service not running"

Firebird V2 has a FBClient.DLL, I am fairly sure we are pointing at the
correct file.


I think the likely problems are one of:

1 - The network paths are not being interpreted in the connection strings -
maybe I need more absolute path names,
On the server the database is in D:\folder\Database.FDB which is shared, and
FBClient.DLL (for V2) has been copied to the same folder to make sure it is
visible.

I have tried paths like

	192.168.1.xx\D$\Folder\Database.FDB
	192.168.1.xx\Folder\Database.FDB
	\\192.168.1.xx\Folder\Database.FDB

All of which tools like EMS seem to accept fine, but I have heard of similar
problems where share names are not good enough

2 - The client machine connecting from has Firebird 1.5 installed for a
local test database and also configured to access other 1.5 Databases on the
network (on other servers), and I suspect the FBClient.DLL loaded for 1.5
conflicts somehow with the required V2 DLL of the same name.

3 - Possible that fact it is Server 2003 64 bit is the problem with
accepting remote connections - ie the 64/32 bit emulation has reached its
limits?

4 - BDE for Delphi Enterprise 5 will not install on the Server, "The image
file SETUP.EXE is valid, but is for a machine type other than the current
machine".  So I cannot load BDE also on the server and test the Delphi
program running locally.

5 - Also the EMS SQL Manager on the 2003 server cannot connect to any of the
V1.5 databases on other servers...which made us suspect networking issues.

Anyone have ideas on what to try next?

Has anyone tried such a migration before?

John




More information about the Delphi mailing list