A desktop technician is deploying a legacy 32-bit database software package on a workstation running a 64-bit edition of Windows 11 Pro. The application requires a custom Data Source Name (DSN) to establish a database connection. The technician launches the standard ODBC Data Sources administrative tool from the Administrative Tools menu and configures a System DSN, but the 32-bit application fails to recognize or connect to the data source. Which of the following actions should the technician take to resolve the issue?
- Launch the 32-bit ODBC Data Source Administrator utility located in the SysWOW64 folder and configure the DSN there.Answer
- BUpgrade the workstation to Windows 11 Enterprise to unlock native 32-bit database driver compatibility features.
- COpen Component Services and configure a DCOM proxy interface for the 32-bit database connection.
- DAccess Indexing Options in Control Panel and add the database driver path to the indexed locations list.
Answer
Launch the 32-bit ODBC Data Source Administrator utility located in the SysWOW64 folder and configure the DSN there.
On 64-bit versions of Windows, 32-bit and 64-bit applications use different registries and driver subsystems. The default ODBC shortcut in Administrative Tools points to the 64-bit tool (in System32). Creating a DSN there makes it visible only to 64-bit applications. To support a 32-bit application, the technician must execute the 32-bit ODBC Data Source Administrator tool located at C:\Windows\SysWOW64\odbcad32.exe.
Step-by-Step Solution
Key Concept
ODBC Data Sources (32-bit vs 64-bit) Architecture in Windows