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

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 M3Virtualization: Parallels Desktop latest updateWindows 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 Arm64TestsTest scenario #1 - ODBC AdminODBC Data Source Administrator 64-bit - started from ‪C:\Windows\System32\odbcad32.exeUser DSN > Add... > Oracle in instance21c_x6

:)

 

ODBC Driver 17 for SQL Server and 32-bit application in 64 bit OS

I have a 32-bit application running in 64-bit OS. The application is connecting to SQL Server data base using the DSN created with ODBC driver "SQL Server" (SQLSRV32.DLL, version 10.00). But I have one customer who enabled TLS1.2 in their windows environment which requires the upgrade of the ODBC driver to latest versions. When I created the DSN using the latest version of ODBC drivers (tried version 13, 17 and 18), the connectivity test is not successful.

I get different errors time to time. Some of the error messages are below



Microsoft ODBC Driver for SQL Server Version 14.00.2037



Running connectivity tests...



Attempting connection

[Microsoft][ODBC Driver 13 for SQL Server]Named Pipes Provider: Could not open a connection to SQL Server [2].

[Microsoft][ODBC Driver 13 for SQL Server]Login timeout expired

[Microsoft][ODBC Driver 13 for SQL Server]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.



TESTS FAILED!



It also a bit strange that the connection test works sometimes without any change. I think the basic issue is I'm creating a 32-bit DSN using "ODBC Data Source Administrator 32-bit" and using the ODBC driver 64 bit (which is what I can install in my 64-bit OS). If I use "ODBC Data Source Administrator 64-bit", everything works fine. But as my application is 32-bit I can't use this DSN.

Do I have any other option without migrating my application to 64-bit?

 

Is there a diffrence between Windows 64-bit OS and Windows 64-bit

Hello. I'm sorry but no. The ARM processor is used for mobile or low voltage applications. Is this a tablet? The Windows 10 32 bit is run through emulation. 64 bit Windows or applications are not supported at this time. See here:A closer look at Windows 10 S, Windows 10 on ARM and Windows 10 IoT

Should be either Intel or AMD 64 bit processors to run 64 bit Windows.

 

ODBC Data Sources (32-bit and 64-bit) seem to be the same

There are two applications under Windows Administrative Tools called ODBC Data Sources (32-bit) and ODBC Data Sources (64-bit). But their shortcuts both point to the same file: %windir%\syswow64\odbcad32.exe. I would expect the 64-bit file to have a name
like odbcad64.exe. Why is the same file used for both 32-bit and 64-bit?

BTW, Windows topics (selected below) should have an "Other" selection when the listed selections don't seem to fit the topic being questioned about.

***moved the thread to the nearest category by query.***