topic Re: SAS connectivity to Teradata not working with SSO/IWA in Administration and Deployment

SAS connectivity to Teradata not working with SSO/IWA

RupaJ — Mon, 05 Nov 2018 22:26:04 GMT

Hello - Have been struggling with this issue for more than 2 weeks now. Need some direction here pls.

Here is the libname that throws error from SAS Enterprise guide.

libname <libname> teradata server=abc schema=<schema name> ;

Here is the error it throws

ERROR: Teradata connection: MTDP: EM_GSSCALLFAIL(236): call to gss_call failed. .

ERROR: Error in the LIBNAME statement.

How do I enable more logging on SAS to debug the SSO /IWA issue? I tested the same from SAS commandline (./sas -nodms) and get the same error.

Re: SAS connectivity to Teradata not working with SSO/IWA

SASKiwi — Tue, 06 Nov 2018 03:07:03 GMT

Have looked at the doc? https://documentation.sas.com/?docsetId=acreldb&docsetTarget=p1djetrmbn53w3n0z737je0qpqt5.htm&docsetVersion=9.4&locale=en

Are you using Kerberos and what user credentials are you using?

Re: SAS connectivity to Teradata not working with SSO/IWA

SimonDawson — Tue, 06 Nov 2018 03:57:40 GMT

This is unlikely to be an issue with SAS if the GSS calls inside Teradata fail for both SAS Foundation on the server and from SAS Enterprise Guide.

I'd have your Teradata DBA deploy the client software to the SAS box so that BTEQ is available.

Logon as a user to the host, run BTEQ and use the .LOGON directive but hit enter for both the username and password without typing anything. ie. Leaving them empty, if the prompt returns and you are logged in then you know your DBA has configured it correctly on the Teradata side. If you get the same EM_GSSCALLFAIL message then this is something for your Teradata folks to look up at not your SAS folks.

Re: SAS connectivity to Teradata not working with SSO/IWA

RupaJ — Tue, 06 Nov 2018 15:09:39 GMT

Hi @SASKiwi - We are using kerberos and yes I did take a look at the document. It says the kerberos tickets generated are either expired or does not exist. However the tcikets are getting generated with proper validity. Our system admin checked it.

@SimonDawson - Thanks for pointing at that. I shall get bteq installed on SAS server and test it outside of SAS and check what happens.

Thanks both of you for pointers. Hopefully I can get this fixed today.

Re: SAS connectivity to Teradata not working with SSO/IWA

RupaJ — Tue, 06 Nov 2018 18:21:32 GMT

@SimonDawson

I tried connecting from bteq to Teradata and here is what I get.

*** CLI error: MTDP: EM_GSSCALLFAIL(236): call to gss_call failed. Failure Server not found in Kerberos database
*** Return code from CLI is: 236
*** Error: Logon failed!

*** Total elapsed time was 1 second.

My linux administrator is not sure how to fix the error "Failure Server not found in Kerberos database". Any direction here pls?

Thanks!

Re: SAS connectivity to Teradata not working with SSO/IWA

SimonDawson — Thu, 08 Nov 2018 09:21:14 GMT

I'd engage Teradata technical support. This same error occurs with no involvement of any SAS software. Teradata software is the only thing in the mix now.

Re: SAS connectivity to Teradata not working with SSO/IWA

RupaJ — Mon, 19 Nov 2018 21:08:20 GMT

Thanks @SimonDawson. It was an issue of not adding the main DSN to the Teradata keytab file. Once that was modified, the issue resolved. Thanks for your inputs on trying to login with bteq. That was very helpful in determining the root cause.

Re: SAS connectivity to Teradata not working with SSO/IWA

SimonDawson — Mon, 19 Nov 2018 21:24:24 GMT

Glad to hear your Teradata system administrators were able to get to the bottom of it.