One of the people here apparently configured the Server DNS host name wrong when they installed Enterprise Guide 7.1. They listed only the first node, prd01, but on my machine (which is working) I have the fully qualified name, prd01.mcp.srxc.int (all four nodes).
Is there a way we can edit the server DNS host name? I believe this is the value contained in macro variable &_SASHOSTNAME
I suppose we could just uninstall/reinstall, but it seems like this should be a 2 second change if I could just figure out what xml file or such to edit.
Thanks in advance,
Jim
P.S. Just to be clear: This is not the Connection Profile I'm talking about here.
Well, embarrassingly, it turns out that it was not a SAS EG issue at all. The TCPIP settings were wrong on that machine, and it just happened to affect SAS EG. Problem solved though.
Jim
Details of error message:
The machine name could not be resolved to an IP address.
-------------------------- Technical Information Follows --------------------------
Exception Details:
----------------------------------------
Exception type: SAS.EG.SDS.SDSException
Message: The machine name could not be resolved to an IP address.
Source: SAS.EG.SDS.Model
Target Site: SASWorkspace
Stack Trace:
at SAS.EG.SDS.Model.Server.SASWorkspace(Boolean checkWorkspace)
at SAS.EG.SDS.Views.View.DoPopulate(DisplayOperation& op)
Inner Exception Details:
----------------------------------------
Exception type: SAS.EC.Directory.Model.SDSException
Message: The machine name could not be resolved to an IP address.
Source: EC.Directory
Target Site: Connect
Inner Exception Details:
----------------------------------------
Exception type: System.Runtime.InteropServices.COMException
Message: The machine name could not be resolved to an IP address.
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)
Well, embarrassingly, it turns out that it was not a SAS EG issue at all. The TCPIP settings were wrong on that machine, and it just happened to affect SAS EG. Problem solved though.
Jim
Join us for SAS Innovate April 16-19 at the Aria in Las Vegas. Bring the team and save big with our group pricing for a limited time only.
Pre-conference courses and tutorials are filling up fast and are always a sellout. Register today to reserve your seat.
What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.
Find more tutorials on the SAS Users YouTube channel.