@JackHamilton thanks for showing your config file, I'm sure that will make it more clear what @pururshothaman should have. Also, sorry the configuration doc isn't as straightforward as maybe it could be. I write much better code than I do doc 🙂 Having 7 different ways to connect to SAS, depending upon if it's local or remote, if you're using a workspace server (and how that's been deployed/configured), or just a simple install of SAS itself, or even if it's SAS in a Viya deployment, is a lot of information to try to provide. And, this has evolved of the past couple years, so I don't disagree that the config section seems a bit complicated. If there's anything specific that would make it better, since you've been through it and were able to configure it, I'm more than happy to try to make it easier to understand.   @pururshothaman for connecting to grid, the config file will be similar to what @JackHamilton showed. You would use the IOM access method Remote version. The config doc for that section is in the links provided by @JosvanderVelden. There are other configuration keys in that doc which you may need for your situation; appserver: for instance, if you have multiple workspace servers defined. If your Grid Admins want to route saspy connections to specific LSF queues, that's possible too; see https://sassoftware.github.io/saspy/advanced-topics.html#configuring-grid-option-sets-to-have-saspy-run-on-a-specific-queue   Opening an issue on github is always a good way to get help on this too. Or you can contact me directly, my email is on there too. I try to search for 'saspy' posts here too, but I have to manually go do that to see that something new has been posted here, so I'll see it eventually, but not immediately.   Let me know if you have any trouble and need more help.   Thanks, Tom ... View more

Ok, so I’ve been looking into what happens when you have two copies of anaconda installed, as I mentioned in the last post. Based upon some of the output you provided so far, I’ve correlated that with what I’ve tried and seen.   There are different options when installing anaconda regarding setting the default python and updating system paths. in all cases so far I’ve taken the default for that. The non-default states that it’s not recommended. There are 2 places anaconda can be installed. You have (or at least had) it in both places: The system (all users): 'C:\ProgramData\Anaconda3 Your user only: 'C:\Users\[user name]\Anaconda3 When installing packages, there a --user option that can be specified. I’ve never used that, but on this system I did it and I see that there’s a new extra directory created for this in the user directory and this path is then added to the python path for both instances of anaconda. You did this at lease some time because that directory is in yout path, even though it is now empty. Jupyter (notebook and lab) have a number of paths where it keep metadata. Specifically for this issue, the kernel metadata. This is also in the user directory, so it is found regardless of what python Jupyter is running in.   So, what I’ve seen regarding the sas_kernel, matches up with problems you are having with it due to both python installs. I don’t know what problems you trying to install Jupyter lab yourself might have caused or not. The anaconda I installed already has both Jupyter lab and notebook, so I haven’t tried doing anything with installing lab.   The following are the Jupyter paths for Jupyter from each of the python installs:   C:\Users\tomuser>C:\Users\tomuser\Anaconda3\Scripts\jupyter.exe --paths config:     C:\Users\tomuser\.jupyter     C:\Users\tomuser\Anaconda3\etc\jupyter     C:\ProgramData\jupyter data:     C:\Users\tomuser\AppData\Roaming\jupyter     C:\Users\tomuser\Anaconda3\share\jupyter     C:\ProgramData\jupyter runtime:     C:\Users\tomuser\AppData\Roaming\jupyter\runtime   C:\Users\tomuser>c:\ProgramData\Anaconda3\Scripts\jupyter.exe --paths config:     C:\Users\tomuser\.jupyter     c:\ProgramData\Anaconda3\etc\jupyter     C:\ProgramData\jupyter data:     C:\Users\tomuser\AppData\Roaming\jupyter     c:\ProgramData\Anaconda3\share\jupyter     C:\ProgramData\jupyter runtime:     C:\Users\tomuser\AppData\Roaming\jupyter\runtime     The python paths from each of the installs are as follows. This is after having done a --user install of a package. Prior to ever doing a --user install, the Roaming\\Python\\Python37\\site-packages path was not in either path and the directory didn’t exist.   >>> sys.path ['', 'C:\\Users\\tomuser\\Anaconda3\\python37.zip', 'C:\\Users\\tomuser\\Anaconda3\\DLLs', 'C:\\Users\\tomuser\\Anaconda3\\lib', 'C:\\Users\\tomuser\\Anaconda3', ['C:\\Users\\tomuser\\AppData\\Roaming\\Python\\Python37\\site-packages', ]  -only after --user install 'C:\\Users\\tomuser\\Anaconda3\\lib\\site-packages', 'C:\\Users\\tomuser\\Anaconda3\\lib\\site-packages\\win32', 'C:\\Users\\tomuser\\Anaconda3\\lib\\site-packages\\win32\\lib', 'C:\\Users\\tomuser\\Anaconda3\\lib\\site-packages\\Pythonwin'] >>>    >>>> sys.path ['', 'C:\\ProgramData\\Anaconda3\\python37.zip', 'C:\\ProgramData\\Anaconda3\\DLLs', 'C:\\ProgramData\\Anaconda3\\lib', 'C:\\ProgramData\\Anaconda3',  ['C:\\Users\\tomuser\\AppData\\Roaming\\Python\\Python37\\site-packages', ]  -only after --user install 'C:\\ProgramData\\Anaconda3\\lib\\site-packages', 'C:\\ProgramData\\Anaconda3\\lib\\site-packages\\win32', 'C:\\ProgramData\\Anaconda3\\lib\\site-packages\\win32\\lib', 'C:\\ProgramData\\Anaconda3\\lib\\site-packages\\Pythonwin'] >>>    So, Jupyter Jupyter has metadata about sas_kernel (you’ve shown those files) in the user directory and inside that file is the python executable that you used to install it. In your case, C:\Users\[user name]\AppData\Roaming\jupyter\kernels\sas\kernel.json shows C:\ProgramData\Anaconda3\python.exe. But, from inside a python notebook in Jupyter, you’ve shown that the python it is running in is your user install: 'C:\Users\[]user name\Anaconda3\python.exe.   So, the sas_kernel will not load when I have it installed like that where it’s in the python that isn’t the one I’m running Jupyter from. You also have installed something using --user at some point also, though you show that directory as empty. So I guess you’ve uninstalled whatever was there. Again, I don’t know anything about what issues might be happening from you doing a pip install jupyterlab from whichever python you did that from. I don’t know what version of anaconda you have in either place.   There are too many unknowns for me to tell you what to do on your system. And you’re not an administrator, so you probably can’t do some of it anyway. But, this information may help your IT staff figure out how to clean up your system, if they aren’t familiar themselves with all of this themselves (I don’t know).   I’ve at least learned a bit about what can go wrong when you have this situation. Though, when I uninstalled and then installed sas_kernel using the right install of python, it just worked with no issue.     I hope this helps in some way.   Tom ... View more

Well, I really think your IT staff should do this. You said they installed and reinstalled anaconda for you already. I just worked on another issue like this where things didn't match up because of having different python things installed and the sas_kernel wasn't found even though saspy was and pip didn't really turn out to be the expected one ... https://communities.sas.com/t5/Administration-and-Deployment/Problem-with-SAS-kernel-in-Jupyter-on-Windows/m-p/565563/highlight/false#M16469   I think you have the same problem and you need someone who can get on your computer who knows how to clean up whatever is/was on there and get one clean install that works like expected. As for Jupyter lab, I have been trying to install anaconda different ways on windows, as part of trying to understand what your situation might be. Jupyer Lab is already installed in Anaconda. I didn't need to install it after the fact.   In fact, I installed anaconda as a user (not admin) and installed sas_kernel (which installs, depends on, saspy) and it works just fine. I started jupyter lab from the anaconda navigator (I've never used that before), and both saspy and sas_kernel worked. Trying to attach a picture; we'll see if that work. Well, can't attach a pic, so putting it in a word doc.   Can your IT people do this for you? Thanks, Tom     ... View more

Well, actually, I'm afraid that output in no way shows whether or not there are other installations of python on your machine. From what you've shown, you have, or at least had (when you installed sas_kernel) anaconda install in the system location in C:\ProgramData\Anaconda3. You also, now at least, have it installed in your user directory. Some things you've installed were done in one and others in the other and I don't think you ever had jupyter lab installed correctly. That is what my guess is from what I've seen here.   But, I think you are on to something. I suggest your IT staff get on your machine, clean up any of this python you've tried to install, make there be only on version of anaconda installed, wherever, and have them then install any other things you want on there till they work. Then you can simply use it to do what you are really trying to accomplish - using it. They should be able to install all of the things you need so that it all works.   Thanks, Tom   ... View more

So, the link I was referring to was of the github issue for users getting the same error you said you got, and what they did to fix it. I haven't seen these files before.   I'm not familiar with those files, and I don't know what directory they are in sub-directories of. But, they seem to be generated, or edited, as part of installation, as they have paths specific to your machine in them. I asked before if you have more than one python installation on your machine, as things seem mismatched. Since these files have the python executable path as well as other of your paths, specific to your machine, it seems the python path would be that of the python you used to install them, but again, I don't know how you've installed these or when. Do, you have more than one python installation? Do you know which one you're using when you installed these various parts? How did you installing them? It looks like you installed the SAS_kernel one with a different python then the python_kernel one was installed with, from what you show.   Sure try changing that path to the python in your home directory anaconda and see what happens. Who knows. maybe it'll work, maybe fail in some other way, maybe make no difference. There are too many things that don't seem to match up here for me to guess.   Tom ... View more

Well, I would have to agree with tech support that you don't have a completely working jupyter lab installation. What I've gathered is that you have clean install of some version of acnaconda, which includes all the various modules that make up juptyer. You haven't tried using that existing version of jupyter, but have installed some version of one other jupyter module (lab) which is dependent upon all the other parts of jupyter in the existing anaconda. Then it fails when trying to start a kernel with some error about a file not found.   The link I sent earlier about similar problems where users had to install other parts, or maybe update lab so it install all of the other correct version of its dependencies, which maybe would work, it doesn't seem you've tried.   My only guess is that you haven't correctly installed jupyter lab such that it will work correctly with the anaconda version you have.   That's all I can tell at this point. Wish I could just say 'do this' and it would all work, but I don't have enough info to know what that one thing is. Probably install Lab all the way or use the jupyter that was in anaconda in the first place.   Tom     ... View more