BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
sathya66
Barite | Level 11

All,

I am running this code from SAS EG to upload one table to caslib=casuser

It was working fine before.

this is happening only after installing new hotfixes on our machines. do we need to look for any files to get it work.

I found this is very usefull but we are on Linux and also user name is 8 characters or less and the password is 15 characters or less

https://support.sas.com/kb/66/487.html

 

sas94 and viya are on diffrent servers.

 

options cashost="test.com" casport=5570; 
cas mysession sessopts=(caslib=casuser timeout=1800 ); 
cas;                   /* log on to the CAS session */
   caslib _all_ assign;   /* create a libref for each active 
                             caslib */

 

 

options cashost="test.com" casport=5570;
29 cas mysession sessopts=(caslib=casuser timeout=1800 );
ERROR: Connection failed. Server returned: SAS Logon Manager authentication failed: Access denied.
ERROR: Unable to connect to Cloud Analytic Services test.com on port 5570. Verify connection
parameters and retry.
30 cas;
ERROR: Connection failed. Server returned: SAS Logon Manager authentication failed: Access denied.
ERROR: Unable to connect to Cloud Analytic Services test.com on port 5570. Verify connection
parameters and retry.
30 ! /* log on to the CAS session */
31 caslib _all_ assign;
ERROR: A connected session is required to complete the Caslib request. Session CASAUTO identified by the option SESSREF= is not
connected. Start the session or reconnect to the session.

1 ACCEPTED SOLUTION

Accepted Solutions
sathya66
Barite | Level 11
Self signed certificates are expired so we updated the certs and working fine now.
see below.
https://communities.sas.com/t5/SAS-Communities-Library/How-to-survive-SAS-Viya-self-signed-certifica...

View solution in original post

6 REPLIES 6
sathya66
Barite | Level 11

And Just checked cas services are UP and running but cas-shared-default server status (port:-5570) is not in green in environment manager.
And SAS studioV is also not working.

Welcome to SAS® Studio
Unable to create compute server session. Failed to launch process. Failed to launch process: host=test.com port=37510 ssl=true Failed to connect to server. Server error: status=0x8BFFC00C messages=[Failed to authenticate to Launcher Server.]

sathya66_0-1601494026394.png

 

sathya66
Barite | Level 11
Self signed certificates are expired so we updated the certs and working fine now.
see below.
https://communities.sas.com/t5/SAS-Communities-Library/How-to-survive-SAS-Viya-self-signed-certifica...
ehsanullah
Calcite | Level 5

Hi

 

How are you ?

 

Were you able to resolve the issue?

 

We are facing similar issue.

 

If some guidance would be provided we will appreciate it .

 

Regards

SAS Customer

sathya66
Barite | Level 11
Hi,
I resolved it by updating the certs.
are you getting the same ERROR?
if yes, then follow link below
https://communities.sas.com/t5/SAS-Communities-Library/How-to-survive-SAS-Viya-self-signed-certifica...
ehsanullah
Calcite | Level 5

No this is not the issue:

 

Here are my logs:

 

2021-04-28 12:16:46.390  INFO 113082 --- [TaskScheduler-1] o.s.boot.SpringApplication               : service The following profiles are active: prod,postgresql

2021-04-28 12:16:46.409  INFO 113082 --- [TaskScheduler-1] o.s.boot.SpringApplication               : service Started application in 0.543 seconds (JVM running for 89.229)

2021-04-28 12:16:46.927  INFO 113082 --- [TaskScheduler-1] o.s.c.e.event.RefreshEventListener       : service Refresh keys changed: []

2021-04-28 12:16:48.704  INFO 113082 --- [    bootstrap-3] c.s.s.oauth2.bootstrap.ClientRegisterer  : service [a8b507ca59756d45] [CLIENT_ALREADY_REGISTERED] OAuth client sas.launcher already registered with server.

2021-04-28 12:17:01.023  INFO 113082 --- [1-auto-1-exec-7] c.s.s.o.token.JwtAccessTokenConverter    : service [036212e834f99ead] [TOKEN_SIGNATURE_ALG] Server is generating token signatures using RS256.

