I am trying to setup a number of other AGENCY workspaces for ORD 2022 R1 which is the first version to include the Manage Configuration tool. A few of these are proving problematic and I need to evaluate what is occurring during their processing. Are there command line switches that will result in one of the Manage Configuration Workspaces to load that I can use with a -debug command line switch. And can that same command line switch be used with the Configuration Explorer?
I'm marking this Solved, even though it is not. At least someone with the same issue will see this and know that it is not user error but a "bug".
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
Hi Chuck, I have encountered something similar and have just found listed a bug that was filed a few days ago that may relate to this.
Please file a service case referencing bug 1270485 to have your concerns linked to this item.
Regards
Marc
Answer Verified By: caddcop
I never got this to work.
The Manage Configurations redirects all of these to new locations and the shortcuts cannot locate the CFG file and the NoWorkspace NoWorkset CFG's are used.
Looking at msconfig.cfg, lines, Line 347-349 which test for the _USTN_CACHECFG succeeds which defines _USTN_WORKSETNAME and _USTN_WORKSPACENAME and _USTN_LAST_ACTIVE_CONFIGURATION.
You would think this would allow the MSDEBUG.TXT to use these.
But lines 376-381 fail even though _USTN_WORKSPACENAME is defined. I believe it is because the next test looks for _USTN_WORKSPACENAME in the _USTN_WORKSPACESROOT folder, but I suspect that the path defined in _USTN_LAST_ACTIVE_CONFIGURATION is never used to redefine _USTN_WORKSPACESROOT.
As a result, eventually the no workspace/workset code is used.
I need help with this.
The -WR switch redefines the variable -USTN_WORKSPACEROOT to whatever path you supply. The example from using the-? (help) switch, is:
-wrC:\Bentley\Workspace\
Another possibility is to use the -WC where you specify a CFG file to use,
-wcC:\Bentley\Workspace\Config\myconfig.cfg
This option requires that the configuration file specified needs to also include any standard configuration files. Usually, this would be using a %include mslocal.cfg, of a modified version of that file.
The -WS option is similar to -WR, except that you can define (or redefine) any variable. The example from the help list is:
-wsMS_SECURITY_LEVEL=HIGH
This can be a built-in variable, or a custom, user-defined variable.
thanks for the answer, but can you please specify the "configuration path", I do not know what to write after the -wr switchregards Rik