Took me hours to find a figure out a fix for this so sharing in case it helps someone else!
Summary:
If you're using Windows 11 ARM (via Parallels) and get Error 193 when adding a 64-bit ODBC DSN, this guide walks you through creating a 32-bit DSN (Data Source Name), then converting it for 64-bit use. (For reference, I used this to create a DSN to SAP Business One on HANA which I then use in Excel's Power Query)
Steps:
Summary:
If you're using Windows 11 ARM (via Parallels) and get Error 193 when adding a 64-bit ODBC DSN, this guide walks you through creating a 32-bit DSN (Data Source Name), then converting it for 64-bit use. (For reference, I used this to create a DSN to SAP Business One on HANA which I then use in Excel's Power Query)
Steps:
- Install the 32 and 64-bit ODBC drivers you need (SQL Server, HDBODBC, etc.)
- Open the 32-bit ODBC Administrator
- Run: C:\Windows\SysWOW64\odbcad32.exe
- Create your DSN using your installed driver.
- Export the 32-bit DSN from the Registry
- Open regedit
- Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ODBC\ODBC.INI\<YourDSN>
- Right-click the folder, choose Export, and save it as a .reg file.
- Edit the .reg file for 64-bit
- Open the .reg file in Notepad.
- Replace: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ODBC\ODBC.INI\YourDSN
with:HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\YourDSN - Save the file.
- Import the modified .reg file
- In Registry Editor, go to File > Import, and select the edited .reg file.
- Map the DSN to its driver
- Go to: HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources
- Right-click on ODBC Data Sources and choose > New > String Value
- Name: YourDSN (whatever you named your connection in step 2b)
- Value: Your driver name (e.g. HDBODBC, SQL Server, etc.)
- Verify in 64-bit ODBC Admin
- Run: C:\Windows\System32\odbcad32.exe
- Your DSN should now be visible and usable in 64-bit applications like Excel or Power BI
- HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\<YourDSN>
- HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources
