Windows 10: ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture...

Hi ExpertsProblem Statement: IT team joined a standalone Windows 2019 Server Version 1809 to Azure AD and rebooted the server. But next day I started facing some issue with my application.Details: OS: Windows 2019 Server Version 1809 build - 17763.2803 64 BitApplication: Web Application hosted on IIS 10.Net framework: 4.8HANA ODBC Driver: 64 bitSQL Version: SQL Server 2016All the connection and set up was working perfectly fine until the reboot. Next day onwards getting this issue which has stopped running the table extracts from SAP HANA.Error Message: ERROR [IM014] [Microsoft][ODBC Driv

:)

 

New data source ODBC driver could not be loaded due to system error 126

Hello,

I have an error when i want to add User DSN in ODBC data administrator 32 bit after clicking the related driver..

"The setup routines for the CSI RBM 4.02 ODBC Driver ODBC Driver could not be loaded due to system error code 126: The specified module could not be found. (C:\Windows\system32\mt40odbc.dll)."

1. I have already installed the driver and already listed in drivers tab ODBC Data source administrator 32 bit (only in 32-bit).
   
2. The file specified above (C:\Windows\system32\mt40odbc.dll) is already EXIST.
   

I used windows 64-bit and the driver was 32 bit.

Gracias

 

Can't create System DSN (ODCB, Microsoft Access Driver)

I tried Microsoft Q&A, they were stumped.

I found this article which describes my problem exactly

https://support.microsoft.com/en-us/topic/7fe70bdd-35fe-8ecd-ae94-9007e4c10d11

1) Although my entry for the key "(Default) ha sa value (not set) I still experience this issue

2) I cannot delete the entry (yes even as administrator)

3) using method 2 to delete it via run dialogue does not work either. I mean, there's no error, but it doesn't help.

I can use odjbjt32 to create one for .mdb but that's no good, I absolutely need accdb.

With that said, if I create DSN for mdb they are located here in here

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ODBC\ODBC.INI

and the list of all dsn are here

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ODBC\ODBC.INI\ODBC Data Sources

If I create a dsn per my original post using the ACE driver, the only instance I can find of my dsn in registry is in a very different location.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Wow6432Node\ODBC\ODBC.INI\mydsn

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources

At this point I'm thinking that I'm going to have to fresh install an old build of windows, like 1809 or something because I don't know when this broke but I know for certain it used to work no problems.

 

File DSN are slow to scan when opening ODBC Data Source Administrator

*Sigh* I swear I spent an hour googling. I figured it out myself. To describe the symptom again:

• If you open the ODBC Data Sources Administrator, and it is very slow to load the File DSN tab (e.g., a few minutes), and/or if when you select an ODBC export from Microsoft Access, and Access becomes unresponsive for a few minutes before opening the ODBC
  connection window, then...
• Your File DSN directory may not be set. The default is a location in Program Files; mine was scanning my Documents directory, which is huge. I don't know why it was set that way. Anyway, I set it to an empty local folder (I never use File DSN), and now
  it opens lickity-split.