01-22-2018 02:05 AM
I am unable to use SAS FEDSQL and DS2 against SQL Appliances that have been connected to using SAS ACCESS/ODBC. I keep getting ERROR: TKTS initialization failed. We don't have the Federation Server licence, hoping it is not required.
01-22-2018 08:14 AM
Did you already do a google search for "ERROR: TKTS initialization failed"? If not, there might be hints in the quite numerous results.
01-22-2018 05:22 PM
Google doesn't provide any detailed information. The basic examples that I have used for FEDSQL and DS2 work when using SAS data on the server. However, it fail with the TKTS error. I have noticed that the TKTS error seems to be very general and not specific. I am so used to specific error messages in the SAS log. DS2 and FEDSQL error messaging needs to be improved.
Note: Using SAS 9.4m3 and SAS/ACCESS to ODBC to connect to a Postgresql Database.
01-22-2018 08:49 PM
You shouldn't need a Federation Server licence for this - I suspect there may be something wrong with your ODBC connection.
Are you able to successfully connect and run some "old school" SAS i.e. not DS2 code against the data source using the same connection string?
01-23-2018 02:21 AM
I have successfully ran PROC SQL and DATA steps against the ODBC connection without issue, just the DS2 and FEDSQL giving problems. As mentioned I know the FEDSQL and DS2 code that I have ran is good as I changed the input and out put libraries to SAS locations and it works really well.
Forgot to mention that SAS is being ran on Red Hat Linux in AWS and using a AWS RDS Postgresql Database.
ODBC connection details I have set are:
Driver = PostgreSQL
Description = PostgreSQL Data Source
Servername = xxxxxxxx-server-location-xxxxxxxx
Port = 5432
Protocol = 7.4
Database = riskindex_poc
SSLMode = require
SSLKeyFile = /apps/unixodbc/etc/rds-combined-ca-bundle.pem
MaxLongVarcharSize = 32767