BookmarkSubscribeRSS Feed
Super User

I have no clue what "obtained different version" might mean but SAS license keys have been tied to versions very closely for a long time and I would not expect a license for Release: 20231028.(anything) to work with Release: 20231028.(something else) in general.

Fluorite | Level 6
Different Version is
Version: Stable 2023.12
Release: 20231223.1703296163239
Fluorite | Level 6

We have downloaded the deployment package named "SASViyaV4_9CX9K5_0_stable_2023.10_20231028.1698456203725_multipleAssets_2023-10-30T124407" which contains deployment assets and a license key. Using Kubernetes commands, we successfully deployed the software and applied the provided license key.


Subsequently, due to the expiration of the license key, we obtained a new deployment package named "SASViyaV4_9CX9K5_1_stable_2023.10_20240104.1704333550501_multipleAssets_2024-01-04T181205"  which contains deployment assets and a license key. Extracted the license key from this package, we attempted to apply it. However, the updated license key did not take effect, and the system still reflects the previous license's expiration status.


We have followed all the steps mentioned in the document(SAS Help Center: How to Apply a New License). 


Observation 1:

The last numbers highlighted in RED are different in Old vs New Deployment Package:

NEW deployment Package: SASViyaV4_9CX9K5_1_stable_2023.10_20240104.1704333550501_multipleAssets_2024-01-04T181205

OLD deployment Package: 


  • The numbers highlighted in Blue appear to represent the download date of the package, and we expect them to vary.
  • The numbers highlighted in Red are uncertain in their significance, and we are unsure whether they should match. Additionally, we are uncertain if a package with a specific number corresponding to the old package is available for download.


Observation 2:

It seems that renewing the license key only requires the .JWT file, yet the package includes both deployment assets and the .JWT license key. There might be something overlooked in this process.


Could you please suggest on this?


@Narendra_P  - moved your post to a more relevant area where experts like @gwootton are very responsive.

When downloading from the SAS portal or API you can choose the deployment assets (sas-bases), certificates, or license. To update the license you only need the license JWT file. To apply that license you update your kustomization.yaml to point to the new license file as described in the linked documentation, and then redeploy using the original deployment method. The path referenced would be relative to the kustomization.yaml file. This should result in the license file in the sas-license secret containing the contents of the new JWT.

The numbers you're talking about in red and blue are the cadence release version as a cadence can be updated after its initial release, this would not typically have bearing on the license.
Greg Wootton | Principal Systems Technical Support Engineer
Fluorite | Level 6

I am attempting to establish a connection to Oracle data using SAS Studio and encountering the following issue:

ERROR: ORACLE connection error: ORA-12170: TNS: Connect timeout occurred.
ERROR: Error in the LIBNAME statement.


Could you please suggest on this?



Please locate the environment variables I've configured below:


Tried both:




Please locate the following sample content in the tnsnames.ora file:



Obsidian | Level 7

Check with your Kubernetes engineer that the firewall rule is opened to your Oracle server with specific port no.

It is the exact tnsnames.ora you are using? Does the connection is in secure connection mode or configured with Oracle wallet?

This should probably be a new topic (and this topic should be marked as solved if your license issue is resolved).

Generally speaking a connection timeout means that we do not have a network path to the database server, so we send a connection request that never receives a reply, so firewall issues are the most likely cause.
Greg Wootton | Principal Systems Technical Support Engineer

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 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 7 replies
  • 1 like
  • 5 in conversation