• State Suggested Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 119 subscribers
  • Views 3472 views
  • Users 0 members are here

Command Line Arguments not processing in Update 4

Ray Leaman
Offline

Since I have loaded MicroStation CONNECT I have not been able to get command line arguments to process.  For example, using this line to start MicroStation:

"C:\Program Files\Bentley\MicroStation CONNECT Edition Update 3\MicroStation\microstation.exe" -wr\\HSSIENG\Resources\HS\MS-CONNECT\CONFIG\

does not process the WorkSpaceSetup.cfg in \\HSSIENG\Resources\HS\MS-CONNECT\CONFIG\

It worked fine with Update 3.

Parents
  • 0 Offline
    OK, I may be a little late to this post, but the command line switches have changed since V8i.

    From the CONNECT help file:
    "-WR<path> Specifies the path to the Configuration root (_USTN_CONFIGURATION). For example:
    -wrC:\Bentley\Configuration\. This command line argument can be used to access a shared Configuration and is displayed as User Configuration in the WorkSpaces drop-down list in the Work Page. "

    With that, Ray is correct, Update 4 does have a problem. I tried to open MS U4 in ProjectWise, to see what doesn't work, and it wrote to the C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration\ConfigurationSetUp.cfg file. This file blocked my ability to use the -wr switch on the network. The file had this in it:

    [SetConfiguration]
    %if defined (_USTN_CUSTOM_CONFIGURATION) && ($(_USTN_CUSTOM_CONFIGURATION) != "") && exists ($(_USTN_CUSTOM_CONFIGURATION))
    _USTN_CONFIGURATION = c:/temp/d0247200/
    %endif

    Once I removed those lines, the -wr switch returned to working as normal. There is a problem in whatever Bentley is doing to adjust that file on the fly. The -wr switch should lock the location of WorkSpaceSetup.cfg, but it does not.
Reply
  • 0 Offline
    OK, I may be a little late to this post, but the command line switches have changed since V8i.

    From the CONNECT help file:
    "-WR<path> Specifies the path to the Configuration root (_USTN_CONFIGURATION). For example:
    -wrC:\Bentley\Configuration\. This command line argument can be used to access a shared Configuration and is displayed as User Configuration in the WorkSpaces drop-down list in the Work Page. "

    With that, Ray is correct, Update 4 does have a problem. I tried to open MS U4 in ProjectWise, to see what doesn't work, and it wrote to the C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration\ConfigurationSetUp.cfg file. This file blocked my ability to use the -wr switch on the network. The file had this in it:

    [SetConfiguration]
    %if defined (_USTN_CUSTOM_CONFIGURATION) && ($(_USTN_CUSTOM_CONFIGURATION) != "") && exists ($(_USTN_CUSTOM_CONFIGURATION))
    _USTN_CONFIGURATION = c:/temp/d0247200/
    %endif

    Once I removed those lines, the -wr switch returned to working as normal. There is a problem in whatever Bentley is doing to adjust that file on the fly. The -wr switch should lock the location of WorkSpaceSetup.cfg, but it does not.
Children
No Data
Communities
Support and Services
Training and Learning
Social Media