06-11-2015 08:06 AM
i have a strange problem.
The SAS platform is correctly installed on a windows server sas.mycorp.com. When i remote access the machine by remote desktop i can validate all SAS servers in the management console.
From my client PC which is inside a completely different domain i can also access the workspace and connect server. However the STP and Pooled Workspace Server cannot be started.
With the SAS IT Configuration tool the error message says "The machine name could not be resolved to an IP address."
With Management Console the error message is more detailed "[6/11/15 1:46 PM] SEVERE: The application could not log on to the server "sas.sas.xyz.internal.mycorp.com:8611". The machine name is not valid."
I would expect the object spawner to redirect client connections to the public domain "sas.mycorp.com:8611"
But for some reasons the object spawner redirects all client connections for the STP server or the pooled workspace server to an internal DNS which cannot be resolved by the client machines because they are inside another domain and have a different DNS server.
In the management console the object spawner and all servers are configured to run on the host "sas.mycorp.com". But when i examine the object spawner log files i always see that the internal DNS is everywhere.
Is there another way to force the object spawner to redirect the clients to the public domain?
06-11-2015 01:55 PM
Try this if not tried:
1. Server Manager --> Object Spawner object
2. Right click on (1) above
3. Options tab of Properties
4. What machine is listed in "Selected:" text box? Is it just a single host name? If so, try reassigning to the fully qualified hostname, e.g. your "sas.mycorp.com" and see if that helps (after Spawner restart)
06-12-2015 07:00 AM
thank you for your suggestion.
There is only one machine available and selected which is "sas.mycorp.com".
This is the part which puzzles me: the spawner and all servers are configured to use the public domain "sas.mycorp.com", but it seems that the object spawner is ignoring these settings and thinks that "sas.sas.xyz.internal.mycorp.com" is more appropriate...
08-03-2015 05:13 AM
I think the way the spawner (and probably some other parts of a server SAS setup) and the clients build physical server names from the metadata and the current connection path needs to be overhauled in future releases to make it more flexible in terms of different access paths.
I also found a problem with supplying the Web Applications over http: and https: concurrently. With the default setup, WRS (eg) will automatically switch back to http:, even when the first access was over https:
Need further help from the community? Please ask a new question.