BookmarkSubscribeRSS Feed
MG18
Lapis Lazuli | Level 10

Hi team , 

 

Our SAS licenses expire don 28 Feb and licenses were not able to supplied till 6 March .

I am getting below error while updating the applying the Licenses ( Update SID file in Metadata).

Does any one know how to fix this issue ?

[exec]
[exec] The ' characters around the executable and arguments are
[exec] not part of the command.
[exec]
[exec] ERROR: The current date of Wednesday, March 6, 2024 is past the final
[exec] ERROR: expiration date for your SAS system, which is Wednesday, February 28,
[exec] ERROR: 2024. Please contact your SAS Installation Representative to obtain
[exec] ERROR: your updated SAS Installation Data (SID) file, which includes SETINIT
[exec] ERROR: information.
[exec] To locate the name of your SAS Installation Representative go to
[exec] http://support.sas.com/repfinder and provide your site number 70305508 and
[exec] company name as RSA INSURANCE GROUP PLC NON PROD METADA NODE. On the SAS REP
[exec] list provided, locate the REP for operating system LIN X64.
[exec] ERROR: Initialization of setinit information from SASHELP failed.
[exec] NOTE: Unable to initialize the options subsystem.
[exec] ERROR: (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED.
[exec] ERROR: Unable to initialize the SAS kernel.
[exec] Result: 115

BUILD FAILED
/sas/meta/software/SASDeploymentManager/9.4/products/cfgwizard__94568__prt__xx__sp0__1/Utilities/configuration_targets.xml:605: The following error occurred while executing this line:
/sas/meta/software/SASDeploymentManager/9.4/products/cfgwizard__94568__prt__xx__sp0__1/Utilities/configuration_scripts.xml:4293: /tmp/_setup16/getSystemOption.output doesn't exist

4 REPLIES 4
Sajid01
Meteorite | Level 14

Hello @MG18 
The error message is clear.
Suggest that you contact SAS Tech Support if you have a valid sid file.

SASKiwi
PROC Star

You need to use SAS Deployment Manager and do the "Renew SAS Software" licence first on your SAS metadata and SAS app servers first if you haven't already:

SASKiwi_0-1709758639144.png

 

 

Kurt_Bremser
Super User

The message comes from a failed try to start the SAS system.

If you dare, you can try this:

Open the sid file (it's just one big text file) with a text editor.

Locate the PROC SETINIT code. It starts with the PROC SETINIT statement and ends with a RUN statement.

Copy/paste the code into its own file, name it setinit.sas.

From the operating system commandline, run (as the SAS install user!)

sas -setinit -sysin /complete_path/setinit.sas

You might also need to supply the complete path to the SAS executable.

ballardw
Super User

Another possible dirty trick that might work is to reset your computer system clock to a date of 28 Feb or early to run the install.

Maybe.

You might have to disable network connections to keep the system clock from resetting. Which means that all of the files needed for the install have to be located on the running computer.

 

 

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
  • 4 replies
  • 808 views
  • 7 likes
  • 5 in conversation