For #1, see if you can change them with https://go.documentation.sas.com/?cdcId=calcdc&cdcVersion=3.3&docsetId=caldatamgmtcas&docsetTarget=n06btniqijz8udn1vtld6ea8lts2.htm&locale=en#p01ovp1zhzb6ejn1qpsms4m3e9fp ... View more

For #2  https://go.documentation.sas.com/?cdcId=calcdc&cdcVersion=3.3&docsetId=calconfig&docsetTarget=n08000sasconfiguration0admin.htm&locale=en#n08049sasconfiguration0admin   You can specify a custom objectFilter      ... View more

the settings put into EV or sitedefault look like they are corrupt, it looks like placeholders have been intermingled with actual values. Have you opened a tech support track? ... View more

not-ready indicates the process is still running, but unhealthy (for a variety of reasons, check the logs for logon) typically it's a problem with the LDAP configuration or access to some other service that's down - however if the only thing in viya-all-services that isn't up is logon, the logs should say what's going on.  ... View more

That path is where the license file exists on the server - so if you're running a remote session via moba, it will need to be copied to the server, rather than relative to your desktop.  ... View more

The email with your new license should've included instructions, but they're also available online: Linux/Unix http://support.sas.com/documentation/installcenter/en/ikunixplannedri/66610/PDF/default/setinit_planned.pdf Windows http://support.sas.com/documentation/installcenter/en/ikwinplannedri/66607/PDF/default/setinit_planned.pdf   ... View more

Have you confirmed the remote display is properly working with another command, like sasmc or jedit/gedit/xeyes ? ... View more

What does it show for logon if you do "sudo service sas-viya-all-services status" - The individual service status commands just report whether or not the server process is online - all-services will check it's endpoint and make sure it's accessible. I'm thinking it says 'not ready' for logon - and if you check the logs for saslogon or identities you'll find an exception of some sort talking to LDAP. ... View more

https://www.sas.com/en_us/certification/resources/certified-professionals-directory.html Is the registry of record. If I login to my account on integral7 I can see a SAS-###### - as my registry ID - maybe that's what people are using? ... View more

It's not a permissions problem.    That's the error message I get if I try to locate the config under an already existing SASHome - do you know if it was one previously (but maybe no longer)?  The sdwpreferences.txt documented here: http://support.sas.com/kb/49/799.html   Will contain a list of the previous paths - if it's no longer used you should be able to remove it, and install there now - but a restart of the SAS Deployment Wizard may be required.      ... View more

http://support.sas.com/documentation/cdl/en/bisag/68240/HTML/default/viewer.htm#n0v5rampodzajbn1w825qtg5lzil.htm " The installer must have Write permission to this path. Do not specify a path that is within the SAS installation directory (for example, SASHome)." is /sas/SAS94MQ your SASHome directory? ... View more

Confirm the plugin is present by checking for the prescence of a directory with META-INF and file sas.framework.picklist.jar inside: SASHome\SASVersionedJarRepository\eclipse\plugins\sas.framework.picklist_903000.0.0.20110518190000_v930   If that exists, it's possible the cache didn't get updated during your update, delete the file SASHome\SASVersionedJarRepository\eclipse\com.sas.app.launcher.cacheFile and try again.  ... View more