Hmm, well, having no idea the state of your system, it didn't sound like it actually reinstalled it. try explicitly uninstalling it, then installing it and you should see that it actually 're-installed' it. Else, I'm guessing that nothing actually happened. ... View more

Well, I don't know what all happened with the conda update all, but have you tried reinstalling the SAS_kernel? Maybe that is the next necessary step? ... View more

Good deal. Yes, on windows, the file starts with an underscore, while on linux it starts with a dot: win - _authinfo   (no file extension!) linux - .authinfo   (permissions 600)   Glad you'r back up! Tom ... View more

Was the password you had to update your SAS Metadata password, or a password for some other account? The user/password in the authinfo file are the credentials you use to authenticate to OMR. I don't know if those credentials are the same as the one you had to change.    1 - try putting the pw back as it was in the authinfo file. 2 - try removing the authkey and see if you get prompted for credentials, and see if either pw works.   uninstalling/reinstalling saspy wouldn't have any effect on any of this. I'm guessing you didn't change your OMR pw, but rather some other account, so changing it in the authinfo file is the problem. But I don't have any information to really know wither way.   Tom ... View more

Connecting to a workspace server requires credentials which are stored in the metadata server (OMR). The error you are getting is pretty clear that the credential being provided are not valid to be able to connect to that server. I would need to have more information to have a better idea of anything more than that. I assume you expect the credentials to work.It may be more productive to open an issue on saspy to get direct help with this: https://github.com/sassoftware/saspy/issues  (click New Issue). Thanks, Tom ... View more

Sure thing, glad you're up and running!   Can you change your accepted answer to the correct one, just so if others search on this they don't go down the wrong path? I appreciate it! (I can't change it)   Thanks!, Tom ... View more

Yes, in the instructions posted previously, you can see that you you can specify the configuration name on the SASsession invocation:   sas = saspy.SASsession(cfgname='sasfusionint')   Or, if you only using one anyway, then only specify that name in the configuration file (SAS_config_names) and saspy will just use it without any input from you:   SAS_config_names = ['sasfusionint'] and with that: sas = saspy.SASsession()     Glad it's now getting the credentials.  Tom ... View more

the picture in your first post showed that you have 3 configuration definition in your config file: sasgriddev, sasfusionhpa, sasfusionint And you were using the one named sasfusionint.     ... View more

The configuration definition is in your sascfg_personal.py file. It's the dictionary that tells saspy where SAS is and how to connect to it. You must have configured this to be able to make a connection to start with, via : sas= saspy.SASsession() https://sassoftware.github.io/saspy/install.html#sascfg-personal-py-details   I don't know what you'rs looks like but it would be something like the following ('authkey' : name is another key value pair): # Windows client and Windows IOM server winiomwin = {'java' : 'java', 'iomhost' : 'windows.iom.host', 'iomport' : 8591, 'encoding' : 'windows-1252', 'classpath' : cpW }   ... View more

Oh, and just to head off the next thing; and again, for others who might search and find this. As you said, _authinfo, I take it you're on windows. Many users on windows had default settings, where windows won't show you the file extensions in it's UIs. This also causes a problem when creating files via it's UI's, so you may have ended up not with a file called '_authinfo', but rather '_authinfo.txt' and in the file explorer it still shows it without the extension, so it looks to the user like it's named right, which it's not.   If you add the 'authkey' to your definition, and then get an error from saspy that it can't filnd that authkey, or the authinfo file (Can't remember the exact error you would get, but it won't work), then that's because the filename is wrong and you have to go remove the '.txt' from it so it's named right.   Hopefully you don't have that problem, but I've seen it plenty of times, so I wanted to write it down here, so it's apparent to anyone who reads this in the future trying to address the same issue.   Thanks again! Tom ... View more

Perfect, now add  'authkey' : 'sasfusionint', to your configuration definition that you are using your sascfg_personal.py file, and saspy will get those credentials for you.   Also, can you switch your accepted answer from the post you have it (implement this yourself), to one that shows to use the supported way? Just to that other users that might read this aren't sent down the wrong path?   Thanks! Tom ... View more