[QODBC Desktop] QODBC: Resolving DSN Architecture Mismatch Errors (32-Bit vs 64-Bit)

Problem Description:

Applications connecting to QODBC via a System DSN may report an "architecture mismatch" error — the application and the ODBC driver must be the same bitness (both 32-bit or both 64-bit). A 32-bit application cannot connect to a 64-bit DSN, and a 64-bit application cannot connect to a 32-bit DSN.

Affected products: QODBC Desktop (any version), any ODBC-aware application (Excel, MS Access, C#, Python, SQL Server, etc.)
Expected outcome: Align the bitness of your application with the correct ODBC Administrator tool to create or select a matching DSN.

Symptoms:

• Error message: "The specified DSN contains an architecture mismatch between driver and application."
• Connection succeeds in the QODBC Test Tool but fails in the customer's application.
• The QODBC About screen shows "read-only, License error" even though the license is active.
• Switching between a newly installed 64-bit driver and an older 32-bit DSN (or vice versa) triggers the mismatch.

Cause:

1. ODBC Administrator tools are bitness-specific. Windows provides two separate ODBC Administrators:
   • 32-bit (SysWOW64): C:\Windows\SysWOW64\odbcad32.exe — manages 32-bit System DSNs.
   • 64-bit (System32): C:\Windows\System32\odbcad32.exe — manages 64-bit System DSNs.
2. A DSN created in one tool is invisible to the other. If your application is 32-bit but you opened the 64-bit ODBC Administrator (or vice versa), the DSN shown may not match your application's architecture.
3. Upgrading QODBC can reset or change DSN bitness. Installing a newer QODBC version (e.g., v24) may install both 32-bit and 64-bit drivers, but existing DSNs may remain on the old bitness until rebuilt.

Environment:

Resolution:

1. Determine your application's bitness. Check whether the application connecting to QODBC is 32-bit or 64-bit. For Excel, open Task Manager — if excel.exe runs under Processes (not Details) as "Microsoft Excel" it may be either; check the installation path or use HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\... registry keys to confirm. For MS Access, check the Office installation bitness.
2. Open the matching ODBC Administrator.
   • For 32-bit applications: Run C:\Windows\SysWOW64\odbcad32.exe (this is mandatory — the Start Menu shortcut may open the wrong bitness).
   • For 64-bit applications: Run C:\Windows\System32\odbcad32.exe.
3. Verify or create the correct DSN. In the matched ODBC Administrator, go to the System DSN tab and confirm that a QODBC DSN exists matching your application's bitness. If it does not exist, click Add and select the appropriate QODBC driver.
4. Test the connection. Use the Test Connection button in the DSN configuration dialog or run your application to verify the mismatch is resolved.
5. Rebuild the optimizer (if applicable). After installing a new QODBC version, the default DSN may be reset. Rebuild the optimizer file:
   1. Delete existing optimizer files per How to remove the Optimizer file.
   2. Rebuild the optimizer per How to rebuild the optimizer file.

Example Scenarios:

Scenario 1 — Upgrading QODBC breaks an existing application connection:

A customer upgraded from QODBC v23 to v24. Their 32-bit MS Access application suddenly reported a DSN architecture mismatch because the new installer created a 64-bit default DSN. Opening C:\Windows\SysWOW64\odbcad32.exe, reconfiguring the existing DSN to use the 32-bit QODBC driver, and restarting Access resolved the issue.

Scenario 2 — QODBC Test Tool works, but Excel fails:

A customer confirmed connectivity via the QODBC Test Tool but Excel 64-bit reported a mismatch. The DSN was created on the 32-bit ODBC Administrator. The customer opened the 64-bit ODBC Administrator (System32\odbcad32.exe), verified the 64-bit DSN, and Excel connected successfully.

Additional Notes:

• Always use the correct ODBC Administrator for your application's bitness. This is the most common cause of architecture mismatch errors.
• After a QODBC version upgrade: The installer may reset default DSNs. Always verify bitness alignment after upgrading, and rebuild the optimizer file per the steps above.
• QuickBooks Desktop is 32-bit only. If you are connecting to QuickBooks Desktop directly (not via QRemote), your QuickBooks data source DSN should typically be 32-bit (SysWOW64\odbcad32.exe).
• For additional information, see the QODBC Architecture Mismatch troubleshooting article.

Related Articles:

Understanding 32-Bit vs 64-Bit ODBC Drivers on Windows QODBC Optimizer Rebuilding and Troubleshooting QODBC 64-Bit Driver and Excel Read/Write Connectivity Issues

Keywords: