No problem, it's just that adding to some old post wont get visibility and is confusing. I think you just click 'Start New Topic' to create one of these posts. There's not a SASPy category here, I think they want that to go into the Programming->Developers area, but it really doesn't matter. FWIW, you can get direct help on SASPy by opening an issue on the SASPy github site. But since I'm here 🙂 Since you only seem to be using local SAS on your PC, the only required content of your sascfg_personal.py file would be:   ``` SAS_config_names=['winlocal']   winlocal = {'java' : 'C:\\Program Files\\SASHome\\SASPrivateJavaRuntimeEnvironment\\9.4\\jre\\bin\\java.exe', 'encoding' : 'windows-1252', } ```   Did you resolve your etc/hosts file, assuming the problem was #6 in the troubleshooting guide for IOM specific errors?   ... View more

Also, FWIW, I see you're providing your own classpath in your config file. You shouldn't be doing that, as it could cause problems if it's not all exactly right. See the doc here: https://sassoftware.github.io/saspy/configuration.html#attn-as-of-saspy-version-3-3-3-the-classpath-is-no-longer-required-in-your-configuration-file   Thanks, Tom ... View more

Yes, you should create a new post for your issue here rather than add to an old solved one that isn't really related to your issue. But, take a look at #6 here: https://sassoftware.github.io/saspy/troubleshooting.html#iom-specific-errors That's likely to be the problem and solution! ... View more

haha, that's great. You tried what I was typing in before I could post it. Awesome! Yep, I can't connect with those 2 hosts, but I can with the 4 in the first list. So good deal; just gotta get to the right set for your id it seems. Great!   Tom ... View more

Well, even though you're not connecting, that looks like you have it mostly correct. It shows that java was found and worked, i see that my iomhost had the same 3 hosts; don't know where I copied that wrong from; at least the host was right and it connects for me. The hosts have to be the right one for your region, based upon the doc here: https://support.sas.com/ondemand/saspy.html, and it looks like you changed it to be the US region based on that doc. I see there are now 2 us regions (I only remember there being one). Did you try the other?   So, the error you got is: `We failed in getConnection The application could not log on to the server "odaws04-usw2.oda.sas.com:8591". The load balancing object spawner timed out. SAS process has terminated unexpectedly.` which, again, means that you are using the correct configuration, and that java was found and the IOM client (what saspy used java for) was working. The error shows that it just couldn't start up a workspace server for you. I just tried each of the 2 US region lists of iomhost hostnames, and I connected with the one you're trying, yet I got the same error about the object spawner timing out when trying the other set of hosts. So, be sure which region you are supposed to be using, and try each of them to see if you can connect to either. And, if you know you're on the right one, try again if it couldn't connect the first time; could just be a resource/timing issue.   Also, as for the sascfg_personal.py; you're not using that with the code provided; you have the config you are passing in dynamically to the SASsession by passing in that oda dictionary. Python on databricks certainly wont be accessing any files from your PCs C drive. So that file there has no part in this.    If the US region is what you use, try each of the two (even just combine the sets of hosts into one list in your config), since if it fails for one it tries the next in the list - won't hurt to have all of them in case one works. ``` oda = {'java' : '/usr/bin/java', 'iomhost' : ['odaws01-usw2-2.oda.sas.com','odaws02-usw2-2.oda.sas.com', 'odaws01-usw2.oda.sas.com','odaws02-usw2.oda.sas.com','odaws03-usw2.oda.sas.com','odaws04-usw2.oda.sas.com'], 'iomport' : 8591, ... ``` . ... View more

I think what you're trying to do is get to SAS ODA from Databricks, right?   Here’s how I am able to get at ODA from databricks. I expect you can do the same, at least; I don’t have a real account to really store files (sascfg_personal.py, ...) or install packages, like SASPy, that stay there. If you can do that it might be easier than the following.   Submit these in their own cells:   # this is to install saspy, because it’s not there by default pip.main(['install','saspy'])   # now import and see that it’s there import saspy saspy   # I submit this and then delete the cell; so user/pw aren’t visible in the notebook import os os.environ['omruser'] = ‘userid’ os.environ['omrpw']  = ‘pw’   # create a dict for the Configuration Definition (could just code these on SASsession, but this is cleaner looking) oda      = {'java'      : '/usr/bin/java',             'iomhost'   : ['odaws01-usw2.oda.sas.com','odaws01-usw2.oda.sas.com','odaws01-usw2.oda.sas.com'],             'iomport'   : 8591,             'omruser'   : os.environ['omruser'],             'omrpw'     : os.environ['omrpw'],             }   # this will use ‘default’ in the example config, but you overrode everything so it will use IOM remote sas = saspy.SASsession(**oda, display='databricks') sas     When trying to render HTML, you have to use their ‘displayHTML()’ function in each cell you want to render html output. They provide no way for saspy to render it for you, which stinks, but I can’t control that. See issue https://github.com/sassoftware/saspy/issues/462 for more info on that.   So for submitting code that returns html output, you would do this:   res = sas.submit(sascode) print(res[‘LOG’]) displayHTML(res[‘LST’])   Hope this works for you, Tom   ... View more

