Error connecting to SAS Guide server

[Jorge90]

Hello, I am having a problem with my connection to the server. The profile is configured correctly and connects without any issues, but the problem arises when I want to deploy the servers to view the tables.

I would appreciate any help if anyone knows how to solve this.

Error message:

"Unable to connect to the server named ‘SASApp’.
Unable to establish a connection to a SAS Workspace server named ‘SASApp’ running on port 8591 on host 'videssasaos001.nh.inet.

Check the following:
- The correct host name and port have been specified.
- If a firewall exists, it is correctly configured to allow
access.
- An object spawner has been started on the server. - SETINIT has not expired on the server.

Contact your SAS administrator if the problem persists.

Server response: The machine name could not be resolved to an IP address.

Translated with DeepL.com (free version)

[SASKiwi]

You will need to talk to your SAS support people to fix this. Troubleshooting will be needed to find what is causing it. Is this the first time you have tried setting this up or was it working and now it isn't?

One test you can try is to ping the SAS server from a Windows command line:

ping videssasaos001.nh.inet

If this is unsuccessful then it means the SAS server isn't available on your network.

Also normally you connect to your SAS metadata server, not your workspace server and that is on the default port of 8561.

[Jorge90]

Hello @SASKiwi,   

Thank you for your help. I ping the server “10.203.25.121” and got a response, but when I pinged “vldessasaos001.nh.inet,” it told me that the host could not be found.

This is the first time I have connected from my computer. Other colleagues in another area are able to connect without any problems.

[SASKiwi]

Try 10.203.25.121 in your EG connection profile then. It is not recognising your host name.

[Kurt_Bremser]

If a name is not recognized, it means that your local DNS serving your network segment has no entry for it.

Do you really have the correct name? If yes, your network admjnistrators need to fix this.