Due To System Error Code 193
Contents |
nco_g_odbc; libodbc; datadirect drivers; ODBC libraries; datasource;
Oracle System Error Code 193
odbc gateway Technote (troubleshooting) Problem(Abstract) Unable to use the Microsoft ODBC Administrator odbc driver could not be loaded due to system error code 126 to create the DataSource on Windows 64-bit. Symptom Receive the error "The setup routines for the DataDirect 5.3
Specified Driver Could Not Be Loaded Due To System Error 126
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. Document information More support for: Tivoli Netcool/OMNIbus ODBC (MySQL) Gateway Software version: 7.3.0, 7.3.1, 7.4.0 Operating system(s): Windows Software edition: All Editions Reference #: 1377507 Modified date: 2016-05-31 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Error 193 received when trying to create an ODBC Connection using the SQL Server 2008 r2 Native Driver SQL Server > SQL Server Data the setup routines for the oracle in error code 126 Access Question 0 Sign in to vote I recently had the SQL Server 2008 the setup routines for the oracle in oraclient11g_home1 odbc driver could not be found R2 Client installed on my Windows XP laptop. Ever since, when I try to create a new System DSN connection in the ODBC
Specified Driver Could Not Be Loaded Due To System Error 127
Administrator using the SQL Server 2008 Native Driver (v10.0 is what shows up in the ODBC Administrator) the process fails with "The setup routines for the SQL Server Native Client 10.0 ODBC Driver could not be loaded http://www-01.ibm.com/support/docview.wss?uid=swg21377507 due to system error code193". Everything that I've been able to find out about this system error suggests that this problem is caused by an error in the way the driver was registered when it was installed (that it was registered as 64 bit when it is really the 32 bit version or vice-versa). Is there an easy registry correction that will fix this problem? Tuesday, January 10, 2012 11:44 PM Reply | Quote Answers https://social.msdn.microsoft.com/Forums/sqlserver/en-US/4e484f1c-fad3-48b2-ae7c-8ab583c99db8/error-193-received-when-trying-to-create-an-odbc-connection-using-the-sql-server-2008-r2-native?forum=sqldataaccess 0 Sign in to vote Hi ElkinsEcon, Regarding to your description, seems the installation of the driver mis-registered a 64 bit driver but it is a 32 bit or vise-versa version. As the ODBC driver listing is determined by registry keys that are set on installation of the driver, it is likely that the driver installer has a fault which is causing it to be mis-registered with ODBC. Please try to load either a 32 bit driver from the 64 bit version (C:\windows\system32\odbcad32.exe) or trying to load a 64 bit driver from the 32 bit version (C:\windows\syswow64\odbcad32.exe). Additional if you build and then run an application as a 32-bit application on a 64-bit operating system, the workaround is try to create the ODBC data source by using the ODBC Administrator tool in %windir%\SysWOW64\odbcad32.exe. To indicate the type of DSN, you can add "_32" to the 32-bit user DSNs and "_64" to the 64-bit user DSNs. More information, please refer to The 32-bit version of the ODBC Administrator tool and the 64-bit version of the ODBC Administrator tool display both the 32-bit user DSNs and the 64-bit user DSNs in a 64-bit version of the Windows operating systemRegards, Amber zhang Marked as answer by Stephanie Lv Tuesday, January 17, 2012 8:00 AM Thursday, January 12, 2012 3:29 AM Reply | Quote Moderator Mi
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of http://stackoverflow.com/questions/7662478/odbc-for-mdb-accdb-error-code-193 this site About Us Learn more about Stack Overflow the company Business Learn http://www.itninja.com/question/odbc-error-193 more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up system error ODBC for mdb/accdb: Error Code 193 up vote 0 down vote favorite 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 due to system 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 share|improve this question asked Oct 5 '11 at 13:58 user973479 75941642 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) –user973479 Oct 5 '11 at 18:38 add a comment| 1 Answer 1 active oldest votes up vote 3 down vote accepted 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) – share|improve this answer answered Dec 12 '11 at 14:50 user973479 75941642 add a comment| Your Answer draft saved draft discarded Sign up o
soucre using microsoft odbc administrator. I am running Windows 7 business 64 bit version. I have oracle 11g 64 bit instant client and the 64 bit ODBC drivers installed. The driver shows up when I click add but then I get a messages saying "The setup routines for the Oracle in instantclient11_1 ODBC driver could not be loaded due to system error code 193. 0 Comments [ + ] Show Comments Comments Please log in to comment Answers 0 Error Code 193 - %1 is not a valid Win32 application. Make sure your installation installed the 64bit version and not a 32bit version of the ODBC driver. The driver listing is determined by registry keys that are set on installation of the driver, it is likely that the driver installer has a fault which is causing it to be mis-registered with ODBC. Answered 03/21/2012 by: Trinity Please log in to comment Please log in to comment Answer this question or Comment on this question for clarity AnswerSubmit Don't be a Stranger! Sign up today to participate, stay informed, earn points and establish a reputation for yourself! Sign up! or login Share Home Pages Software Deployment Tips Questions Blog Posts Shared Links FAQ & Support Site FAQ AppDeploy FAQ About ITNinja Welcome Video Tour Contact Sitemap Share/Contribute © 2016 Dell Inc. All rights reserved. Legal | Feedback c926729 Tue September 6 19:00:00 EDT 2016"www.itninja.com