We have an application that requires that a firebird odbc system DSN be set up. This has always functioned well in 32-bit Windows Server environments.
For the first time we tried to set the same app up on a 64-bit Server 2008. We have tried both the 32-bit and 64 bit Firebird ODBC drivers but both fail to connect with the error message 'Open Database c:\program files\appointments\appoint
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Actually the database is located in c:\db ... as a standalone file. And it doesn't seem to matter where we locate it - the ODBC connection simply fails to open the gdb.
Firebird itself is 32 bit and running fine as a service on the server - we know it is running OK because other applications are able to interact with it.
Thanks,
Jerry
Since I do not know what is running behind the scenes with Firebird, I only can recommend using filemon resp. procmon (www.sysinternals.com, free), with filter set to the gdb file name, to get information about why the file cannot be opened.
Settings>Control Panel>ODBC>System DNS Tab>Add
DataSourceName=SMSReminder
Driver=IscDbc
Description=SMSReminders
Database=D:\Program Files (x86)\SpectraSoft\Appointm
Database Account=SYSDBA
Password=masterkey
[No other fields changed from defaults]
On clicking 'Test Connection' error message is produced: "Open database 'D:\program files (x86)\SpectraSoft\Appointm
This happens irrespective of the lcoaiton of the gdb file.
FIrebird is running correctly and the appointmentspro.gdb file can be accessed correctly by e.g. IBConsole
When you tried the 32-bit version, did you use odbcad32.exe to create the ODBC data source?
Which version of the drivers are you using for the 64-bit access?
http://www.firebirdsql.org
In each case (32-bit / 64 bit)I did not click directly on an executable - I went to the Control Panel > Administrative Tools > Data Sources (ODBC).
After the 64-bit driver failed to work I uninstalled it and then installed the 32-bit driver which also failed to work. I have now re-installed the 64-bit driver in order to carry on trouble-shooting.
Yes, I am using the RC1 64-bit driver downloaded from the url above.
I meant, are you using odbcad32.exe?
This is a specific question that was not answered by your http:#25896414 description of the dialog.
New information: I attempted to use the 'Users' tab on the Firebird ODBC Service dialog. On clicking the 'Get Info' button, the following error message is produced:
Error produced within Firebird 64-bit ODBC Users dialog
The question not asked, but which proved critical, was whether the user application was a 32-bit 0r 64-bit app. As it turned out, because it was a 32-bit app, use of the 64-bit Firebird driver was inappropriate. This meant that the 32-bit driver had to be used, and thus Olemo's observation re the respective location of the relevant odbcad32.exe files was the key to unlocking this puzzle
Business Accounts
Answer for Membership
by: QlemoPosted on 2009-11-05 at 06:41:13ID: 25749882
I assume you have a problem with the file system virtualization feature. Is the database located in "Program Files" or "Program Files (x86)"?