Odbc Could Not Be Loaded Due To System Error 193
Contents |
nco_g_odbc; libodbc; datadirect drivers; ODBC libraries; datasource; odbc driver could not be loaded due to system error code 126 odbc gateway Technote (troubleshooting) Problem(Abstract) Unable to use the Microsoft ODBC Administrator to
The Setup Routines For The Oracle In Oraclient11g_home1 Odbc Driver Could Not Be Found
create the DataSource on Windows 64-bit. Symptom Receive the error "The setup routines for the DataDirect 5.3
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20122008 R2200820052000LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: odbc administrator system error code 193 SQL Server > SQL Server Data Access Question 0 Sign in to vote
Specified Driver Could Not Be Loaded Due To System Error 126
I am trying to create data soucre using microsoft odbc administrator. I am running specified driver could not be loaded due to system error 127 Windows 7 business 64 bit version. I have oracle 11g 64 bit instant client and the 64 bit ODBC drivers installed.
The Setup Routines For The Oracle In Error Code 126
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.Any http://www-01.ibm.com/support/docview.wss?uid=swg21377507 help would be greatly appreciated.Thanks Moved by Steven - Support EngineerMicrosoft Support Wednesday, January 13, 2010 8:00 PM Moving to related community (From:Hardware and Drivers) Tuesday, January 12, 2010 5:20 PM Reply | Quote Answers 1 Sign in to vote This error code means this: ERROR_BAD_EXE_FORMAT193 (0xC1) %1 is not a valid Win32 application. If you are talking about ODBCAD32.exe, then it looks like the installation of the driver https://social.technet.microsoft.com/Forums/sqlserver/en-US/02e932e0-fddc-49f7-bb96-b43e6e999f07/odbc-administrator-system-error-code-193?forum=sqldataaccess mis-registered a 32 bit driver ad 64 bit or vise-versa. It is trying 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). As 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.I would take this up with Oracle from here, I suppose.Hope that helps,JohnThis post is provided 'as is' and confers no express or implied warranties or rights. Marked as answer by John C GordonMicrosoft employee, Moderator Wednesday, January 13, 2010 9:53 PM Wednesday, January 13, 2010 9:53 PM Reply | Quote Moderator All replies 1 Sign in to vote This error code means this: ERROR_BAD_EXE_FORMAT193 (0xC1) %1 is not a valid Win32 application. If you are talking about ODBCAD32.exe, then it looks like the installation of the driver mis-registered a 32 bit driver ad 64 bit or vise-versa. It is trying 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). As the driver listing
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) 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 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 r2 Native Driver SQL Server > SQL Server Data Access Question 0 Sign in to vote I recently had the SQL Server 2008 R2 Client installed on my Windows XP laptop. Ever since, https://www.experts-exchange.com/questions/27227544/Pervasive-ODBC-Error-193-When-Trying-to-Remove-System-DSN.html when I try to create a new System DSN connection in the ODBC Administrator using the SQL Server 2008 Native Driver (v10.0 is what shows up in the ODBC Administrator) the process fails could not with "The setup routines for the SQL Server Native Client 10.0 ODBC Driver could not be loaded 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 could not be 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 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 versio
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Pervasive ODBC Error 193 When Trying to Remove System DSN Want to Advertise Here? Solved Pervasive ODBC Error 193 When Trying to Remove System DSN Posted on 2011-07-28 Databases Windows 7 1 Verified Solution 4 Comments 3,540 Views Last Modified: 2012-05-11 Whenever I try to remove a System DSN I get an error message that states "the setup routines for the Pervasive ODBC client interface ODBC driver could not be loaded due to system error code 193." I recently purchased a new laptop that runs Windows 7 (64-bit). I used the "migration" tool to import documents/settings from my XP laptop (32-bit). I think it also moved my ODBC connections and now, since the drivers, driver locations, and driver bit level have changed, everything is messed up. Am I on the right track? Can someone suggest a way out of this mess? 0 Question by:trbbhm Facebook Twitter LinkedIn Google LVL 18 Active 2 days ago Best Solution bymirtheil Check the HKEY_LOCAL_MACHINE\SOFTWARE\ODBC key. I wonder if it migrated the ODBC entries to the 64 bit portion of the registry. Go to Solution 4 Comments LVL 18 Overall: Level 18 Databases 15 Windows 7 1 Message Active 2 days ago Expert Comment by:mirtheil2011-07-28 The easiest way to remove these entries would be to load up the Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC and then you can remove the DSN name entry from the "ODBC.INI" and "ODBC Data Sources" keys. The other option would be to install the old PSQL engine, remove the DSNs, then uninstall (if you're not using PSQL any more). 0 Message Author Comment by:trbbhm2011-07-28 I looked at the registry but the DSNs in question are not there. I've also installed the 32-bit Pervasive drivers and tried to remove the DSNs in question, but no joy. 0 LVL 18 Overall: Level 18 Databases 15 Windows 7 1 Message Active 2 days ago Accepted Solution by:mirtheil2011-07-28 Check the HKEY_LOCAL_MACHINE\SOFTWARE\ODBC key. I wonder if it migrated the ODBC entries to the 64 bit portion of the registry. 0 Message Author C