Hi
I've made some changes to where microstation looks for workspaces and worksets. It works great except when I create a new workset. I have to restart microstation for the new workset to be visible. How can I solve this?
Robert
Can you post your configuration file where those variables are being defined?
Also, at what level in the configuration is the configuration file being loaded (System, Application, Organization, etc)?
Rod WingSenior Systems Analyst
In my organization's standards.cfg-file I've put the line:
_USTN_WORKSPACESROOT = R:\Bentley\Workspaces\
Thanks for your reply Rod.
I actually have _ustn_custom_configuration set to a different location. The reason for this is a legacy from before my time, but the servers back then were not as fast as they needed to be. So the organization folder is mirrored from a server to C: on every computer log in, this way the files were always stored locally. This also meant the users couldn't change anything they're not supposed to change, or it would get overwritten on the next login, which has been a great benefit and is why we still go with this workflow.
But we couldn't use this for workspaces/worksets since users are writing data to those files. Not just reading. So the organiztion-folder and workspaces/worksets are separated.
I tried to set the workspacesroot-variable in the workspacesetup.cfg and configurationsetup.cfg, stored in "C:\ProgramData\Bentley\OpenBuildings CONNECT Edition\Configuration" My thought was that maybe these files would be reloaded after a workset creation. But it didn't help.
Not sure what to try next.
I've had issues in CONNECT with creating dgnlib files, and them not being recognized until I restart MicroStation, but never the WorkSets.
Robert Högberg said:Not sure what to try next.
Without taking a deep dive into your configuration it's hard to say.That being said, I think the next logical place to look is your _USTN_WORKSETSROOT and _USTN_WORKSETROOT variable definitions. Both where in the configuration they are being defined, and the actual definitions.
I noticed that when I create a workset without a template I don't need to restart the program, the list of worksets are updated right away. Is that how you always create worksets?
Not always, but it that solves your problem that seems like a simple solution.
No, it doesn't fit my needs. I have to use a specific workset as seed.
But at least I know where the problem is.