I'm trying to install the Firebird ODBC driver (linked to from http://www.firebirdsql.org) within an Advanced Installer 6.4.1 installer.
Here are the relevant logs:
MSI (s) (A4:EC) [10:10:53:796]: Executing op: ActionStart(Name=InstallODBC,Description=Installing ODBC components,)
Action 10:10:53: InstallODBC. Installing ODBC components
MSI (s) (A4:EC) [10:10:53:796]: Executing op: ODBCInstallDriver(DriverKey=Firebird driver,Component={9DE763EA-B3CB-46FC-8518-DF686F369C6A},Folder=C:\WINDOWS\system32\,Attribute_=Driver,Value_=OdbcFb32.dll)
1: Firebird driver 2: {9DE763EA-B3CB-46FC-8518-DF686F369C6A} 3: C:\WINDOWS\system32\ 4: Driver 5: OdbcFb32.dll 6: Setup 7: OdbcFb32.dll 8: APILevel 9: 1 10: ConnectFunctions 11: YYY 12: DriverODBCVer 13: 03.51 14: FileExtns 15: *.fdb,*.gdb 16: FileUsage 17: 0 18: SQLLevel 19: 1
MSI (s) (A4:EC) [10:10:53:827]: LocalSQLInstallDriverEx returned 1 in local context.
MSI (s) (A4:EC) [10:10:53:843]: LocalSQLConfigDriver returned 1 in local context.
MSI (s) (A4:EC) [10:10:53:843]: Executing op: ODBCDataSource(DriverKey=Firebird driver,,Registration=4,Attribute_=DSN,Value_=dbname)
1: Firebird driver 2: 3: 4 4: DSN 5: dbname 6: Description 7: dbname 8: QuotedIdentifier 9: Y 10: Dbname 11: C:\Program Files\lala\dbname.FDB 12: SensitiveIdentifier 13: N 14: ReadOnly 15: N 16: AutoQuotedIdentifier 17: N 18: NoWait 19: N 20: Dialect 21: 3 22: CharacterSet 23: NONE 24: JdbcDriver 25: IscDbc
MSI (s) (A4:EC) [10:10:53:843]: LocalSQLConfigDataSource returned 0 in local context.
MSI (s) (A4:EC) [10:10:53:858]: LocalSQLConfigDataSource returned 0 in local context.
MSI (s) (A4:EC) [10:10:53:858]: LocalSQLInstallerError returned 0 in local context.
On the screen appears the following error:
"Error configuring ODBC data source: dbname, ODBC error 7: Invalid driver name. Verify that the file dbname exists and that you can access it."
I've verified that both the ODBC driver file, c:\windows\system32\odbcfb32.dll exists and can be accessed, as well as the C:\program files\lala\dbname.FDB file. I've also verified that the registry entries at the stage where this message box appears match exactly that of the ODBC driver if it's installed through its own setup executable, yet even trying to add a data source using this ODBC driver from the control panel fails with an "invalid driver name" error.
If I install the ODBC driver through its supplied setup executable, and point the data source in Advanced Installer to that driver, instead of the one I'm trying to install, the setup of the data source works fine.
I've tried all sorts of workarounds and searched all over to find an answer to this problem, but nothing seems to work. Do you guys have any ideas?
FOLLOW US
Get the latest news in Application Packaging