02-04-2016 09:56 AM
First of all thank you very much for your time and support
the error is solved and this is the steps
1- Run this script file "generate_boot_scripts.sh"
2- This file will generate "sas.server"
3- Check the the up servers by write this command "sas.servers -status"
4-Restart servers by write this command "sas.servers -restart"
5- The error will be solved
02-04-2016 07:37 AM
02-04-2016 08:11 AM
02-04-2016 08:25 AM
02-04-2016 08:25 AM
If you can not find sas.servers script then run generate_boot_scripts.sh script in that same directory, this script will create sas.servers and then you can check server status
02-04-2016 08:34 AM
server is one tier and here is the status of sas.servers
SAS servers status:
SAS Web Infrastructure Data Server is UP
SAS Data Remediation Data Server is UP
SAS Job Monitor Data Server is NOT up
SAS Metadata Server 1 is UP
SAS Object Spawner 1 is UP
SAS CONNECT Spawner 1 is UP
SAS DIP Job Runner 1 is NOT up
SAS Information Retrieval Studio Server is UP
SAS JMS Broker is UP
SAS Cache Locator Service ins_41415 is NOT up
SAS Web Server is UP
SAS Web App Server SASServer1_1 is UP
SAS Web App Server SASServer12_1 is UP
SAS Web App Server SASServer13_1 is UP
SAS Web App Server SASServer2_1 is UP
SAS Web App Server SASServer7_1 is UP
SAS Web App Server SASServer8_1 is UP
SAS Environment Manager is UP
SAS Environment Manager Agent is UP
02-04-2016 09:05 AM
As per my talk with SAS Folks,
Load content just load some sample datas, It will not configure in SAS Environment,
So if you have no need of sample datas of SAS, then you can go ahead by clicking yes, Same error is faced in CentOS 7, and after click on YES, when installtion is completed, SAS gave no error in its environment.
02-04-2016 09:25 AM
True, but it's nice to have an installation/configuration that has no errors in it, that way if you encounter problems later you can rule out a faulty installation/configuration and don't have to worry about doing it all over again.
Have you tried selecting "Retry" to see if can load the content again? I've seen it happen where there was just a communications error and it worked after retrying (but usually there is something else going on that would prevent it from properly loading sample content).
Need further help from the community? Please ask a new question.