OpenBuildings Designer Update Issue - Can't open files

After updating to the latest version of openbuildings, I get the following "configuration audit alert" when opening any dgn file (new or existing):

WorkSpace 'AECOsimExamples'/WorkSet 'BuildingTemplate_US' does not define an adequate configuration for ProStructures.

Details are as follows:

_USTN_WORKSPACENAME = AECOsimExamples
_USTN_WORKSETNAME = BuildingTemplate_US

PS_MATERIALFILE = C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\Standards\ProStructures\USA_Canada_Imperial\Data\ProStructuresMaterial.mdb
Evaluation finds no files

PS_BOLTINGASSEMBLIES = C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\Standards\ProStructures\USA_Canada_Imperial\MechanicalFasteners\Bolts\
No files with extension .bsy are found

PS_BOLTINGASSEMBLIESLIST = C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\Standards\ProStructures\USA_Canada_Imperial\MechanicalFasteners\Bolts\PsBoltList.bls
File does not exist

PS_CODESSELECTION = C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\Standards\ProStructures\USA_Canada_Imperial\Rebar\PcCodeSettings.xml
File does not exist

PS_POSITIONFLAGSTYLES = C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\Standards\ProStructures\USA_Canada_Imperial\PositionFlags\
No files with extension .psy are found

PS_DETAILSTYLES = C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\Standards\ProStructures\USA_Canada_Imperial\Details\Styles\
No files with extension .stx are found

PS_DRAWINGFRAMEDEFINITION = C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\Standards\ProStructures\USA_Canada_Imperial\Details\
No files with extension .frm are found

PS_DRAWINGSCALETEMPLATE = C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\Standards\ProStructures\USA_Canada_Imperial\Details\
No files with extension .scl are found

PS_ELEVATIONFLAGSTYLES = C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\Standards\ProStructures\USA_Canada_Imperial\ElevationFlags\
No files with extension .ksy are found

PS_PARTLISTTEMPLATES = C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\Standards\ProStructures\USA_Canada_Imperial\Partlist\
No files with extension .lst are found

PS_CONCRETEPARTLISTTEMPLATES = C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\Standards\ProStructures\USA_Canada_Imperial\Partlist\Concrete\
No files with extension .lst are found

REBAR = C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\Standards\ProStructures\USA_Canada_Imperial\Rebar\
Directory does not exist

REBAR_PROJECT = C:\ProgramData\Bentley\AECOsim CONNECT Edition\Configuration\WorkSpaces\AECOsimExamples\Standards\ProStructures\USA_Canada_Imperial\Rebar\Detailing\Metric\
Directory does not exist

Parents
  • Hi Robert,

    I have faced the same issue after upgrading to latest OpenBuildings Update 7, but only with new Workset, which I was trying to create.

    After some investigation and help from my colleague Marc Thomas, we discovered that new Workset is created with standard configuration, which is missing many important data required for it to work smoothly with Prostructures integration.

    If you are facing this issue with new Workset, then you can fix this by just copying all content from existing workset's *.cfg file and pasting it into your own workstet's *.cfg.

    After pasting everything from existing workset to my own one, OBD started opening all files from this new workset without any issues.

    Hope this will help you.

    Best Regards,
    Kestutis Mitkus

    Application Engineer, Building, Structural & Plant

     

Reply
  • Hi Robert,

    I have faced the same issue after upgrading to latest OpenBuildings Update 7, but only with new Workset, which I was trying to create.

    After some investigation and help from my colleague Marc Thomas, we discovered that new Workset is created with standard configuration, which is missing many important data required for it to work smoothly with Prostructures integration.

    If you are facing this issue with new Workset, then you can fix this by just copying all content from existing workset's *.cfg file and pasting it into your own workstet's *.cfg.

    After pasting everything from existing workset to my own one, OBD started opening all files from this new workset without any issues.

    Hope this will help you.

    Best Regards,
    Kestutis Mitkus

    Application Engineer, Building, Structural & Plant

     

Children