Configuring AECOsim (BBES) to allow for symbol manager modifications

We're currently fighting with AECOsim on the electrical side trying to edit content in the symbol manager. I can open the symbol manager fine but we'd like to be able to add new content and modify some existing content that we've seen issues with. Our database and other BBES components are stored in a shared network location (writeable). Our main workspace is in a location that is write protected (we're not using ProjectWise). Despite whatever variables I set I'm unable to edit/add content. I've tried using the BBES_DETAILED_CFG variable and it doesn't seem to make much different. I even tried pointing back to my local machine and am getting errors stating I don't have permissions. What are the proper variables to set to allow for editing this content?

  • Just to be sure - do the \metadata (application database) and _bbes folders (project database) in their current locations both have read/write permissions?



  • Also check read/write permissions to these folders:

    C:\Program Files (x86)\Bentley\AECOsimBuildingDesigner V8i Ss5\AECOsimBuildingDesigner\ServerApp\bin\

     ...\WorkSpace\BuildingDatasets\Dataset_US\symLibs\

    (this folder is wherever you have located the shared workspace, or on your local machine as mentioned in your testing)

    Not every user needs write permissions to the symLibs folder, only users that are editing or creating symbols. 



  • Double checked, everything is set to read/write. No clue what the issue is, followed the documentation in the Electrical Wiki and I have it configured to what I believe is proper. I think BBES hates me :(
  • Unknown said:
    Double checked, everything is set to read/write. No clue what the issue is, followed the documentation in the Electrical Wiki and I have it configured to what I believe is proper. I think BBES hates me :(

    Nah... how could Electrical hate someone with that avatar?   Hehehe...   :)

    Do you have the ability to revert to an out of the box configuration without too much effort?   If so, perhaps it would be beneficial to start there (assuming that it does provide the expected results) and then move towards your "real" configuration step-by-step to determine where it's failing.

    If that is not an option, maybe using Configuration Explorer will help better detail exactly that is pointing where, and help identify any anomalies:



  • So... I redid my configuration several times in hopes this would start working but no luck.

    I should note that we are using a client supplied workspace and I couldn't deviate too much from what they provided.

    I decided to cheat...

    I created a separate configuration, pointed to my project database and symlibs and was able to create/edit without issue.

    We've used the product before so I was pretty sure I knew what I was doing.

    Now my users can use a separate shortcut to create the content they need and then close and jump back into the client workspace. Clearly there is something in the client setup that is breaking this functionality.

    I'll make sure to let them know so others don't suffer as we've been.