SPECTRUM: "The parent landscape does not exist in the location server map for the local landscape" (Legacy KB ID CNC TS31051 )

Document ID : KB000051790
Last Modified Date : 14/02/2018
Show Technical Document Details
Check the $SPECROOT/LS/.locrc files on the SpectroSERVER systems to see if the MLS is configured using the FQDN if it is, change it to use the hostname. For example:


MLS using FQDN:


LOC_SERVER_SOCKET_NUMBER=0xdaff
MAIN_LOCATION_SOCKET_NUMBER=0xdaff
MAIN_LOCATION_HOST_NAME=HostName.ca.com
MAX_CONNECTIONS=750
orb_args=-ORBpropStorage .natfwrc


MLS using HostName:


LOC_SERVER_SOCKET_NUMBER=0xdaff
MAIN_LOCATION_SOCKET_NUMBER=0xdaff
MAIN_LOCATION_HOST_NAME=HostName
MAX_CONNECTIONS=750
orb_args=-ORBpropStorage .natfwrc


After making the change, kill the running LocServ on each of the SpectroSERVER systems. processd will restart a new LocServ process


Restart tomcat on the OneClick systems



Related Issues/Questions:
The following error is seen in the OneClick Administration Landscapes window:


The parent landscape does not exist in the location server map for the local landscape



Problem Environment:
SPECTRUM 09.00.00.00
CallT0000225276
swbug021944
In SPECTRUM 9.0, it does not matter the fully qualified hostname configured on the SpectroSERVER system, we advertise the hostname in the Location Server (LocServer). This was done to resolve an issue in previous SPECTRUM versions where the SpectroSERVER host had multiple ip addresses resolved to different domains. For example:


SpectroSERVER host has multiple subnets, with the following names:


spectrumhost.usa.ca.com
spectrumhost.emea.ca.com


We will advertise "spectrumhost" in the LocServer and will bind to all available interfaces.  We require that `spectrumhost` be resolvable for any host that wants to connect to `spectrumhost`.


For those systems on the usa.ca.com network, spectrumhost should resolve to spectrumhost.usa.ca.com.  For those systems on the emea.ca.com network, spectrumhost should resolve to spectrumhost.emea.ca.com.  Everything should be fine.



Causes of this problem:
The cause of the "The parent landscape does not exist in the location server map for the local landscape" error maybe the Fully Qualified Domain Name (FQDN) of the Main Location Server (MLS) is entered in the $SPECROOT/LS/.locrc file on the SpectroSERVER systems.


(Legacy KB ID CNC TS31051 )