Looking into this a little deeper, I found a bug in the proc where these early failures are exiting the proc without a failure rc. I've fixed those cases and now &SYSERR is correctly being set when there is a failure. So, once this propagates into whatever release it gets in, you will be able to check &SYSERR to see if the proc failed or not. SYSERR gets set (reset) after each step, while SYSERRTEXT doesn't get reset. That's not the proc behavior, but rather SAS's way it sets, or doesn't, these various macro variables. But, that should be a much cleaner way to programmatically check.   Tom 1? 2? proc python;quit; %put &syserr &syserrortext &sysrc &syscc &syswarningtext; options set=PROC_PYPATH='/bad/path'; /* make it fail */ proc python restart;quit; %put &syserr &syserrortext &sysrc &syscc &syswarningtext; options set=PROC_PYPATH='/usr/bin/python3.5'; /* make it work again */ proc python restart;quit; %put &syserr &syserrortext &sysrc &syscc &syswarningtext; NOTE: Python initialized. Python 3.5.6 (default, Nov 16 2018, 15:50:39) [GCC 4.4.7 20120313 (Red Hat 4.4.7-23)] on linux Type "help", "copyright", "credits" or "license" for more information. >>> NOTE: PROCEDURE PYTHON used (Total process time): real time 1.97 seconds cpu time 0.07 seconds 4? 0 0 0 8? NOTE: Python terminated. NOTE: Previous Python state destroyed. ERROR: Failed to create Python subprocess. NOTE: Python terminated. ERROR: Launch Failed. Cannot execute program "/bad/path", error = 2 (No such file or directory). ERROR: The specified executable module either cannot be located or it is not a valid executable. ERROR: Failed to launch Python sub-process in tkpy extension. NOTE: The SAS System stopped processing this step because of errors. NOTE: PROCEDURE PYTHON used (Total process time): real time 0.07 seconds cpu time 0.01 seconds 9? 1012 Failed to launch Python sub-process in tkpy extension. 0 1012 13? NOTE: Python initialized. Python 3.5.6 (default, Nov 16 2018, 15:50:39) [GCC 4.4.7 20120313 (Red Hat 4.4.7-23)] on linux Type "help", "copyright", "credits" or "license" for more information. >>> NOTE: PROCEDURE PYTHON used (Total process time): real time 1.10 seconds cpu time 0.01 seconds 15? 0 Failed to launch Python sub-process in tkpy extension. 0 1012 17? ... View more

