The type of error returned for an unsupported Java version would be something like this: >>> sas = saspy.SASsession(cfg='winlocal') Using SAS Config named: winlocal Java Error: java.lang.UnsupportedClassVersionError: pyiom/saspy2j : Unsupported major.minor version 51.0   The type of error you're getting: Java Error: java.lang.NoClassDefFoundError: com/sas/services/connection/ConnectionFactoryException indicates an issue with the class paths to the jars rather than the version of Java.   Verify that the class paths in the sascfg.py file are correct. The default paths to the jars under the SASDeploymentManager install directory included in the file almost certainly need to be updated for the maintenance release of SAS running at your site. For example, I had to update mine to reference the correct deploywiz__<version>__ for my SAS release as follows: # build out a local classpath variable to use below for Windows clients cpW = "C:\\Program Files\\SASHome\\SASDeploymentManager\\9.4\\products\\deploywiz__94502__prt__xx__sp0__1\\deploywiz\\sas.svc.connection.jar" cpW += ";C:\\Program Files\\SASHome\\SASDeploymentManager\\9.4\\products\\deploywiz__94502__prt__xx__sp0__1\\deploywiz\\log4j.jar" cpW += ";C:\\Program Files\\SASHome\\SASDeploymentManager\\9.4\\products\\deploywiz__94502__prt__xx__sp0__1\\deploywiz\\sas.security.sspi.jar" cpW += ";C:\\Program Files\\SASHome\\SASDeploymentManager\\9.4\\products\\deploywiz__94502__prt__xx__sp0__1\\deploywiz\\sas.core.jar"  ... View more

As @Kurt_Bremser correctly mentions in his reply, the limitation of configuring SAS Token Authentication is that you lose granularity of host access on the workspace servers. You'll need to be very aware of the privileges assigned to the service account on the host operating system - if it's configured to have generous privileges, than any user's workspace server session will also have that generous access to the host OS (although you can apply some access restrictions via SAS metadata).    I'm interested in understanding the business value / reason behind the type of configuration you are asking about. Can you give us more info about why this configuration is desired at your site? ... View more

SAS Studio does not currently offer a way to hide folders in the directory tree that a user doesn't have access to because the file navigation interface functions in the same manner as Windows Explorer where users can see folders even if they cannot access them. As a workaround, you can set the custom root path to each individual user's directory using the <userid> token in the path (ex. set the custom root path to G:\Data\Users\<userid>). Then if users also need to access other directories on the G:\ drive, create global folder shortcuts to each of the directories every user needs access to. This will effectively "hide" the other user directories that users do not have access to in G:\Data\Users\ from the SAS Studio interface.   See SAS® Studio 3.71: Administrator’s Guide > SAS Studio Mid-Tier > Working with SAS Workspace Servers > How to Set Up Different Root Directories and SAS® Studio 3.71: Administrator’s Guide > Configuration Properties for SAS Studio > Configuring Global Folder Shortcuts for more information.   If you'd like to request the ability to hide folders in the SAS Studio navigation panel, create a post in the SASWare Ballot Community.  ... View more

Instructions for updating SAS 9.4 to a later maintenance release are in the SAS® 9.4 Guide to Software Updates document. Not all sections may apply to your type of installation, but it's best to review the whole document so you can determine the best approach for updating SAS software at your site.   Here's a broad overview of the process: Download the new SAS 9.4M5 order. You can download it to the existing SAS Software Depot (containing the 9.4M3 order) or you can create a new depot. The benefit of downloading it to the existing depot is that only updated files will need to be downloaded - any depot files that did not change between M3 and M5 will not need to be downloaded, meaning that the download time can be reduced. Make sure you have prepared the environment as outlined in SAS® 9.4 Guide to Software Updates, including creating usable backups in order to restore customization after the update has been applied. This is essential for planned deployments. Follow this page of instructions to apply the update. ... View more

The free SAS Platform Administration: Getting Started course is a good place to start learning SAS administration. Check out the SAS Platform Administration Learning Path for other available courses. If you decide you would like to become a SAS administrator, it's well worth it to get certified.    ... View more

A good starting place to debug this issue is to ping sasmd.abcd.local on port 7081 outside of SAS to make sure it's open and accessible to incoming requests. If you can't ping that port, you'll need to open it up on the server. Take a look at the SAS® 9.4 Intelligence Platform: Installation and Configuration Guide > Setting Up Users, Groups, and Ports > Designating Ports and Multicast Addresses to make sure that you have set up the ports on the server as outlined.   A few other troubleshooting steps to start with: Environment Manager is configured on port 7080 by default so if you did not perform the install, make sure you are getting the URL for Environment Manager from sas-config/Lev1/Documents/Instructions.html to confirm that you are connecting on the correct port. Make sure that the Environment Manager server is running as well as the agent. Both of these services must be started with the SAS installer account on Linux deployments.  If you can ping the port and all the services are running as expected, then open a ticket to technical support to request assistance.  ... View more

Hi Sébastien,    Darn, I was hoping you were NOT using SAS Studio Single User because it's more complicated to change the launch parameters due to the architecture of that application. I'll think about this and do some testing over the next few days and let you know when I have more information to share with you.    I'll also check into your other question regarding the missing lines in the log.   Thanks, Shayne ... View more

Here are instructions to enable XCMD on SAS Studio Basic if your IT will allow it:  SAS Studio Administrator's Guide > SAS Studio Basic > Enabling the X Commands   Essentially the admin of the instance will need to recreate the spawner service with the -allowxcmd option.  ... View more

What edition and version of SAS Studio are you running, and what operating system (OS) is hosting SAS Studio? You can find this from within SAS Studio by clicking on the ? icon in the upper right corner and selecting "About SAS Studio". The Release field will tell you the version / edition, and the SAS Platform field will tell you the OS.   Editions of SAS Studio that use a workspace server (Basic and MidTier) process the autoexec file before executing application initialization code, and the application initialization code for SAS Studio sets all of the options that you mention in your post. So any settings you specify in your autoexec file will be overwritten by the application initialization code. There are a few ways around this but they differ by edition / version of SAS Studio.    For example, in SAS Studio Basic edition, these options are set on the spawner and they can be modified by recreating the service / process with the desired options. If you are using SAS Studio Basic, you can use these instructions as a template for how to change the options on the spawner: SAS Studio Administrator's Guide > SAS Studio Basic > Enabling the X Commands. Note that this change will affect all users.   SAS Studio MidTier edition works a bit differently - let me know if you are using MidTier and I'll post different instructions (or if you are using SAS Studio Single User...).  ... View more