.NET Data Provider for Teradata error [Call-Level Interface, Version 2] [303]

Connectivity
N/A

.NET Data Provider for Teradata error [Call-Level Interface, Version 2] [303]

Hi,
We are trying to use NET Data Provider for Teradata 01.01.00.00 to connect to our data source.

We are running a test with Nquery (a .Net tool provided by NCR to test connectivity to the Teradata Database using Teradata.Client.Provider.dll)

The connection sting we are using is:
User Id=xxxxx;Password=xxxxx;Data Source=xx.xx.xx.xx;Database=databasename;

The error we get is:
Teradata.Client.Provider.TdException was unhandled
Message="[Call-Level Interface, Version 2] [303] "
Source="Call-Level Interface, Version 2"
ErrorCode=-2147467259
TxRolledBack=false

Any help is much appreciated.
4 REPLIES
Teradata Employee

Re: .NET Data Provider for Teradata error [Call-Level Interface, Version 2] [303]

Error 303 is "BADLOGON Invalid logon string".

Earlier versions of CLI did not support IP address as the "Data Source".
I suspect you are not using CLI version 4.8.1.4.

I suggest:
a) Download LISTDLLS.
b) Run NQuery and try to connect.
c) Open a DOS Command Prompt and run ListDlls NQuery | Find "wincli"
d) Check CLI version and the path. The version should be 4.8.1.4 or greater.

I think you might have an older version of CLI in Windows\System32 directory.
Teradata Employee

Re: .NET Data Provider for Teradata error [Call-Level Interface, Version 2] [303]

I´ve the same issue with Visual Studio 2005 using the Teradata .Net Provider 1.02.
All components delivered with the .Net Provider 1.02 package are installed incl. CLI version 4.8.2.2. Also listdlls displays cli version 4.8.2.2.
Because the ODBC.Net provider is working correct and the issue also occurs in NQuery I assume that this is a localization based issue.
Do you have any ideas to get the .Net provider working?

Thanks,
Mario
Teradata Employee

Re: .NET Data Provider for Teradata error [Call-Level Interface, Version 2] [303]

I think CLI cannot parse the Logon String which is something like "DataSource/UserId,Password".
Do you have BTEQ? Can BTEQ logon to the DataSource?
Teradata Employee

Re: .NET Data Provider for Teradata error [Call-Level Interface, Version 2] [303]

Also make sure your DataSource conforms to TDPID rules like 8 characters max.
CLI enforces this rule but ODBC does not.
You can use IP address for the DataSource.