Hey, so there a a couple different things that may help, depending upon what's not set up right for the proc to work. The first thing I do to see if the correct options are set and configured (PROC_PYPATH, lockdown, and if lockdown, both PYTHON and SOCKET being enabled) is to run the following code.   data _null_; x= sysget('PROC_PYPATH'); put 'PROC_PYPATH=' x; x= sysget('VIYA_LOCKDOWN_USER_METHODS'); put 'VIYA_LOCKDOWN_USER_METHODS=' x; run; proc options option=lockdown;run; On a system here, that's set up correctly, I get the following: 80 data _null_; 81 x= sysget('PROC_PYPATH'); put 'PROC_PYPATH=' x; 82 x= sysget('VIYA_LOCKDOWN_USER_METHODS'); put 'VIYA_LOCKDOWN_USER_METHODS=' x; 83 run; PROC_PYPATH=/opt/sas/viya/home/sas-pyconfig/default_py/bin/python3 VIYA_LOCKDOWN_USER_METHODS=PYTHON PYTHON_EMBED SOCKET NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.00 seconds 84 proc options option=lockdown; run; SAS (r) Proprietary Software Release V.04.00 TS1M0 LOCKDOWN Specifies that access to files and certain SAS features will be restricted. This feature is only applicable for a SAS session executing in a batch or server processing mode. NOTE: PROCEDURE OPTIONS used (Total process time): real time 0.00 seconds cpu time 0.01 seconds For cases where something isn't configured right, the error can vary. If LOCKDOWNis set, but PYTHON isn't enabled, the error will be something to the effect of saying the proc can't be run because PYTHON isn't enabled (it won't try to start a subprocess). If SOCKET isn't enabled, but the proc runs, the sd2df() and df2sd() methods will fail and the log from those will have an equivalent error about SOCKET not being enabled while in LOCKDOWN mode. For cases where Python can't start (the path isn't set or wrong, the deployment has issues, whatever), then you'll see something like the error you showed about failing to create the subprocess.   The only way I see to programmatically check, is that the &SYSERRTEXT automatic marco variable has a message in it, while it is blank (empty) when the proc succeded.   proc python;quit; %put &syserr &syserrortext &sysrc &syscc &syswarningtext; options set=PROC_PYPATH='/bad/path'; /* make it fail */ proc python restart;quit; %put &syserr &syserrortext &sysrc &syscc &syswarningtext; 87 proc python;quit; NOTE: Python initialized. Python 3.8.13 (default, Jul 21 2022, 07:19:43) [GCC 8.5.0 20210514 (Red Hat 8.5.0-10)] on linux Type "help", "copyright", "credits" or "license" for more information. >>> >>> 88 %let SAS_workpath = %sysfunc(pathname(work)); NOTE: PROCEDURE PYTHON used (Total process time): real time 1.13 seconds cpu time 0.05 seconds 89 %put &syserr &syserrortext &sysrc &syscc &syswarningtext; 0 0 0 90 91 options set=PROC_PYPATH='/bad/path'; /* make it fail */ 92 93 proc python restart;quit; NOTE: Python terminated. NOTE: Previous Python state destroyed. ERROR: Failed to create Python subprocess. NOTE: Python terminated. NOTE: PROCEDURE PYTHON used (Total process time): real time 0.02 seconds cpu time 0.00 seconds 94 %put &syserr &syserrortext &sysrc &syscc &syswarningtext; 0 Failed to create Python subprocess. 0 0 95 So, you could programmatically check by seeing is &SYSERRTEXT is empty or not after trying 'proc python;quit;'. I wouldn't check for a specific error message, just blank or not.    I hope some of this helps, Tom   ... View more

Have you looked at the instructions/documentation? https://sassoftware.github.io/saspy/configuration.html Where is the SAS deployment you're trying to connect to? Where is your Python deployment? You need to configure SASPy so it knows where SAS is and how to connect to it. Are you able to access whatever SAS deployment you have already, with some other client? ... View more

So, it won't have the windows .exe extension as part if it's filename, but Mac's can still have java installed, it's just the executable you need the path of. it would just be named java, in some directory where it's installed. I don't do 'I' things (Mac's are included in that), so I don't know where it would be installed or how you navigate the file system on that. I googled how to find the path to java on a mac and got this hit: https://stackoverflow.com/questions/15826202/where-is-java-installed-on-mac-os-x along with plenty others. You ought to be able to find it on the filesystem if it's already installed, or just install it and then be able to see where it is. ... View more

Hey, the error you got is about java not being found. https://sassoftware.github.io/saspy/troubleshooting.html#java-problems You show  'java' : '/Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin/Contents/Home', for java, which isn't java, so that's for sure the first problem. Also, I would issue `import saspy' not  `from saspy import SASsession' Not sure where you saw that. Import the package. And set the java config to an actual java.exe (java executable; can't tell if you are on windows or what). You provided an authkey config value; did you put your credentials in the authinfo file (that the next thing once you point to a real java).  Then give it another try. ... View more

Just an FYI, as of the latest version of SASPy, V4.3.0 (published yesterday), there is now the ability to use sshpass (a Linux tool) with the STDIO over SSH access method, which allows you to automate connecting over ssh with user/pw. So, you can now connect without having to set up passwordless ssh. See the current doc on this here: https://sassoftware.github.io/saspy/configuration.html#stdio-over-ssh   Thanks, Tom ... View more

The connection you are trying to make is using SWAT, not SASPy. That would be the reason for the error. SWAT connect to CAS, whereas SASPy connect to SAS. The SAS ODA servers are SAS servers, so using SASPy would be the way to connect to them from Python. The config doc for saspy is here: https://sassoftware.github.io/saspy/configuration.html and for ODA, the specific config would use IOM access method Remote: https://sassoftware.github.io/saspy/configuration.html#remote The specific config doc for ODA access from saspy, with the hosts and port, ... is here: https://support.sas.com/ondemand/saspy.html Tom ... View more