#DateForumTypeThreadPost
2109 Nov 2006 @ 06:17 PSTConnectivityReplyDisplaying Teradata Database Errors in VB6 using ADOI only have access to Visual Studio 2005. So I decided to use ADO (ADODB) from C#.Following code fragment works and correctly displays1-3807[NCR][ODBC Teradata Driver][Teradata Database] Object 'ad...
2009 Nov 2006 @ 04:56 PSTConnectivityReplyConnect to TeraDatabase using Teradata.Client.ProviderCouple of suggestions:a) Try BTEQ first. BTEQ also has dependency on CLI which has a dependency on ICU and TeraGSS. If you can load BTEQ, then "SHOW Versions" will display the CLIV2 and TDICU Versi...
1906 Oct 2006 @ 12:53 PDTConnectivityReplyConnect to TeraDatabase using Teradata.Client.ProviderIn production, Domain Name Services is setup with COP entries for Teradata systems. Therefore there is no impact to Windows HOSTS file.I suggest that you contact Global Support Center and work with...
1803 Oct 2006 @ 06:47 PDTConnectivityReplyConnect to TeraDatabase using Teradata.Client.ProviderTDPID (a.k.a. SystemName or DBCName) has to be less than or equal to 8 characters.CLI appends COPn to the TDPID; and resolves the name to an IP Address. n is a number between 1 an X where X is the ...
1703 Oct 2006 @ 04:42 PDTConnectivityReplyConnect to TeraDatabase using Teradata.Client.ProviderAre you trying to connect to a DEMO database?Or is this a production machine?There is something wrong with your System Name and it must not conform to TDPID rules.Ping the system name and get the I...
1603 Oct 2006 @ 01:15 PDTConnectivityReplyConnect to TeraDatabase using Teradata.Client.ProviderI suggest starting out by indicating an invalid system name.That is use this Connection String: Data Source=Foo;User Id=Bar;Password=BG;It should generate the following error:[Call-Level Interfa...
1503 Oct 2006 @ 12:43 PDTConnectivityReplyConnect to TeraDatabase using Teradata.Client.ProviderAre you passing values for Data Source, User ID and Password?Your reply is not clear.
1402 Oct 2006 @ 05:37 PDTConnectivityReplyConnect to TeraDatabase using Teradata.Client.ProviderConnection String Syntax for .NET Data Provider is: Data Source=mySystemName;User Id=myUserId;Password=myPassword;Refer to the Help file for additional information on the Connection String.
1302 Oct 2006 @ 05:31 PDTConnectivityReplyConnect to TeraDatabase using Teradata.Client.ProviderCan you post the Connection String?I think there is something wrong with your connection string.
1202 Oct 2006 @ 03:16 PDTConnectivityReplyConnect to TeraDatabase using Teradata.Client.ProviderIs TeraSSO.dll the root cause of this issue?Did you try renaming the file and did it work?You can download TTU8.1 ODBC Driver from http://www.teradata.com/t/page/130536.
1129 Sep 2006 @ 07:15 PDTConnectivityReplyConnect to TeraDatabase using Teradata.Client.ProviderI also recommend upgrading to TTU8.1 ODBC driver.
1029 Sep 2006 @ 07:10 PDTConnectivityReplyConnect to TeraDatabase using Teradata.Client.ProviderTeraSSO.dll is used by ODBC Driver for Teradata and CLI.I noticed that you have ODBC Driver 03.01.00.00. Rename the TeraSSO.dll in Windows\System32 directory to TeraSSo.dll.old.Also, Dependes.exe ...
928 Sep 2006 @ 05:30 PDTConnectivityReplyConnect to TeraDatabase using Teradata.Client.ProviderI think you might have multiple copies of WinCli32.dll.Can you search your hard drive? specifically Windows\System32 directory.WinCli32.dll has a dependency on tdusr32.dll; which is usually in the ...
828 Sep 2006 @ 02:49 PDTConnectivityReplyConnect to TeraDatabase using Teradata.Client.ProviderCould you open a command prompt and display the Path?It should have C:\Program Files\NCR\Teradata Client\Cliv2 in it.Or better yet, Check the path in Start->Control Panel->System->Advanced->"Enviro...
728 Sep 2006 @ 01:05 PDTConnectivityReplyConnect to TeraDatabase using Teradata.Client.ProviderI suspect that the Path is not correct. Therefore CLR cannot find and load CLI (wincli32.dll).I suggest testing CLI installation by running NQuery.exe first.NQuery.exe is usually installed in "C:\P...
626 Sep 2006 @ 02:16 PDTConnectivityReplyError from .Net Provider - CLI2: BADMOVEMODE(387)Also look for TeraGss.dll in Windows\System32 directory and rename it.TeraGSS much like CLI is no longer installed into Windows\System32 directory.Also, TW 8.1 Demo CD is now available from http://...
514 Sep 2006 @ 10:18 PDTConnectivityReplyOLEDB Connection issueNo, not to my knowledge.Please Contact Teradata Global Support Center.
414 Sep 2006 @ 10:00 PDTConnectivityReplyError from .Net Provider - CLI2: BADMOVEMODE(387)Search for wincli32.dll on your hard drive.I think you will find an older version of wincli32.dll in Windows\System32 directory.Also, you can download ListDlls from www.sysinternals.com. It will he...
314 Sep 2006 @ 01:18 PDTConnectivityReplyOLEDB Connection issueTeraGSS 6.1.0.14 improves the performance for the very first logon within a process. I suggest using 6.1.0.14 with the .NET Data Provider for Teradata.
214 Sep 2006 @ 12:28 PDTConnectivityReply.NET Provider TdConnectionStringBuilder helpPlease set TdConnectionStringBuilder.PersistSecurityInfo property to true.Release 1 required this property to be set to true before it would persist the password to the Connection String. This requ...
114 Sep 2006 @ 12:22 PDTConnectivityReplyError from .Net Provider - CLI2: BADMOVEMODE(387).NET Data Provider for Teradata Release 1 requires CLI Version 4.8.1.2.Please uninstall CLI and install CLI Version 4.8.1.2..NET Data Provider for Teradata Release 1.0 utilizes Teradata Call-Level ...

Pages