Could Not Be Loaded Nt Error 998
All communityThis categoryThis boardKnowledge baseUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Did you mean: Teradata : Product Forums : Connectivity : ODBC Connection Error - Specified driver could not... Options Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page brydgesk Enthusiast Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Get Direct Link Print Email to a Friend Report Inappropriate Content 04-03-2012 03:00 PM 04-03-2012 03:00 PM ODBC Connection Error - Specified driver could not be loaded I installed the most recent ODBC driver earlier today (Windows XP 32-bit, ODBC version 14.00.00.04), and immediately lost the ability to connect via ODBC, in Teradata SQL Assistant. The error I receive is: 160: Specified driver could not be loaded due to system error 126 (Teradata) I gave up on trying to troubleshoot this error, and uninstalled that ODBC driver, but still receive the error. Since then I have done many things, but still receive the error: Uninstalled all programs relating to teradata (utilities, ODBC driver, ICU, GSS, SQL Assistant, etc) Deleted Tdata32.dll, Tdatas32.dll, tdprsr32.dll, and terasso.dll in the WINDOWS\system32 folder Did a registry search for 'Teradata' and removed all references to Driver Version 14 Restarted Installed complete Teradata 13 TTU, including all utilities, ODBC driver, ICU, and GSS Created new ODBC entries using newly installed Teradata driver Copied dll's from "C:\Program Files\Teradata\Client\13.10\ODBC Driver for Teradata\Lib" to "C:\WINDOWS\system32" Restarted After all those steps, I still receive the same "dri
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph Outlook OneDrive/Sharepoint Skype Services Store Cortana Bing Application Insights Languages & platforms Xamarin ASP.NET C++ TypeScript .NET - VB, C#, F# Server Windows Server SQL Server BizTalk Server SharePoint Dynamics Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Windows Dev Center Windows Dev http://community.teradata.com/t5/Connectivity/ODBC-Connection-Error-Specified-driver-could-not-be-loaded/td-p/48945 Center Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise Windows Store opportunities Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference https://msdn.microsoft.com/en-us/library/windows/desktop/ms681388(v=vs.85).aspx Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Why Windows Dashboard Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise Windows Store opportunities Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Why Windows Dashboard Error Handling Error Handling Reference System Error Codes System Error Codes System Error Codes (500-999) System Error Codes (500-999) System Error Codes (500-999) System Error Codes (0-499) System Error Codes (500-999) System Error Codes (1000-1299) System Error Codes (1300-1699) System Error Codes (1700-3999) System Error Codes (4000-5999) System Error Codes (6000-8199) System Error Codes (8200-8999) System Error Codes (9000-11999) System Error Codes (12000-15999) TOC Collapse the table o
HELP Contact Support Ask Question Support Plans https://bugs.mysql.com/bug.php?id=1602 RESOURCES System Requirements Software Updates Document Library FEEDBACK Service Feedback Support Escalation Fatal SQLUNIRL.DLL could not Initialization Error on a Domain Controller Edit 1 … 0 Tags No tags Notify RSS Backlinks Source Print Export (PDF) This article applies to NET SatisFAXtion 8.5. SOLUTION Fatal SQLUNIRL.DLL could not be Initialization Error 'File: ..src\procaddr.c\ line: 422 COMCTL32.DLL Could not be loaded, NT Error 998' When installing MSDE on a Domain Controller (Model Native or Mixed mode Platform 2000-2003 Active Directory) PDC emulator role needs to be the 'local server' and the install will complete. After installation is complete, change the role back. Javascript Required You need to enable Javascript in your browser to edit pages. help on how to format text Copyright © FaxBack, Inc. Turn off "Getting Started" Home ... Loading...
Oz Email Updates: Status: Can't repeat Impact on me: None Category:Connector / ODBC Severity:S1 (Critical) Version:3.51.06 OS:Microsoft Windows (Windows NT4) Assigned to: View Add Comment Files Developer Edit Submission View Progress Log Contributions [19 Oct 2003 20:15] Wizard of Oz Description: I installed the MySQL ODBC driver on Windows NT4 with SP6a installed. When I try to setup a System DSN then I get the following error messages: The setup routines for the MySQL ODBC 3.51 Driver ODBC driver could not be loaded due to system error code 126. ... and then Could not load the setup or translator library. I did look at the KB article and installed the latest version of the MDAC (2.8), rebooted and the problem persists. Please note that I am not requesting support, the proposed solution just does not seem to work. The ODBC driver works just fine on Win2k and higher. How to repeat: Install the ODBC driver on Windows NT [4 Dec 2003 9:53] Miguel Solorzano I don't have NT 4 for to make this test, then I have limited for to search a possible cause for, and, I found that this issue isn't limited only to MyODBC driver should happen also with anothers ODBC drivers. The explanation for this issue and possible solution for you can find at: http://support.microsoft.com/default.aspx?scid=kb;en-us;260558 [4 Dec 2003 10:12] Wizard of Oz Dear Miguel, Thank you for your efforts, the referenced article at Microsoft (KB260558) unfortunately does not solve the problem. I am quite certain that the MDAC installation is correct. It was just verified with a special utility called "Component Checker" which you can download from http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF09.... According to this tool the MDAC installation is 100% OK, yet the problem with the MySQL ODBC driver remains. Note that this is a machine with hardly any software running on it, a clean NT4 installation with MDAC 2.8 installed. There are no problems with a SQL ODBC driver, only the MySQL doesn't work. This is quite a shame since we can't use MySQL here. Best Regards, Ingmar Koecher. [22 Jul 2004 3:45] Timothy Smith Unfortunately, we can't repeat this problem to figure out what is wrong. This issue has been stalled for eight months now, so I'm setting it to "Can't Repeat". If any further information is available, I would be glad to hear of it. With apologies, Timothy [3 Aug 2004 2:09] Chris Jeske I've had this problem twice now. Running the same setup as you, NT 4.0 with SP6 and latest MyODBC driver. Doublechecked everything, all the paths are correct everywhere, registry is fine, latest version of MDAC (I just reverted because I