- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hi All,
Hope Doing Good !!
Our UAT environment is a single layer architecture with the combination of Meta,Mid and Compute servers. And also with the installed client tools SAS DI,EG,SMC,LSF,SPDS in windows 2012 R2 OS.
All of sudden we are facing issue with the Connectivity with SAS App server from our SAS applications. So that we checked the Services where Object spawner is not running. So that we stopped the services in defined order and trying to start. Metadata service is not getting started hence we killed all orphan SAS related programs by using Task manager and again trying. Still not able to start services.
We have 2 levels in our UAT environment. In both levels all services including metadata are not starting.
Please help us in resolving this issue. Earliest response might be appreciated.
Bunch of Thanks in Advance !!.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Have you verified the validity of your sas licence ? if the licence is past the grace period the services might not start.
Try running this code on the server on the Server if Foundation SAS is installed or check the licence files.
proc setinit;
run;
Look for this information.
Grace Period: 13 days (ending 14JUN2019). Warning Period: 16 days (ending 30JUN2019).
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Contacting tech-support is highly recommended. Maybe another service is blocking the port used by the metadata server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Have you verified the validity of your sas licence ? if the licence is past the grace period the services might not start.
Try running this code on the server on the Server if Foundation SAS is installed or check the licence files.
proc setinit;
run;
Look for this information.
Grace Period: 13 days (ending 14JUN2019). Warning Period: 16 days (ending 30JUN2019).
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Many Thanks Both of you !!
Your suggestions worked well. We got the route case of the issue and we resolved it. Everything is working fine now.
Regards,
Lakshmi.