Type initializer error and Unable to get the client policies for specified resource
search cancel

Type initializer error and Unable to get the client policies for specified resource

book

Article ID: 151966

calendar_today

Updated On:

Products

IT Management Suite

Issue/Introduction

When the console is launched, it sends you into NSSetup, which fails. NSEs are not processing.

The errors below or similar can be seen in the logs.

Date: Jan 10 23:36:29:000
Source: GetClientPolicies::Page_Load
Description: Unable to get the client policies for the specified request (Request: <Request configVersion="2" hash="9C68B2185D731FE295E0F0F2E1D8E7B2" compress="1"><WrkstaGuid>{8931D494-EB2D-49B5-B9DF-1A38B61EBC3E}</WrkstaGuid></Request>, Exception: Altiris.NS.Exceptions.AeXException: Unable to get the Uri from the specified config file ---> System.Xml.XmlException: The root element is missing.

Date: Jan 11 10:15:23:000
Source: Altiris.NS.ClientConfigManagement.ClientConfigManager.GetClientConfig
Description: Unable to get the client policies for specified resource (Resource: {00000000-0000-0000-0000-000000000000}, Exception: System.TypeInitializationException: The type initializer for "Altiris.NS.Configuration.Core" threw an exception. ---> System.Xml.XmlException: The root element is missing.

Date: Jun 07 17:10:49
Source: Altiris.NS.UI.CoreWebService 
Error getting node url: Altiris.NS.Exceptions.AeXException: Unable to get the Uri from the specified config file ---> Altiris.NS.Exceptions.AeXException: Unable to locate the remoteUri with a alias of "DataClassTransformer" in the config file

Cause

In this case the coresettings.config file was corrupted. This can be verified by copying the file to a different location, renaming it to a .xml file then opening it with Internet Explorer. If Internet Explorer gives an error when opening the file then it is corrupt.

Resolution

If the CoreSettings.config file opens without an error message in Internet Explorer, there can also be "damage" caused by syntax errors. For example type instead of type, Value instead of value, or missing an equal sign or an extra equal sign in the file.

If there is a backup of the CoreSettings.config file that can be opened using Internet Explorer, you can just rename it to the correct name and then run it through NSSetup.aspx

If not, then a repair of the Notification Server will need to be run from Add or Remove Programs. Make sure that repairs are also run on any hotfixes that are installed after the Notification Server repair finishes.

Applies To
Notification Server

Powered by Wolken Software