Share via

ETA for supporting 64-bit ODBC drivers on Windows 11 IoT (ARM) LTSC (24H2)

Anonymous
2024-09-12T09:52:27+00:00

I've already put a week effort in researching this topic and could not find any useful hints on the web so far.

Starting point:

  • Host: Mac OS on Apple Silicon (M3)
  • Virtualization: Parallels Desktop (latest update)
  • Windows 11 IoT LTSC (24H2) - all available updates installed.
  • Oracle Instant Client with ODBC - both x64 and x86 variants.
  • Microsoft Visual C++ Redistributable: 2013 (both x64/x86), 2015-2022 (both x64/x86), 2022 (Arm64)

Tests

Test scenario #1 - ODBC Admin

  1. ODBC Data Source Administrator (64-bit) - started from ‪C:\Windows\System32\odbcad32.exe
  2. User DSN > Add... > Oracle in instance21c_x64
  3. Getting the following error message: The setup routines for the Oracle in instance21c_x64 ODBC driver could not be loaded due to system error code 193: .

NOK

Test scenario #2 - Access

  1. Create new DB in Access
  2. Add new data source (SQL Server) > Link to the data source by creating a linked table.
  3. Machine Data Source
  4. Choose "Oracle in instant21c_x64" (this choice could be also a full client installation with ODBC, in that case it's named "Oracle in OraClient21Home1")
  5. Finish.
  6. Oracle ODBC Driver Connect dialog pops up > fill out and OK.
  7. The data tables in the DB gets listed and can be linked and queried.

OK

Test scenario #3 - IIS - ASP.NET w/Oracle.DataAccess

  1. Create an ASP.NET Application with Oracle.DataAccess (x64) which connects to the DB.
  2. Deploy it to the local IIS
  3. Boot up fails.

NOK

Hint: in order to enforce the usage of 64-bit architecture I created a symlink in the C:\Windows\System32 for the instant client, so the Path env. var. looks contains this: C:\Windows\System32\instant21c_x64

Further hint: https://learn.microsoft.com/en-us/windows/arm/apps-on-arm-x86-emulation - this article describes, that x64 emulation for drivers cannot work at the moment, that's the reason for my initial question: when we can expect it to come.

Note that emulation only supports user mode code and does not support drivers; any kernel mode components must be compiled as Arm64.

Windows for home | Windows 11 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2024-10-14T15:48:58+00:00

    @miklos: I used the workaround as described in ODBC 64 bit error 193 - Microsoft Q&A To summarize the workaround: configure with the 32-bits version first and then copy over the registry setting to the 64-bits version.

    @microsoft: please fix this asap because it seems that the ODBC 64-bits administrator app is the real issue over here.

    0 comments No comments
  2. Anonymous
    2024-09-15T20:11:49+00:00

    Hi Brian,

    thanks for your quick reply!

    Unfortunately, there is a misunderstanding: the "Test scenario #1 - ODBC Admin" is a Windows bug:

    • look at on the "Test scenario #2 - Access": this opens the right ODBC Admin panel and the Oracle ODBC x64 driver works like a charm.
    • even if I open the right ODBC Data Source Administrator (64-bit) (C:\Windows\System32\odbcad32.exe), I did not get the right x64 ODBC Admin panel.
    • So there is discrepancy between opening the ODBC Admin panel from Microsoft Access and from the system files or the Start Menu.

    >>> I hope I can solve your problem, but unfortunately, this forum is for ordinary Microsoft users to help them solve some problems in computer use. <<<

    Furthermore, if you do a research on the internet, there are plenty of forum topics with users who cannot test the ODBC driver (x64) by the ODBC Admin panel, so this is not just a bug on a virtualized Windows 11 IoT, but this bug occurs also on a bare-metal installation.

    I managed to solve the issue with the "Test scenario #3 - IIS - ASP.NET w/Oracle.DataAccess": this was a configuration issue indeed.

    Summary: the bug in "Test scenario #1" is still an issue: the user cannot open an ODBC x64 Admin panel from the start menu or diretly opening the exe file.

    I'm looking forward to your response!

    Regards,

    Miki

    0 comments No comments
  3. Anonymous
    2024-09-13T09:41:32+00:00

    Hello, Miklos Moricz

    Welcome to the Microsoft Community

    Thanks for your feedback. I read the information you provided.

    We understand your current dilemma and it is indeed very frustrating.

    According to the problem you described, your problem occurs in Windows 11 IoT LTSC virtualized by Parallels Desktop for Mac OS.

    I hope I can solve your problem, but unfortunately, this forum is for ordinary Microsoft users to help them solve some problems in computer use. I hope I can solve your problem, but your problem is beyond the scope of the forum. I suggest that professional users like you can submit your problem to Parallels technical support staff, who will provide more professional and effective help. You can contact them by clicking the link below.

    Support Resources & Contact Info | Parallels

    Disclaimer: Microsoft does not provide any implied or other guarantees and/or warranties and is not responsible for the information you obtain from third-party linked websites or any technology-related support.

    We hope that your problem can be properly resolved. Thank you for your understanding.

    Best regards

    Brian - Microsoft Community Support Specialist

    0 comments No comments