Windows 10: ODBC Registry settings are not reflected in UI - ODBC Database administrator32-bit

I am using Windows Server 2019 version 1809 OS Build 17763.1158. I want to enable encryption for ODBC DSN connection So I am calling this command "C:\Windows\SysWOW64\odbcconf.exe /A {CONFIGSYSDSN "ODBC Driver 17 for SQL Server" "DSN=MVFServer=%SDX_DBSERVER%Encrypt=yesTrustServerCertificate=yes"}" from the script file .bat file. Registry settings are updated properly under "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ODBC\ODBC.INI\MYDatasource" but when I launch ODBC Database administrator32-bit and selected my data source and clicked on configure -> Next -> Next->Next c

:)

 

Suspect configuration of ODBC


I suspect that something is not correct concerning the configuration of ODBC. The Control Panel shows the two entries for this software as it should for a 64 bit system and when you drill down to General under Properties it shows the correct shortcuts for both versions, i.e. system 32 for the 64 bit and SySwow64 for the 32 bit.

When you open up both versions to look at the Administrators, the data appears to be identical for both in some cases. User DSN, System DSN (empty), File DSN, Tracing and About appear to be the same in both. However, in User Data Sources both sets of files are flagged as 32 bit platform and in About all the ODBC Core Components for both versions are pointing to system32 location which is the 64 bit.

For the Drivers tab the 32 bit version is fully populated including SQL Server, most having a version no. of 10.00.1493.00. For the 64 bit version the only entry is SQL Server with the same version.

The same goes for Connection Pooling. The 32 bit version is populated including a SQL Server whereas the 64 bit version only has SQL Server.

Reading various posts online I would expect the 32 bit version to refer to syswow64 files and the 64 bit be populated with the system32 ones if they were there, which they are not.

I also have found the following-:
https://blogs.msdn.microsoft.com/dat...-odbcad32-exe/
Towards the bottom of the first paragraph it says that on a 64 bit system the 64 bit drivers are held at a certain registry location. The registry has the full path but under ODBC Drivers there is only the one entry for the SQLServer which bears out what the Drivers tab is saying above. The 32 bit drivers are there, again confirming the Drivers tab. In the screenshot it shows a typical 64bit system for 64 bit drivers, that data is not in mine.

Below the screenshot it talks about certain registry keys be set to value not set. On my system under 64 bit system and 64 bit drivers, items 1 and 2 are as I have them. For the 32 bit drivers items 1 and 2 again are as per post. However, in both locations ODBCINST.INI and ODBC the 32 bit drivers are fully populated.

To me the 32 bit drivers are in the right place in the registry but not when you look in the Administrators. As for the 64 bit drivers, they appear not to be in the registry nor in the Administrator.

Incidentally, the SQLServer for both versions in the ODBC registry, point to system 32.

This system is an upgrade from Windows 7. Am I wrong in my assumptions or I have missed something, guidance appreciated. If I am correct, how does one resolve this?

 

ODBC connection to oracle database in SSIS

Following error occurs while creating ODBC connection to Oracle database 12c in SSIS





i have created ODBC DSN which itself is connecting to database. When using the same DSN in visual studio 2012 for ODBC connection to Oracle Database 12c. The error occurs.

Following are the resources used:

1.ssdt - VisualStudio(2012 shell integrated) x86

2. Oracle database 12c

3. ORACLE DRIVER (SQORA32.dll)

4. WINDOWS 7 (64bit)

 

Access ODBC connection stopped working

Starting Monday, Feb 10, the ODBC connection on all my access databases stopped working. I cannot connect to the ODBC database, and Access keeps trying to open a second instance of the OSBC data, even though the source is open, the driver works, and the
Windows 10 ODBC manager is set to use the open database. The datbase is QuickBooks 2017 and the driver is QODBC, just updated to current. Is anyone else experiencing this? Does anybody have a solution?