configuration explorer

RE: configuration explorer

MaryB — Tue, 12 Oct 2021 18:04:22 GMT

Done!

RE: configuration explorer

Marc Thomas — Tue, 12 Oct 2021 16:26:04 GMT

You could all pile onto the MicroStation Ideas page, this one in particular: Request a configuration management tool | MicroStation Ideas Portal (aha.io)

The Ideas page carries a lot of weight with product management.

RE: configuration explorer

MaryB — Tue, 12 Oct 2021 13:03:29 GMT

You could always file a Service Ticket and ask them to fix the Configuration Explorer. If enough of us do that, maybe they'll make the necessary changes.

RE: configuration explorer

PH — Tue, 12 Oct 2021 07:15:23 GMT

Hi Mary,

Thanks for your reply. I know the the -debug parameter, but the configuration explorer is much more capable of displaying parent-child relations in the variables. I use the -debug option often, but if I have really a problem in my configuration I use configuration explorer to examine it in depth. And then it would be nice if I didn't have to mess around with moving network configurations to the default program data\configuration folder to have the configuration explorer pick up the desired workspaces and worksets..

RE: configuration explorer

MaryB — Mon, 11 Oct 2021 21:00:20 GMT

No, Configuration Explorer is not really compatible with networked workspaces, or command line switches.

The next best thing (not great, but surprisingly helpful) is to add the switch -debug=5 to the end of your shortcut. This will create and open an msdebug.txt file (that you can save anywhere you like) of all your configuration variables. What is most useful is that the =5 lists all of your variables at the end of the file, with their definition AND any level of configuration where that value changes. Here is one of my variables that gets its definition from several config files:

MS_RFDIR         : System       = M:\Bentley\ORD\Configuration\WorkSpaces\WorkSets\Dgn\  
                 : Application  = (null)
                 : Organization = (null)
                 : WorkSpace    = M:\Bentley\ORD\Configuration\WorkSpaces\Standards\Sheet Borders\;M:\Bentley\ORD\Configuration\WorkSpaces\WorkSets\Dgn\
                 : WorkSet      = M:\Bentley\ORD\Configuration\WorkSpaces\WorkSets\Standards\Sheet Borders\;M:\Bentley\ORD\Configuration\WorkSpaces\Standards\Sheet Borders\;M:\Bentley\ORD\Configuration\WorkSpaces\WorkSets\Dgn\
                 : Role         = (null)
                 : User         = (null)

It's not as pretty as Configuration Explorer, and it can still be a challenge to track down exactly where a variable goes off the rails, but it's the most useful msdebug.txt format I've seen.