Troubleshooting: "The Settings Property Is of a Non-Compatible Type" Error

Version Affected: All

 

Overview

After migrating a Classic realm to New Experience on a newer version, a user may see an unhandled exception with a message such as The settings property 'DigitalFP' is of a non-compatible type — the same error can name a different property, for example PNToken, AccessHistory, or OATHToken instead.

 

Cause

The migration can leave one or more settings properties in the realm's web.config missing their type="object" attribute. For example, an entry like:

<add name="DigitalFP" />

is missing the type attribute it needs, and should instead read:

<add name="DigitalFP" type="object" />

New Experience raises the SystemConfiguration_SettingsPropertyWrongTypeException exception whenever it reads one of these properties without its type attribute. The properties known to be affected are DigitalFP, PNToken, AccessHistory, and OATHToken.

Resolution:

For a single realm, use the built-in Update Web Config tool:

1. Log in to the Admin Console for the affected realm.
2. Go to Tools > Update Web Config.
   

This adds the missing type="object" attribute back to the affected settings properties for that realm.

If many realms are affected and updating them one at a time is impractical, SecureAuth Support has a PowerShell script that updates all realms (or a specific range of realms) in one pass, automatically excluding the SecureAuth0 realm and backing up each realm's web.config with a date/time stamp before making any change; it also supports a dry-run mode to preview the changes first. Contact SecureAuth Support to request this script.

 

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.