Quantcast
Channel: Teradata Forums - Database
Viewing all articles
Browse latest Browse all 14773

Teradata .Net Dataprovider connection error - response (3) by ysrinu

$
0
0
The following the article from Teradata support for KAP1B0756    Teradata Knowledge Base    Solution    ID: KAP1B0756 Special character in password such as @ prevents LDAP login 1 Condition/Symptom:              LDAP logins fail if the password includes a special character such as an at @ sign. The error indicates "User ID, Password or Account is invalid." Probable Cause:          The characters @, / and \ have special meanings in a UPN. If they are encountered in a password, they must be escaped as follows: \@, \/ (backslash followed immediately by forward slash, not capital V)and \\. Solution:          The problem is documented in DR 119905 for CLIv2 and DR 132857 for ODBC, and is fixed in the following product versions: CLIv2 12.0.0.7, 13.0.0.2, 13.10.0.0 ODBC 12.0.0.6, 13.0.0.3, 13.10.0.0 Prior to using a fixed version, the workaround is to use the escape character \ prior to the character. Configuration Data:      References to Procedures:      Additional Info/Comments:      Current Attachments:     There are no attachments on this document.    

Viewing all articles
Browse latest Browse all 14773

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>