topic Re: SAS Required Ports ? in SAS Enterprise Guide

SAS Required Ports ?

apolodor — Tue, 24 Sep 2013 08:00:42 GMT

How can I find out what ports my SAS client is using to connect to a SAS Server (Metadata)?

I was able to connect/log in using SAP Enterprise Guide but I got an error while expanding Server List items.

Thank you!

Re: SAS Required Ports ?

Amir — Tue, 24 Sep 2013 11:39:53 GMT

Hi,

Posting the error message and/or a screen shot of the issue, might help someone provide an answer.

Does the following document help?:

http://support.sas.com/techsup/technote/ts790.pdf

There are many references to "port" in it as well as some default values.

Regards,

Amir.

Re: SAS Required Ports ?

apolodor — Tue, 24 Sep 2013 12:09:58 GMT

Thanks for the info! That utility - itconfig.exe - didn't help to trace the missing ports.

There has to be a better way to find out what are the ports required by SAS.

I was able to connect with Personal Login Manager but I can't expand the servers listed in Enterprise Guide - the error is very generic and I'm pretty sure is related to a closed port.

Re: SAS Required Ports ?

Amir — Tue, 24 Sep 2013 12:27:38 GMT

Hi,

So I guess the section on page 9 of the PDF was not relevant / does not apply to your case or does not tell you the port numbers you want:

Regards,

Amir.

Re: SAS Required Ports ?

apolodor — Tue, 24 Sep 2013 12:42:46 GMT

Yeah, the connectivity test was unsuccessful.

Re: SAS Required Ports ?

Amir — Tue, 24 Sep 2013 12:45:51 GMT

Hi,

Then in that case, I'd recommend you get in touch with SAS Technical Support (link at bottom of page) who should be able to help you with your specific issue.

Regards,

Amir.

Re: SAS Required Ports ?

apolodor — Tue, 24 Sep 2013 13:00:59 GMT

It looks like SAS is a "black box". This information should be transparent.

Re: SAS Required Ports ?

Haikuo — Tue, 24 Sep 2013 13:06:20 GMT

I doubt it is a port problem, unless during the deployment, your SAS admin purposely made some change. Ask your Admin to verify if object spawner is running as a service on your Appserver, and if your credential is permitted to access Appserver on OS level (on Windows server local security setting, your credential should be able "act as part of operation system", and "able to run batch jobs"). If you just try to figure out port number in your connection profile, just open the profile and check it out. In EG, the active connection profile is on the right bottom corner, click to open it, then you will see:

Similar connection profiles can also be found in Management Console, Olap cube studio, information map studio , Microsoft add-ins and other clients.

Re: SAS Required Ports ?

apolodor — Tue, 24 Sep 2013 13:21:19 GMT

Thanks for this info!

Before I tried the authentication with a specific port in connection profile and it was successfully but no luck trying to retrieve AppSrv items .

Meanwhile I have opened all ports and now I can see the items under AppSrv. The challenge is to find out what specific ports do I need to keep them opened... My guess is: there are several ports required...

Re: SAS Required Ports ?

Haikuo — Tue, 24 Sep 2013 14:43:38 GMT

Not sure if I understand when you say "have opened all ports".

Well, there are several steps when doing the connection, knowing the anatomy will help to understand the problem, take workspace server for example:

1. When you launch a connection request using a client in SAS EBI environment, you first connect to Metadata server, in the case showed above, the port is 8561

2. Then the metadata server searches the metadata to retrieve the name of the machine hosting the workspace server, the port on the which the object spawner listens for requests for this server, and the authentication domain info. This connect information will then be return to your clients.

3. Your client (EG) will then make the request for the a workspace server using the information obtained from metadata server.

4.The object spawner will verify your credentials and launch the workspace server.

5. TCP connection is completed.

So from your description, it seems to me that the connection info stored in your metadata (Profile_A) is NOT matching the configuration reality of your Appserver (Profile_B). If you have Management console, you can find out "Profile_A" easily by going to plug-ins, then server manager. For "Profile_B", you need to access the machine that hosts your Appserver, and locate objectspawner.bat and some other Config files which define the initiation process of objectspawner and other server service, such as Workspace server, storeprocess server etc.

However, frankly if I were you, I would have involved SAS tech support long time ago.

Haikuo

Re: SAS Required Ports ?

apolodor — Thu, 26 Sep 2013 08:52:41 GMT

----Not sure if I understand when you say "have opened all ports". ---

It's simple. Not all ports are opened (pointing to the SAS servers) on my workstation . Initially the one used by Metadata Server has been opened but it wasn't enough. Now I have to figure out what are the others required.

It's quite complicated... I might end up asking SAS tech support

But first I would like to understand a little bit this issue: how many ports are required to be opened?

Re: SAS Required Ports ?

ChrisHemedinger — Thu, 26 Sep 2013 13:00:25 GMT

For the minimum setup for connection between SAS Enterprise Guide and your environment behind a firewall, the answer is two:

- one port for the SAS Metadata Server (by default, 8561)

- one port for the SAS Workspace Server (by default, 8591)

If you have a stored process server, you will also need a port for that (8601 by default).

You need to open the ports only for server resources that EG will connect to directly, where it acts as the client endpoint. There are other ports in play, but many are "SAS to SAS" connections that will be in the same "zone" and probably won't be governed by the firewall that is affecting EG.

Chris

Re: SAS Required Ports ?