2021-04-28 12:18:03.539 ERROR 113082 --- [1-auto-1-exec-2] com.sas.launcher.tklauncher.TKClient     : <username> [7645c049548f253c] [CLIENT_CONNECT_ERROR] Failed to connect to server: Kerberos handshake error.

2021-04-28 12:18:03.550 ERROR 113082 --- [1-auto-1-exec-2] com.sas.launcher.tklauncher.TKClient     : <username> [7645c049548f253c] [CLIENT_LAUNCH_ERROR] Failed to launch process: server=TKServer{id='sas-viya-launcher-server-default:sas-viya-host', name='launcher-server', type=ServerType{name='launcher'}, state=ServerState{name='up'}, host=Host{name='sas-viya-host'}, port=Port{port=25631}, operatingSystem=OperatingSystem{name='linux', pathSeparator='/', installBasePathPropertyName='sas.launcher.deployment.linux.install-base-path', configBasePathPropertyName='sas.launcher.deployment.linux.config-base-path', scriptExtensionPropertyName='sas.launcher.deployment.linux.script-extension'}, gridEnabled=false, environment=Environment{{SASMAKEHOMEDIR=1, SAS_SERVICE_PRINCIPAL=sas-launcher/host@domain}}, sasDeploymentProperties=SASDeploymentProperties{sasServicesUrl=SASServicesUrl{url=https://sas-viya-host:443/}, sasDeploymentId='viya', sasHome='/opt/sas/viya/home', sasConfig='/opt/sas/viya/config', spreHome='/opt/sas/spre/home', sasInstanceId='default'}, consulUrl=ConsulUrl{url=https://localhost:8501}, vaultUrl=VaultUrl{url=https://sas-viya-host:8200/}, sslEnabled=true, sslCAList='/opt/sas/viya/config/etc/SASSecurityCertificateFramework/cacerts/trustedcerts.pem', sslCertificate='/opt/sas/viya/config/etc/SASSecurityCertificateFramework/tls/certs/tklauncher/default/certificate.pem', sslPrivateKey='/opt/sas/viya/config/etc/SASSecurityCertificateFramework/tls/certs/tklauncher/default/key.pem', spn=ServicePrincipalName{value='sas-launcher/sas-viya-host'}} cause=Failed to connect to server.

2021-04-28 12:18:03.584 ERROR 113082 --- [1-auto-1-exec-2] com.sas.commons.rest.ExceptionLog        : <username> [7645c049548f253c] com.sas.commons.rest.exceptions.ResourceException: Failed to launch process.

2021-04-28 12:18:03.585 ERROR 113082 --- [1-auto-1-exec-2] com.sas.commons.rest.ExceptionLog        : <username> [7645c049548f253c]   caused by: com.sas.launcher.tklauncher.ClientException: Failed to launch process: host=sas-viya-host port=25631 ssl=true

2021-04-28 12:18:03.585 ERROR 113082 --- [1-auto-1-exec-2] com.sas.commons.rest.ExceptionLog        : <username> [7645c049548f253c]   caused by: com.sas.launcher.tklauncher.ClientException: Failed to connect to server.

2021-04-28 12:18:03.585 ERROR 113082 --- [1-auto-1-exec-2] com.sas.commons.rest.ExceptionLog        : <username> [7645c049548f253c]   caused by: com.sas.launcher.error.LauncherRuntimeException: Kerberos handshake error.

                                                                                                                                                                                                 

jcFranklin
SAS Employee

@ehsanullah the issue you are facing is a kerberos handshake issue. I would suggest working through the troubleshooting steps found in this blog: https://communities.sas.com/t5/SAS-Communities-Library/SAS-Viya-3-5-Kerberos-Troubleshooting/ta-p/63... After that, if you still cannot find the issue, I would suggest opening up a SAS Technical Support ticket for assistance going through your kerberos configuration to see where the issue is coming from. 

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 6 replies
  • 13447 views
  • 4 likes
  • 3 in conversation