Could Not Be Loaded Due To System Error 193
Contents |
nco_g_odbc; libodbc; datadirect drivers; ODBC libraries; datasource; specified driver could not be loaded due to system error 193 teradata odbc gateway Technote (troubleshooting) Problem(Abstract) Unable to use the Microsoft ODBC Administrator specified driver could not be loaded due to system error 193 oracle to create the DataSource on Windows 64-bit. Symptom Receive the error "The setup routines for the DataDirect 5.3
Could Not Be Loaded Due To System Error Code 193
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
content management Sitefinity Digital Experience Cloud Track, analyze and shape every step of the customer journey Application Development, Testing & Deployment Telerik DevCraft Leverage a complete UI toolbox for web, mobile
Odbc Driver Could Not Be Loaded Due To System Error Code 193
and desktop development Telerik Platform Build mobile apps for iOS, Android and specified driver could not be loaded due to system error 126 Windows Phone Test Studio Automate UI, load and performance testing for web, desktop and mobile OpenEdge Streamline business specified driver could not be loaded due to system error 126 (sql server) app development and management Rollbase Develop SaaS business apps with point and click ease Modulus Run Node.js, PHP, Java and MongoDB at scale Data Connectivity Tools DataDirect Connectors Optimize data http://www-01.ibm.com/support/docview.wss?uid=swg21377507 integration with high-performance connectivity Business Rules Management Corticon Rules Engine that improves productivity and lowers costs by automating your decision process View All Products Whats New New DigitalFactory: Our comprehensive solution for crafting and managing sophisticated digital experiences Solutions Digital Business Transformation Transform your businesses in order to survive in a completely digitized and connected world driven by software innovation. DigitalFactory http://knowledgebase.progress.com/articles/Article/P141118 Comprehensive solution for crafting and managing sophisticated digital experiences Modernization UX and app modernization to powerfully navigate todays digital landscape DigitalFactory for Sites Globally scale websites with innovative content management and infrastructure approaches aPaaS Fuel agility with ever-ready applications, built in the cloud DigitalFactory for Engagement Content-focused web and mobile solution for empowering marketers DigitalFactory for Mobile Faster, tailored mobile experiences for any device and data source New & Trending E-book The Digital Ultimatum: Why Businesses Must Digitally Transform to Survive â€" and Thrive Survey Report The State of Digital Business Support & Learning Support Support Services Knowledge Base Customer Order Management Download Center Services Training Consulting Services Managed Database Offering Learning Documentation Webinars How-To Videos Whitepapers Community Blogs Success Stories Partners Company Login Progress Support Rollbase DataDirect Cloud PartnerLink Telerik Your Account Telerik Platform Global Sites Brazil France Germany Netherlands United States Menu 1-800-477-6473 Contact Sales Knowledge Base 000013067 < Back to search results System Error 193 when configuring the 10.2A ODBC driver on Windows 64-bitPrintable View «Go BackInformation EnvironmentProduct: OpenEdge Version: 10.2A OS: Windows 64-bits Other: InstallQuest
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) 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 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 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, 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 with "The could not 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 bit version or could not be 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 version of the ODBC Administrator tool displa