A systems administrator is setting up a legacy 32-bit financial application on a 64-bit Windows 11 Pro workstation. The application requires a 32-bit System Open Database Connectivity (ODBC) driver to connect to a backend database server. However, when the administrator opens the default ODBC Data Sources applet from Administrative Tools, the installed 32-bit database driver does not appear in the drivers list. Which of the following administrative actions should the technician take to successfully configure the DSN?
- Launch the 32-bit ODBC Data Source Administrator executable located in the C:\Windows\SysWOW64 directory.Answer
- BOpen Component Services (dcomcnfg.exe) and add the database driver under the 32-bit COM+ Applications node.
- CUse System Configuration (msconfig.exe) to force Windows to run administrative management snap-ins in 32-bit emulation mode.
- DUpgrade the workstation operating system to Windows 11 Enterprise to unlock native 32-bit driver backward compatibility.
Answer
Launch the 32-bit ODBC Data Source Administrator executable located in the C:\Windows\SysWOW64 directory.
In 64-bit editions of Windows, the default administrative shortcut named 'ODBC Data Sources' launches the 64-bit version of the utility located in C:\Windows\System32\odbcad32.exe. The 64-bit utility can only see and manage 64-bit database drivers. To configure 32-bit drivers for legacy applications, administrators must manually launch the 32-bit utility executable, which is counterintuitively located in C:\Windows\SysWOW64\odbcad32.exe.
Step-by-Step Solution
Key Concept
Windows 32-bit vs. 64-bit ODBC Data Source Administrator paths (SysWOW64 vs. System32)