IBDAC: Unreachable connection in Schema modeler

I’m using latest RODA (Server Edition) for Delphi with Delphi XE 3 and IBDAC Driver 4.5.9, connection to Firebird 2.0.6 on local machine. RODA-IBDAC-Driver is installed.

After updating to the latest RODA version (coming from RODA 7) I have trouble with my firebird connection. The Schema Modeler reports an “Unreachable connection” and no metadata is shown in the connection manager of the schema modeler.

My connection string looks like this:
IBDAC?Server=localhost;Database=c:\daten\firebird\tcs_3_5_5.fdb;UserID=tcsadmin;Password=tcsadmin;role=standard;dialect=3;charset=iso8859_1

The Database is on my local machine and is up and running.

I tried to generate a new connection, but in the driver combo box only four drivers are shown: AbsoluteDB, ADO, ANYDAC and BDE - no IBDAC connection.

What is going wrong here? This is a show stopper at the moment.

Can you check that DAIBDACDrv.dad is present in …\RemObjects Software\Data Abstract (Common)\Bin folder?

if you reinstall RemObjects Data Abstract for Delphi, Server Edition - 8.1.87.1145.exe, this file will appear in folder?

Yes, this file was in bin-Folder. I uninstalled and installed RODA 8 Server .1145, but now it was a totally mess: no bpl-files where generated in folder dcu/d17/win32 and I got a huge amount of errors when starting Delphi XE3. No error message was shown during RODA-Installation.

What to do now?

can you review %da%\log.html ? it should contain some hints what was wrong.

by other hand, you can attach it here or send to support@

It works now - I do not know why, but it works.

What I did: Deinstalled everything from RO, also deleting any folder I found mentioned RO. Restarted computer. Installed RODA 8 Server (install time was much longer than in previous install), gave user full access rights on RemObjects folder in programm files (x86), installed IBDAC-Driver in RODA - and now it works. Connection works in Schema Modeler and IBDAC shows up as an option in Connection builder. So far, so good.

I don’t know the reason for the malfunction before, but it works now. Thanks for your attention.