New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running saspy with SAS Enterprise Guide #163
Comments
@peter-hamilton-MOH No, I'm afraid that EG isn't what saspy can use. It needs to be SAS (sas.exe) or a remote workspace serer. When you use EG outright, is it not connecting to a workspace server somewhere? Basically, you need the ip (hostname) of the object spawner that starts up that workspace server, and the workspace server port. You need OMR credentials too, which should be the same as you need with EG. Can you connect to the workspace server instead of trying a local connection (that you don't have SAS to make)? Tom |
Hey Tom, Thanks for the quick reply. So would that be the 'winiomwin' option? I believe our server is running windows. I set that in the configuration with what I believe is the hostname & port (which I took from SAS EG's settings) and got back the following error (some credentials redacted - note that my host name isn't an IP but just a long alpha string):
|
Yes, that winiomwin template shows what you need for this case. You are getting a permission error running the java command. Can you run that whole java command from a cmd prompt and see if it displays any more of an error?
Also, depending upon how java was installed, just saying 'java' may work fine, but sometimes you have to specify the full path to java.exe. Try running the command interactively and lets see if there more error messages to point us in the right direction. Tom |
Here's what running in a DOS prompt yielded:
|
Well, that looks like it 'worked'. You didn't get a permission error. Java ran, found saspyiom.jar and ran it. The socket error would be expected in this case, and it's trying to connect back to pyhon, which isn't running in this case. |
I realized afterwards I was running saspy via python3 through a cygwin (shell emulation) terminal instead of a DOS prompt! I re-ran using python3 through a DOS prompt and got a slightly different error:
Running the java command via DOS prompt returns the same java.net.ConnectException: Connection refused: connect error however |
Try specifying the full path including \java.exe for the 'java' keyword in your winiomwin cofig definition. I think it can't find 'java' in your path how you're running. |
Thanks I think it's working now!! It's asking for my password - I need to contact my SAS admin for this, so I can't confirm what happens after I enter it. Thanks for all your help! |
Great!, btw, you can put your user/pw in an _authinfo file in your home directory (secured so you're the only one w/ read access), and you won;t have to enter credentials any more. Check it out in the install/config guide. |
Thanks again! Waiting to hear about credentials - in the meantime I've realized after looking through the SAS EG settings that I'm configured to use IWA for authentication. I have enabled the flag and gotten the error:
According to the trouble shooting guide I need to add the path to the sspiauth.dll in my System Path variable. Not sure what this means? Some Googling suggests adding to the Windows registry, but I'm unsure where and what to add exactly? |
Very good. Yes, for IWA, you don't need the _authinfo nor to specify user or pw.
and you'll see the environment variables, including Path. You can add the directory to it via the UI: |
Hmm did a system wide search for the sspiauth.dll and can't find it anywhere - perhaps it's not included in SAS EG? |
That seems odd (though I don't know for sure about an EG only install). If EG is connecting to the server with IWA, I would think it would have to use this dll. But, I'm not positive. EG may use the .net IOM client instead of java (again, I'm not sure), but if so, I guess that could do something different that doesn't use that dll. Or, are you sure you're EG is using IWA and not just passing user/pw? Can you get that file off the machine where you're workspace server is running? It should be there, as that's a real SAS install. Just copy it to your machine somewhere and put that directory in the PATH env var and see if you can connect. |
I was able to find the file - but unfortunately not download it in a reliable way - I couldn't actually see the server I needed in the explorer view, so I had to manually search for and find it using the SAS |
Someone's working on finding me some valid credentials as well, so maybe that'll work instead? |
Hey Tom! Finally logged in yay! Thanks for all the help, I really appreciate it 💯 🥇 This will hopefully help a bunch of people at my organization who use SAS. -Peter |
That's great! Glad to hear it. I'm all about helping you guys (our customers)! :) |
Hi there, I'm trying to get saspy up and running using SAS EG and have run into a roadblock.
I've set the config file to winlocal and was able to find all of the .jar files on my machine, and tested the
"java -classpath ..." command. Where I got stuck I was able to locate in the trouble shooting guide:
Fixes listed as:
I don't have the SAS Workspace Server (eg. sas.exe) application on my computer - is it still possible to use saspy? Can I get this application somehow? Also, is it even possible to use saspy with SAS Enterprise Guide?
Thanks for your help,
Peter
The text was updated successfully, but these errors were encountered: