Blueprint: Unable to run a report due to error "The configuration file section 'LogonSpecificAdminConfig could not be read."

Symptom:

When using the Blueprint Administrator to run a report the error below is displayed.

"The Blueprint Administrator has encountered a fatal error ans is about to shut down. The configuration file section ´LogonSpecificAdminConfig´ could not be read"

Answer:

The "LogonSpecificAdminConfig" section is part of the user-specific configuration for the BP Administrator, and its absence typically indicates that the user login config file is broken.

To correct this behavior, if you navigate to the directory "C:\ProgramData\PharosSystems\Blueprint" you will find at least one (if not a couple, depending on the number of BP Admin logons you have created) XML file that starts with "LogonConfig_" and is then proceeded by the name of the BP Admin user. Delete it and restart the Administrator application.