SAS 9.3 License Renewal not reflecting in SASGSUB

[SASWayne]

Hello,

I have renewed license of our SAS 9.3M2 grid environment using the SAS license renewal utility for SAS 9.3 and we can see the new license expiry date in SAS foundation and SAS EG. However, SASGSUB shows the license expiry notification still.

Could someone help with this issue?

Thanks in advance! 

[SASKiwi]

Which SAS server did you run the utility on? All SAS App server nodes and the SAS metadata server would need their licences updated.

[SASWayne]

I applied license on Metadata and grid nodes as well using the renewal utility. Also, from SAS EG, I don't see the license expiry notification.

[SASKiwi]

Are you by any chance using IBM's Platform Process Manager for grid management? If so that has a separate licence and renewal process.

[SASWayne]

@SASKiwi
Yes, we have IBM platform process manager. I have placed the new license.dat under ppm\conf network path and started LSF services. Is there any additional step to be performed for SAS 9.3?

[SASKiwi]

@SASWayne  - The PPM licence file also needs to be copied to the LSF conf folder.

[SASWayne]

yes, I have placed it under lsf conf as well.

[SASKiwi]

@SASWayne  - That's all you need to do for PPM AFAIK. Best to open a Tech Support track if you haven't already. There are probably not too many SAS sites still running Grid 9.3. 

[gwootton]

Was the license updated on the host where SASGSUB is being run?

[SASWayne]

Hi ,
We use citrix to run client applications from where we use sasgsub. We haven't applied any license in citrix.
I tried to submit proc setinit; through SASGSUB from the grid server itself where we renewed SAS license and still see license expiry notification in the command prompt. However, the output log for the job shows new expiry date. This seems weird.

[gwootton]

Looks like SASGSUB (SAS Grid Manager Client Utility) uses the SID file in Metadata:

Usage Note 49750: To extend the expiration date for particular SAS® solutions and products, you must perform the "Update SID File in Metadata" task
https://support.sas.com/kb/49/750.html

[SASWayne]

Hi @gwootton
Thank you for the link. I think there is the catch. When I tried update sid file in Metadata, I see an encountered error message from the deployment manager which is pointing out to cfgwizard_config.xml in one of SAS deployment manager's subfolders. It also points out a log file within Lev1\logs\Configure to know more information, unfortunately, I cannot find the log in specified path. I have raised a SAS track for this as well, wish someone could pick it up quickly.
Do you have any idea about the error message?

[gwootton]

Do you see any logs in the path that correspond with your attempt? Does the Event Viewer have any corresponding errors? Does your execution user have permission to write to that log path?

[doug_sas]

SASGSUB will look in metadata for the license or it can use a license file via the GRIDLICENSEFILE option.

The license in metadata is updated via the SAS Deployment Manager's 'Update SID File in Metadata' option under the 'Administrative Tasks' task group.

Make sure you are updating the license in metadata for the metadata server that SASGSUB is pointing to in its SASGSUB.CFG file. The config file is in the <config>/<LevX>/Applications/SASGridManagerClientUtility/9.3 directory which should be the same location that the sasgsub script is run from.

[SASWayne · Accepted solution]

I know this is a very delayed update - the issue was fixed with the help of SAS Support. We had to launch the deployment manager using the JRE option that points to the java path within SASHome via command line and then updated SID file to metadata.