Failure to establish hierarchy- Error: Could not find any resources appropriate for the specified culture or neutral culture.


Article ID: 157971


Updated On:


IT Management Suite


When attempting to establish a hierarchal relationship between a parent and child server, after completing the last step, the process immediately fails with the following generic error box:

Hierarchy Node Process failed. Please review the logs for details.

IIS also returned error 500 (internal server error) when the process was attempting to hit:  /Altiris/NS/Admin/Configuration/Hierarchy/dlgNodeConfigurationProgress.aspx


 The underlying error was the following:

Could not find any resources appropriate for the specified culture or the neutral culture. Make sure "System.Runtime.Remoting.Messaging.StackBuilderSink.resources" was correctly embedded or linked into assembly "mscorlib" at compile time or that all the satellite assemblies required are loadable and fully signed.


The KMS files (C:\ProgramData\Symantec\SMP\KMS) on the target server had originated from an installation on another server and had since been manually copied over to the new server. As a result they were neither registered nor were they functional.  Usually there will be errors in the logs of the target server indicating a problem with finding *.KMS files.

At the time the attempt to establish the hierarchy was made, the server initiating the request required a response using NS.WebServiceCredential.kms but the target server was unable to complete the request.



1. Log onto the server who's KMS files are the problem.

2. Delete or move all files in the KMS folder beginning with NS.*

3. Open a command prompt on the server and change the pointer to:   .\Program Files\Altiris\Notification Server\Bin

4.  Run the following command to rebuild the set of files for the local server:

AeXConfig.exe /configure "C:\Program Files\Altiris\Notification Server\Config\CoreSolution.config"

Note: The command assumes the config file is on drive C:  If the Platform installation was done to a different path then change the path accordingly.


Applies To

Symantec Management Platform 7.1 SP2 MP1.1