Use an ODBC driver that matches the application making the connection. This guide explains which driver and Windows ODBC Administrator to use, how to check a data source, and how to troubleshoot an architecture mismatch.
Which Driver Does VDM Need?
VDM version 10 and later require 64-bit ODBC drivers. A 32-bit driver cannot be used by these versions, even when it is installed on a 64-bit Windows computer.
Choose the driver based on the application’s architecture, not only the Windows version or the database server’s architecture. A 32-bit application needs a 32-bit driver; a 64-bit application needs a 64-bit driver. Microsoft confirms this requirement in Check ODBC Driver Installation and DSN Configuration.
Open the Correct ODBC Administrator
On 64-bit Windows, there are two ODBC Administrator tools. Both executables are named odbcad32.exe; the folder identifies their architecture.
| Application | Driver | ODBC Administrator Path |
|---|---|---|
| VDM version 10 or later, or another 64-bit application | 64-bit | %windir%\System32\odbcad32.exe |
| A 32-bit application | 32-bit | %windir%\SysWOW64\odbcad32.exe |
For VDM version 10 and later: Search Windows for ODBC Data Sources (64-bit), or press Windows + R, enter %windir%\System32\odbcad32.exe, and select OK.
%windir% refers to the Windows installation folder, usually C:\Windows. Despite its name, System32 contains the 64-bit tool on 64-bit Windows; SysWOW64 contains the 32-bit tool.
Check the Driver and Data Source
- Open the ODBC Administrator that matches your application.
- Select the Drivers tab and confirm the required database driver is listed.
- Open the appropriate DSN tab and locate the data source.
- If creating a new DSN, select Add, choose the matching driver, and enter the database settings supplied by your administrator.
- Run the driver’s connection test if available, then save the configuration.
- Select the DSN in the VDM connection workflow and test the connection from VDM.
Driver installation and configuration differ by database provider. Follow the provider’s instructions for server details, authentication, encryption, and any additional client files. Microsoft’s Managing Data Sources documentation describes the general DSN workflow.
User DSNs and System DSNs
A User DSN is associated with the current Windows user. A System DSN is configured for the computer. For scheduled jobs running under a different Windows account, use the DSN configuration required by that service and verify access from its execution environment.
Seeing a DSN does not prove it is compatible. User DSNs can appear in both ODBC Administrators even when their driver matches only one architecture. System DSNs are separated into 32-bit and 64-bit configurations. See Microsoft’s ODBC Administrator and DSN visibility explanation.
Creating a System DSN does not grant database permissions or access to files and network resources. Those still depend on the credentials and account used by the application or service.
Troubleshooting
| Symptom | What to Check |
|---|---|
| Driver is missing | Check the Drivers tab in the correct ODBC Administrator. Install the vendor-approved driver for the application’s architecture. |
| DSN is missing from VDM | Check the driver architecture, DSN type, Windows account, and computer where the DSN was created. |
| “Architecture mismatch” error | Confirm the application and driver match. Recreate the DSN with the correct driver if needed. |
| “Data source name not found” error | Check the DSN name, installed driver, architecture, and DSN availability to the account making the connection. |
| Works manually but fails in Scheduler | Check the driver and DSN on the Scheduler computer, the service account’s access, and the saved connection configuration. |
| Connection test fails | Check server availability, network access, credentials, and provider-specific requirements in addition to architecture. |
Related Articles
- How to Set Up the Universe ODBC Driver
- How to Create a Database Connection Profile in VDM
- How to Open a Database Connection in VDM
Need Help?
Contact your database provider or administrator for ODBC driver installation and configuration assistance; BridgeWorks does not provide support for that setup. For help using a configured connection in VDM, contact support@bridgeworksllc.com with your VDM version, driver name, DSN type, and error message. Do not include passwords.
Comments
0 comments
Please sign in to leave a comment.