Hi Folks,
We have a development SAS Server (9.4) on Linux. The server was stopped for some time (all SAS services were down). During that time the license expired.
Now, we need to re-enable the server for some tests. So, we renewed the SAS license using option 5 from SAS Deployment Manager and it applied correctly. The problem is when we tried to update the SID on MetadataServer (it's the same server). If we tried to run option 6 from SAS Deployment Manager, an error appears because the MetadataServer is not up. If we tried to start the Metadata Server (using metadataserver.sh script) the license expired message appears and the MetadataServer doesn't start.
Is there any parameter we can use with metadataserver.sh script to inform the path of the license file?
Regards,
Back in the day with earlier SAS releases this used to be the way to fix this: https://support.sas.com/techsup/notes/v8/10/269.html
Don't know if this is still possible with SAS 9.4 but there is no harm in trying. You will need to login into the metadata server with a user account with admin privileges. Failing that Tech Support should be able to help.
EDIT: Actually, you should run Deployment Manager on the metadata server and run option 5 there as well. In your case since it is on the same machine navigate to your SAS metadata software HOME directory and run this:
SASHOME/SASDeploymentManager/9.4/sasdm.sh
Once that is done try restarting the metadata server services.
The SID file is a large text file; open it with a text editor, and locate the PROC SETINIT code. Extract the code text (from proc setinit; to run;), and save it as a separate text file.
Then execute this text file, using the path of the SAS executable as found in the metadata server script:
/path_to_executable/sas -setinit path_to_your_setinit.sas
The -setinit option forces SAS to start even if the license is expired, but you can only run the SETINIT procedure.
Thanks @Kurt_Bremser .
As mentioned, we have one server only, it's Linux with SAS 9.4M7 installed. So, as you mentioned, we run the following command:
/sas/software/SASFoundation/9.4/sas sas -setinit /sas/setinit.sas
After that, we verified the log and the setinit procedure executes fine. Then, we tried to start the MetadataServer by running the following command:
/sas/config/Lev1/SASMeta/MetadataServer/MetadataServer.sh start
But the same error occurs:
Waiting up to 600 seconds for Metadata Server to listen to port 8561.
Server is started (pid 7176)...
Server is stopped
Log files are located at: /sas/config/Lev1/SASMeta/MetadataServer/Logs
When we validated the log file, the error appears:
ERROR: includes SETINIT information.
ERROR: Initialization of setinit information from SASHELP failed.
ERROR: (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED.
ERROR: Unable to initialize the SAS kernel.
ERROR: The current date of Tuesday, May 23, 2023 is past the final expiration date for your SAS system, which is Tuesday, March 1, 2022. Please contact your SAS Installation Representative to obtain your updated SAS Installation Data (SID) file, which
ERROR: includes SETINIT information.
The setinit file we are using is:
Site validation data before saving/zapping
Current version: 9.04.01M7P080620
Site name: 'XXXXXXXXXX'.
Site number: 00000000000.
CPU A: Model name='' model number='' serial=''.
Expiration: 29NOV2023.
Grace Period: 45 days (ending 13JAN2024).
Warning Period: 45 days (ending 27FEB2024).
System birthday: 02FEB2023.
Operating System: LIN X64 .
Product expiration dates:
---Base SAS Software 29NOV2023 (CPU A)
---SAS/STAT 29NOV2023 (CPU A)
---SAS/GRAPH 29NOV2023 (CPU A)
---SAS/ETS 29NOV2023 (CPU A)
---SAS/OR 29NOV2023 (CPU A)
---SAS/AF 29NOV2023 (CPU A)
---SAS/IML 29NOV2023 (CPU A)
---SAS/SHARE 29NOV2023 (CPU A)
---SAS/CONNECT 29NOV2023 (CPU A)
---SAS/SHARE*NET 29NOV2023 (CPU A)
---SAS Risk Management 29NOV2023 (CPU A)
---SAS Enterprise Miner 30MAY2023 (CPU A)
---SAS Risk Management-Enterprise Edition 29NOV2023 (CPU A)
---External function linking system 29NOV2023 (CPU A)
---SAS Integration Technologies 29NOV2023 (CPU A)
---SAS/Secure 168-bit 29NOV2023 (CPU A)
---SAS Enterprise Miner Server 30MAY2023 (CPU A)
---SAS Enterprise Miner Client 30MAY2023 (CPU A)
---SAS Credit Scoring 30MAY2023 (CPU A)
---SAS High-Performance Forecasting 29NOV2023 (CPU A)
---SAS Enterprise Guide 29NOV2023 (CPU A)
---OR OPT 29NOV2023 (CPU A)
---OR PRS 29NOV2023 (CPU A)
---OR IVS 29NOV2023 (CPU A)
---OR LSO 29NOV2023 (CPU A)
---SAS/ACCESS Interface to Oracle 29NOV2023 (CPU A)
---SAS/ACCESS Interface to PC Files 29NOV2023 (CPU A)
---SAS/ACCESS Interface to ODBC 29NOV2023 (CPU A)
---SAS/ACCESS Interface to R/3 29NOV2023 (CPU A)
---SAS/IML Studio 29NOV2023 (CPU A)
---SAS Workspace Server for Local Access 29NOV2023 (CPU A)
---SAS Workspace Server for Enterprise Access 29NOV2023 (CPU A)
---SAS/ACCESS to Postgres 29NOV2023 (CPU A)
---SAS Firmwide Risk Management for Insurance 29NOV2023 (CPU A)
---High Performance Suite 29NOV2023 (CPU A)
---SAS Add-in for Microsoft Excel 29NOV2023 (CPU A)
---SAS Add-in for Microsoft Outlook 29NOV2023 (CPU A)
---SAS Add-in for Microsoft PowerPoint 29NOV2023 (CPU A)
---SAS Add-in for Microsoft Word 29NOV2023 (CPU A)
---SAS High-Performance Risk Engine Server 29NOV2023 (CPU A)
---SAS Search and Indexing Server 29NOV2023 (CPU A)
---SAS Web Crawler Server 29NOV2023 (CPU A)
---Business Rules Services 29NOV2023 (CPU A)
---SAS LASR Analytic Server 29NOV2023 (CPU A)
---SAS Visual Analytics Hub 29NOV2023 (CPU A)
---SAS Visual Analytics Services 29NOV2023 (CPU A)
---High Performance STAT MPP 29NOV2023 (CPU A)
---Decision Manager Server 29NOV2023 (CPU A)
---Advanced Programming for LASR Analytic Server 29NOV2023 (CPU A)
---High Performance Analytics Distributed Mode 29NOV2023 (CPU A)
---SAS Visual Analytics Server Components 29NOV2023 (CPU A)
---Bus Rules Manager Server 29NOV2023 (CPU A)
---Stress Testing Server 29NOV2023 (CPU A)
---Visual Analytics Explorer 29NOV2023 (CPU A)
---Model Imp Mgmt Server 29NOV2023 (CPU A)
---Model Implement Pltfrm Adv 29NOV2023 (CPU A)
---SAS/ACCESS to Google BigQuery 29NOV2023 (CPU A)
NOTE: Siteinfo data have been updated.
I also open a SAS Ticket (7613820055).
EDIT: SASFoundation look ok! Now you have to update Metadata license with SAS Deployment Manager as you were trying before.
Hi @MarcoGhiglieri ,
Yes, the Foundation looks fine, but the problem is exactly the update SID for Metadata. If we tried to execute option 6 from SAS Deployment Manager, we have an error saying the MetadataServer is not up or running.
So, when we tried to start the metadata server using the metadataserver.sh script, we received the following error:
Waiting up to 600 seconds for Metadata Server to listen to port 8561.
Server is started (pid 7176)...
Server is stopped
Log files are located at: /sas/config/Lev1/SASMeta/MetadataServer/Logs
And the log for the metadata services is:
ERROR: includes SETINIT information.
ERROR: Initialization of setinit information from SASHELP failed.
ERROR: (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED.
ERROR: Unable to initialize the SAS kernel.
ERROR: The current date of Tuesday, May 23, 2023 is past the final expiration date for your SAS system, which is Tuesday, March 1, 2022. Please contact your SAS Installation Representative to obtain your updated SAS Installation Data (SID) file, which
ERROR: includes SETINIT information.
So, at this moment we have the SAS Foundation ok but we can't find a way to update the SID on metadata.
Oh, didn't get it.
This is strange:
ERROR: The current date of Tuesday, May 23, 2023 is past the final expiration date for your SAS system, which is Tuesday, March 1, 2022. Please contact your SAS Installation Representative to obtain your updated SAS Installation Data (SID) file, which ERROR: includes SETINIT information.
Are you getting the latest log? Host date/time is ok?
It's very strange, @MarcoGhiglieri .
Yes, the return of date command is:
Wed Jul 5 13:24:26 GMT 2023
In fact, in the setinit log appears ok too:
1 The SAS System 12:58 Wednesday, July 5, 2023
NOTE: Copyright (c) 2016 by SAS Institute Inc., Cary, NC, USA.
NOTE: SAS (r) Proprietary Software 9.4 (TS1M7)
Licensed to XXXXXXXXXXX, Site 0000000.
NOTE: This session is executing on the Linux 4.1.12-124.48.6.el6uek.x86_64 (LIN X64) platform.
@MarcoGhiglieri , you are right. I was looking at the general MetadataServer log. So, I verified the log of metadata for today and now I'm seeing a different error:
2023-07-05T11:53:28,960 ERROR [00000005] :sas - Unable to obtain IP addresses for host sasdev.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
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.