canmjs — Tue, 06 Oct 2015 04:37:03 GMT

Hey Chris,

Thank you for your post on this - very helpful and saves alot of navigation through documentation. Now, with SAS 9.4M3 the default pooled workspace server appears to be 8701. Is this correct?

Marc

Re: SAS Required Ports ?

ChrisHemedinger — Tue, 06 Oct 2015 10:59:34 GMT

Yes, it looks that way. All of the default ports are documented in the Install Guide.

Chris

Re: SAS Required Ports ?

rf_mikael — Wed, 24 Aug 2016 17:35:44 GMT

Chris,

I am forwarding port 8561 on the SAS server to a port on my local machine via Bitvise SSH and then pointing EG to the local port.

However, it looks like I also need to forward 8591 as well, which I can do, but then how do I point EG to the local port?

Does EG has a config file somewhere in C:\Program Files\SASHome\SASEnterpriseGuide\7.1 ?

Will it work if both ports are forwarded and pointed to?

Re: SAS Required Ports ?

ChrisHemedinger — Wed, 24 Aug 2016 18:42:58 GMT

I don't know much about the port-forwarding software you mention, but you can try the 8591 connection with another tool that I built called SasHarness, which is an example of a Microsoft .NET application connecting via SAS Integration Technologies. You can get the tool (source and binaries) on my GitHub repository.

Re: SAS Required Ports ?

rf_mikael — Thu, 25 Aug 2016 01:29:35 GMT

Thank you, I'll review.

Re: SAS Required Ports ?

rf_mikael — Mon, 21 Nov 2016 22:24:23 GMT

Chris,

I have both ports forwarded now - 8561 and 8591.

Tested by SAS Integration Technologies Configuration and shows success:

Congratulations! You have successfully established a connection with the SAS server. The details of the SAS server are below.

SAS Server Definition Information:
Machine DNS Name: localhost
Prog ID: SAS.Workspace.1.0
Class Identifier: 440196D4-90F0-11D0-9F41-00A024BB830C
Protocol: IOM Bridge
Encryption Level: Credentials
Encryption Algorithm(s): SASProprietary
Port: 8591
Service: sasobjspawn

But when I open EG it seems to connect but when I click on the SASapp to see the directory of files on the server, I get these errors:

Exception Details:
----------------------------------------
Exception type: SAS.EG.SDS.SDSException
Message: Could not establish a connection to the server on the requested machine. Verify that the server has been started and that the host and port of the server match the client's connection information.
Source: SAS.EG.SDS.Model
Target Site: SASWorkspace

Stack Trace:
at SAS.EG.SDS.Model.Server.SASWorkspace()
at SAS.EG.SDS.Views.View.DoPopulate(DisplayOperation& op)

Inner Exception Details:
----------------------------------------
Exception type: SAS.EC.Directory.Model.SDSException
Message: Could not establish a connection to the server on the requested machine. Verify that the server has been started and that the host and port of the server match the client's connection information.
Source: EC.Directory
Target Site: Connect

Inner Exception Details:
----------------------------------------
Exception type: System.Runtime.InteropServices.COMException
Message: Could not establish a connection to the server on the requested machine. Verify that the server has been started and that the host and port of the server match the client's connection information.
Source: SASObjectManager
Target Site: CreateObjectByLogicalNameAndLogins

Stack Trace:
at SASObjectManager.ObjectFactoryMulti2Class.CreateObjectByLogicalNameAndLogins(String Name, Boolean synchronous, Object pIOMI, String LogicalName, LoginDef pOMRLoginDef, LoginDef pSASLoginDef, String nameValuePairs)
at SAS.EC.Directory.Model.Server.Connect(ConnectionInfo connInfo)

What else does Enterprise Guide need to successfully connect?

Re: SAS Required Ports ?

rf_mikael — Tue, 22 Nov 2016 19:08:45 GMT

Forwarded 8581 as well - still, the same error.

Re: SAS Required Ports ?

ChrisHemedinger — Tue, 22 Nov 2016 19:15:24 GMT

I'm not familiar with the port forwarding mechanism, but if ITConfig works, then EG *should* work as well. Do you have access to PowerShell?

You could try saving this script into a PS1 file and then running (pass your host name in as an argument).

if ($args.Count -eq 1)
{
  $host = $args[0] 
}
else
{
  Write-Host "EXAMPLE Usage: CheckServerHealth.ps1 <host-name or IP address>"
  Exit -1
}


$ports = @{
 8561  = "SAS Metadata Server"
 8591  = "SAS Workspace Server"
 8581  = "SAS Object Spawner Operator"
 8571  = "SAS Object Spawner Load Balancing"
 5451  = "SAS OLAP Server"
 8701  = "SAS Logical Pooled Workspace Server"
 8601  = "SAS Logical Stored Process Server"
 7551  = "SAS/Connect Spawner"
 8551  = "SAS/Share Server"
 5091  = "SAS Remote Services Registry"
 22031 = "SAS Framework Data Server"
 8080  = "SAS Web Application Server"
}

foreach ($port in $ports.Keys)
{
    $tcp = New-Object System.Net.Sockets.TcpClient
    try
    {
       $tcp.Connect($host,$port)
       Write-Host "SUCCESS: Connection to " $ports.Item($port) " on port " $port
    }
    catch
    {
      Write-Host "FAIL: Unable to connect to " $ports.Item($port) " on port " $port
      Write-Host "  " $_.Exception.Message
    }

}