Cause INFA_CauseThe issue occurs because the Teradata ODBC dll (C:\Program Files\Teradata\Client\13.10\ODBC Driver for Teradata nt-x8664\Lib\Tdata32.dll) has dependencies on the Shared ICU libraries which are installed to C:\Program Files\Teradata\Client\13.10\Shared ICU Libraries for However, the information provided is for your information only. This issue only occurs if using Teradata ODBC libs version 13.10 or later on Windows 32 bit or Windows 64 bit. That applies to both 32 and 64 bit. 0 Kudos Reply zipippis N/A Mark as New Bookmark Subscribe Subscribe to RSS Feed Get Direct Link Print Email to a Friend Report weblink
Resolving the problem This problem has been reported to SPSS Development - Workaround Available Windows based SPSS OEM SDAP6 have a dependency on CLIv2 library files. Thanks! 0 Kudos Reply All forum topics Previous Topic Next Topic 1 REPLY patrickhu Fan Mark as New Bookmark Subscribe Subscribe to RSS Feed Get Direct Link Print Email to a Even added the QV Admin group to the teradata folder permissions to test that theory too. I did it many times in many variations.It's all about Teradata 15.0 package.Is there any way to know what does it want?
This document resolved my issue This document did not resolve my issue This document helped but additional information was required to resolve my issue What can we do to improve this Workaround If it is preferable to have the Test Connection pass, do the following to resolve this issue: Open Windows Explorer on the Server machine and navigate to C:\Program Files\Teradata\Client\13.10\Shared ICU Download the appropriate files from here: http://downloads.teradata.com/download/connectivity/teradata-odbc-driver-13-0-for-windows-64-bit Example: For windows these are the files: cliv2_WINDOWS_x8664.13.00.00.07.ZIP (64 bit) cliv2_WINDOWS_i386.13.00.00.07.ZIP (32 bit) You may need to use the 13.00.00.05.zip versions in the absence
Odbc operation attempted: SQLDriverConnect. Specified Driver Could Not Be Loaded Due To System Error 126 (sql Server) Can anyone advise a fix? The OS, report, Teradata server are all 64b but the Tera ODBC makes it appear 32b even from teh 64b tera folder location.Thanks for the suggestion, originally I applied the 32b So the OBDC detils in registry was causing the major issue.Here's the step I followed,1.Uninstalled the Teradata ODBC (ODBC-ICU-GSS)2.I cleaned the registry for any entry reference to Teradata ODBC driver. (To
Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. have a peek at these guys Please see SB 823 at : http://cks.teradata.com/skb/i/KAC13BFE2 0 Kudos Reply Teradata Links Teradata.com Teradata Partners Support & Forums Support Portal / TaYS Teradata Aster Community Communities Downloads Documentation Developer In my case, it worked. Tags (3) Tags:32-bit connection64-bit connectionodbc 0 Kudos Reply All forum topics Previous Topic Next Topic 3 REPLIES salmanali01 N/A Mark as New Bookmark Subscribe Subscribe to RSS Feed Get Direct Link Specified Driver Could Not Be Loaded Due To System Error 193
ErrorCode=[-1]. Progress Software Corporation makes no explicit or implied claims to the validity of this information. i gotit resolved yesterday. check over here I restarted the server, this was done to ensure that all system files and variables could get itself set right5.
Historical Number 1028294 Document information More support for: Cognos 8 Business Intelligence Report Studio Software version: 8.1 Operating system(s): Windows Reference #: 1341264 Modified date: 20 March 2008 Site availability Site Im003 Specified Driver Could Not Be Loaded These include: GSS (security sub system) TDICU (TeraData Internationalization system) MDAC 2.5 (comes with Windows XP/2003) Once all these are installed, the system needs to be rebooted to ensure that all Like Show 1 Like (1) Actions Re: Problems with Teradata ODBC connector Colin Albert Jan 14, 2015 12:47 PM (in response to Jayson Osmars) You should be able to copy the
Steps to ReproduceClarifying Information Error MessageSpecified driver could not be loaded due to system error 126Defect/Enhancement NumberCauseThe error message occurs when the Teradata client has not been configured correctly. Same result. 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 Error Im003 Specified Driver Could Not Be Loaded Due To System Error 8 For example, with the ODBC component from the Aster Clients 6.21 release the following error is observed : "The setup routines for the Aster ODBC driver could not be loaded due
I have installed the bundled TTU13.10.00.05 64 bit. Should I go to a previous version?The entire Aster Clients 6.21 package was removed from this download site and the TeradataAsterR_1.0.0 component was added. Make sure you have 64-bit TTU 13.0 (or later Efix on this release) Teradata ICU package installed. 0 Kudos Reply bkrywucki Fan Mark as New Bookmark Subscribe Subscribe to RSS Feed this content Help anyone?
Like Show 0 Likes (0) Actions Re: Problems with Teradata ODBC connector Colin Albert Jan 14, 2015 9:58 AM (in response to Colin Albert ) You may also need to connect