After installing OpenBuildings Designer Update 7 you may see error messages when performing operations such as opening the product, updating Structural members, or attempting to define default HVAC fittings.
Since OpenBuildings Designer Update 7 is dependent on new and modified workspace files for proper operation, if you don't have these files in their expected locations and/or proper read/write access to them you may encounter error messages. This wiki is intended to address each potential instance individually, based on the cases that have been reported to date.
This error indicates that the application does not have edit rights to the dataset.cfg file. If you have any existing version of this file, Update 7 will attempt to edit the file to add the required ProStructures related variables as mentioned here. Check your read/write permissions to the ..Your_Location\Configuration\Datasets\Dataset_Name\ folder to insure that editing rights are available at the file level. Note that when using certain NAS systems you may need to add permissions specific to that system's environment that are beyond standard Windows permissions. For example, if using Synology you may have to enable Advanced Share Permissions as outlined in this page from the manufacturer's website: https://www.synology.com/en-global/knowledgebase/DSM/help/DSM/AdminCenter/file_share_privilege_asp. Once the dataset.cfg file is updated you may be able to reset your permissions back to their normal state.
This indicates that the dataset.cfg file was not found in the expected location. Check that the location defined by the configuration variable TFDIR (dataset root folder) is correct and that it does contain the "dataset.cfg". Note that this file should have a recent modification date by virtue of installing Update 7, since ProStructures variables are written as outlined in the example above.
This error indicates that the AutoFittingOptions.xml file is from a previous release. Since Update 7 is expecting an Ogee settings group that does not exist when using a previous version of this file, it cannot properly generate the UI element and therefore causes a .NET Framework error. Copy these two files from the closest equivalent Update 7 dataset based on your region, and add them to the applicable locations in your custom configuration.
ProStructures Interoperability - Configuration Changes