Problem
You receive the following system error code 193 when using the Microsoft ODBC Administrator to create the DataSource for Tivoli Netcool / OMNIbus on Windows 64-bit: The setup routines for the DataDirect 5.3 ODBC driver could not be loaded due to system error code 193.
Symptom
Receive the error
«The setup routines for the DataDirect 5.3 <driver name> ODBC driver could not be loaded due to system error code 193.»
Cause
The driver is a 32-bit driver and the default Microsoft ODBC Administrator utility is for 64-bit drivers.
Resolving The Problem
On 64-bit Windows, there are two versions of the Microsoft ODBC Administrator tool. Typically, you go to Start —> Administrative Tools —> Data Sources (ODBC) to create ODBC connections. This calls the program %WINDIR%\System32\odbcad32.exe to create a 64-bit ODBC connection. However, this program will not create 32-bit ODBC connections.
The ODBC gateway requires a 32-bit ODBC connection. Use the 32-bit version of the Microsoft ODBC Administrator tool located in %systemdrive%\Windows\SysWoW64\odbcad32.exe to create the ODBC Data Source.
[{«Product»:{«code»:»SSSHTQ»,»label»:»Tivoli Netcool\/OMNIbus»},»Business Unit»:{«code»:»BU053″,»label»:»Cloud & Data Platform»},»Component»:»ODBC (MySQL) Gateway»,»Platform»:[{«code»:»PF033″,»label»:»Windows»}],»Version»:»7.4.0;7.3.1;7.3.0″,»Edition»:»All Editions»,»Line of Business»:{«code»:»LOB45″,»label»:»Automation»}}]
- Remove From My Forums
-
Question
-
I’ve been struggling to re-set up my ODBC for Oracle connection. My new laptop is Windows 10 pro, 64-bit. I’m running Access 2016.
I’ve been tinkering with the properties based on googling around. Below is a common solution provided, but it does not work.
Go to control panel -> administrative tools –> select data sources(ODBC) –> then right click on that file –> go to properties –> in the shortcut tab -> change the path from %windir%System32odbcad32.exe to %windir%SysWOW64odbcad32.exe
Does anyone know how to resolve?
when I try to run the sqlcmd command in the command line, I get the following error message:
Sqlcmd: Error: Microsoft ODBC Driver 11 for SQL Server : Specified driver could not be loaded due to system error 193: (ODBC Driver 11 for SQL Server, C:\Windows\system32\msodbcsql11.dll)
I checked «C:\Windows\system32\» directory and I can see that the the dll is located correctly:
DLL is located in the directory
I also double checked that «Microsoft ODBC Driver 11 for SQL Server» is installed (version 12.0.2000.8).
OS: Windows Server 2012 R2 Standard
SQL Server Version: Microsoft SQL Server 2014 — 12.0.2000.8 (X64)
Feb 20 2014 20:04:26
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.3 (Build 9600: )
Any ideas why I cannot run the command sqlcmd in the command line?
Thanks a lot in advance,
Roman
asked Oct 15, 2015 at 14:40
2
I downloaded Dependency Walker and realized that msodbcsql11.dll is really x86 instead of x64. I replaced the DLL and everything works fine.
Thanks for your help, Roman
answered Nov 3, 2015 at 10:57
- I have a Win7-64 bit OS
- I have MS Office 2010 32-bit installed
I manage the ODBC data sources via ControlPanel->SystemAndSecurity->AdministrativeTools->DataSources
In the UserDSN tab, I see an entry for «MS Access Database Microsoft Access Driver(*.mdb, *.accdb);
If I click on the ‘remove’ or ‘configure’ buttons for that entry, I get an Error code 193.
Note:
- I ran AccessDatabaseEngine.exe to make sure I have the 32 bit dlls.
- I can verify that the dlls exist in the 32 bit folder (Ex: C:\Program Files (x86)\Common Files\microsoft shared\OFFICE14\ACEODBC.DLL)
What am I doing wrong? Am I missing something?
Thanks!
- windows-7
- odbc
- ms-access
asked Oct 5, 2011 at 13:58
user973479user973479
1,6295 gold badges26 silver badges48 bronze badges
0
1 Answer
Ok, I figured it out. Basically if you run the C:\Windows\SysWOW64\odbcad32.exe the messages go away since you are now looking at 32 bit odbc connections and not 64 bit ones (which are the default when going through the Windows7 64-bit GUI) –
answered Dec 12, 2011 at 14:50
user973479user973479
1,6295 gold badges26 silver badges48 bronze badges
Sometimes configuring ODBC gives error code 193 on windows 64 bit. Let’s see how we can fix it. At Bobcares, we can handle your server-related issues with our Server Management Services.
Configuring ODBC gives error code 193 on windows 64 bit – Why?
The setup of OpenEdge 10.2A produces registry entries under the wrong Node. 10.2A includes functionality for 64-bit OpenEdge installations, so the wownode is no longer written to, unlike in 10.1B and 10.1C. The installation creates ODBC driver registry keys in the:
The ODBC driver is not properly created in the wownode as it would be like:
The error message is as follows:
We can resolve this problem if the setup recognizes “if bits=64” and writes to the 64-bit registry or the wownode as necessary. This is possible by upgrading to OpenEdge 10.2B or later.
How to fix the error?
We can use any of the below methods to create the registry keys. We’ve to make sure to keep a backup of the registry before any change.
Method 1
-
- On Windows, go to start >> programs >> run >> regedit.exe.
- Navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]
- Choose export by right-clicking on ODBC drivers.
- Save in a file xx.reg
- Go to [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Progress OpenEdge 10.2A Driver] from regedit again.
- Choose export by performing a right-click on Progress OpenEdge 10.2A Driver.
- Save in a file yy.reg
- Modify yy.reg and add Wow6432Node to the line.
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]
The new line will be:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\ODBC Drivers]
- Maintain yy.reg.
- Utilize the Register Editor’s import feature (File >> import) to import xx.reg.
- Utilize the Register Editor’s import feature (File >> import) to import yy.reg.
- From this point forward, add or configure your User or System DSN using the 32-bit ODBC Data Source Administrator by running
%WINDIR%\SysWow64\odbcad32.exe
Method 2
- Copy the below contents after creating a .REG file.
- To add the keys to the registry, save the file and double-click on it.
[Need help with another issue? We’re available 24/7.]
Conclusion
The article points out the cause for the error code 193 on windows 64 bit while configuring ODBC. We also provide two methods from our Tech team to fix the issue.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
GET STARTED