Setting up Windows Server to allow SAS Studio Basic connections

[snoopy369]

I have a Windows server installation of SAS 9.4 TS1M5 that we currently use in remote desktop mode (i.e., we remote into it and open EG or DM to run things, or schedule batch jobs via sas.exe).  No mid-tier, just a single server.

I learned about SAS Studio Basic at MWSUG, and wanted to see if we could set it up to allow connections in SAS Studio rather than having to remote in.  After installing M5 update with Studio 3.7, we set it up to include SAS Studio Basic; it seems to start, and I can connect to localhost:38080 with no problem.

However, I don't seem to be able to connect from my local machine.  I've got the Server team looking at things, but they think the ports are fine; there's an opening for 38080 both inbound and outbound, and sasstudiohost.exe is allowed for all ports on the domain (I'm testing from the domain).  But I still get "server not found" when I try to connect to the server from my local machine.

Is there anything else on the SAS configuration side, or a common issue that we might be overlooking?

[JuanS_OCS]

Hello @snoopy369,

f

Please read the introduction and overview http://documentation.sas.com/?activeCdc=webeditorcdc&cdcId=sasstudiocdc&cdcVersion=3.7&docsetId=webe...

And the system requirements: https://support.sas.com/documentation/installcenter/en/ikstudiosr/68202/PDF/default/sreq.pdf

Anyway, if you can connect ok from the server itself, perhaps it is not the server what is blocking you, but your client.

Maybe your local PC's firewall or a company firewall (eg, if you have Citrix or virtualized applications, you would have an F5 firewall in between the clients and the servers).

The best you can do is: 

1- see if you can connect to that server  from another server. Then you can see if it is your clients/laptop what is blocking the access

2- From your laptop, your admins can, if telnet is activated, a "telnet yourhost.yourdomain 38080"   to test the connection.

In the end, probably nothing to do from SAS point of view, but from your network specialists.

[snoopy369 · Accepted solution]

Thanks, Juan.

The issue ended up being firewall related after all.  While we did open up the 38080 port, there was a separate rule blocking SAS's java runtime specifically.  I'm not sure if this is something we set up, or if it was put in automatically by SAS; but apparently the java runtime needs to be able to pass through the firewall as well.

[3fatty]

Hi, could you please share more information about using single user SAS studio to connect a remote SAS? I installed SAS (not SAS server) on a window server. And can I use local SAS studio to connect that server? If yes, how to do the operations?

Thank you very much.

[Kurt_Bremser]

First of all: do not hijack old, answered threads. You deprive yourself of a lot of audience, and in most cases the issues are different. Open your own thread with your question.

To use SAS Studio, you need

• a SAS (BI) server with SAS Studio licensed
• a connection to that server
• a web browser

The "server" might be installed locally on the machine where you use SAS Studio, but in most cases it is installed on a central server, and nothing needs to be installed on the clients except a compatible web browser.

Purely local (workstation) installations typically include Enterprise Guide as a frontend, not SAS Studio, as then there is no need for the whole midtier (web server, web application server, webapps).