I've upgraded from version 6 to 7 and am having issues with a custom configuration. I will like to keep the dataset on the C:\ as I had done prior to this upgrade.
I followed the instructions as per this article on Configuring the Datasets Root Folder Location and the section on Use datasets on C:\drive. Though after running the Structural Dataset Upgrade I received this error.
I can confirm from Configuration Explorer that the following are still in the default location on the C:\
_TF_WORKSPACEROOT
TF_DATASETS
TFDIR
Also as part of the custom configuration I have placed a copy of the worksets template BuildingTemplate_AU.cfg into the Organization directory on the Network and renamed to 01_DATASET.cfg. I have a feeling this is causing the problem but it was working in v6 but am not sure.
I have attached a bcf from Config Explorer of the configuration.
OpenBuildings Designer CONNECT Edition-BGER-BGER WorkSet_20200901.bcf
see: https://communities.bentley.com/products/building/building_analysis___design/f/aecosim-speedikon-forum/201952/opening-building-designer-update-7
reinstall U6, you can't use U7
Which part of the post are you referring to?
U7 works running locally but not on the network. I would of thought Bentley would of tested this out thoroughly before rolling out the update.
HI Steve
I have already followed along to the wiki and the section Use datasets on C:\ drive:
It would be appreciated if someone could read the bcf file I attached or they could attach a bcf file of a working custom config with the dataset on the C:\ for users to compare.
On a side note do you know what is the future of Configuration Explorer? some of the functionality has been left out of CONNECT like the ability to compare to configurations (bcf's) Also the description for the variables hasn't been given, though I also have seen these have been neglected in OBD too.
Hi Simon,
I don't see a BCF file attached to your post. So, I've zipped one that I just created using the UK dataset for comparison purposes. OpenBuildings Designer CONNECT Edition-Building_Examples-BuildingTemplate_UK.zip
Hi Steve
The BCF was attached to my original post but I will attach it again.
Thanks for the BCF, I will see if I can see where I'm going wrong
OpenBuildings Designer CONNECT Edition-BGER-BGER WorkSet_20200901.zip
I've been going back and forth between your BCF and the delivered UK version and found that sure enough, dataset.cfg is not being loaded. So the error message is accurate.
I see that you have a custom 01_DATASET.cfg file loaded from the Organization folder and it defines the command to load dataset.cfg:
Since TFDIR is defined as the typical "$(TF_DATASETS)$(TF_DATASETNAME)\," Is there a dataset.cfg file under the R:\CAD Admin\04 - Bentley\WorkSpace\OpenBuildings CONNECT Edition\Datasets\Dataset_AU\ folder? If not, then you'll need to copy a valid U7 version (including the PS variables) to that folder.
Thanks for looking into this, don't you miss the bcf compare tool that has been removed from the latest Configuration Explorer?
Up until update 7, I had been using 01_Dataset.cfg file as common variables across worksets, instead of these being repeated in every Workset.cfg file.
If you look further than TFDIR, TF_DATASETS is defined as $(_TF_WORKSPACEROOT)Datasets\ and _TF_WORKSPACEROOT is defined as $(USTN_CONFIGURATION). I have $(USTN_CONFIGURATION) set to C:/ProgramData/Bentley/OpenBuildings Connect Edition/Configuration/ ConfigurationSetup.cfg so this should point TFDIR to the C:/ location shouldn't it? However when I start up OBD _USTN_CONFIGURATION gets overwritten to the _USTN_CUSTOM_CONFIGURATION.
Before starting OBD
After starting OBD
Also in the BCF you sent you haven't set a path for _USTN_CUSTOM_CONFIGURATION which is what I am trying to achieve so you won't be experiencing the same behaviour. I want the Workspaces and Organization directories to live on the server but the Datasets to live locally on the C:/.
I'm thinking I need to define the location for the _USTN_CUSTOM_CONFIGURATION elsewhere in another startup script. This would be my preference too so I wouldn't have to go around and change the ConfigurationSetup.cfg on every users machine.
Huh... the result is just like the "root folder location" wiki; i.e ., pointing to the network drive instead of the root c:\. Of course, the steps for Update 7 are the opposite of Update 6 and earlier, and you'll also need to un-define TF_WORKSPACEROOT and then re-define it in WorkSpaceSetup.cfg. Now I am wondering if the load sequence is a factor...
What do you mean by un-define _TF_WORKSPACEROOT?
I have defined it in WorkSpaceSetup.cfg as required in Updated 7
However, _USTN_INSTALLED_CONFIGURATION is still set to the C drive location so this must be ignored?
It would be good if Bentley could sort this out as I've wasted too much time trying to fix what wasn't broken before this update.
Un-defining TF_WORKSPACEROOT then re-defining it, is the last section of that wiki, titled "To use delivered datasets on C:\ drive".