Connect update 4 does not recognise worksets

Updated to update 4 and now I cannot get connect to recognise my worksets. 

Workspaces are defined and recognised, but on selecting a workspace the only option I have is to create a new workset(defaulting to C drive) as none exist?? 

I have tried directly defining worksetsroot in the workspace cfg, and also in the workspacesetup.cfg but no luck. 

  • you might want to post what it was that you did to fix your issue....

    Timothy Hickman

    CADD Manager | CADD Department

    timothy.hickman@colliersengineering.com

    Main: 877 627 3772| 

    1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691

  • I would if I knew!! changed/replaced cfg files nothing working, changed back to original file and hey presto, working.
  • Tim

    there is an issue with the auto updates.....  

    It replaces the C:\ProgramData\Bentley\CONNECT Edition\Configuration\WorkSpaceSetup.cfg file.  

    Thus, if a user defines their setup via this file, it will reset it to the default one when the update takes place.  A SR has been raised on my behave, but I do not have it to hand.

    In my opinion it is best practice to change the location of the workspaceSetup.cfg file and define it in the mslocal.cfg as

    _USTN_CONFIGURATION : $(MSDIR)Config/

    Or a path you know....

    Ian 

  • Hi Ian,

    Did you follow the recommendation from Microstation CONNECT edition Readme file available from Bentley Communities, Here http://communities.bentley.com/products/microstation/m/microstation_gallery/272430

    This information is also available during the installation by clicking in the question mark. see images below:

    Configuration changes in MicroStation CONNECt update 4:

    In MicroStation CONNECT Edition Update 4, you can define two Configuration locations at install time

    •  First is the delivered or installed configuration.
    • Second configuration is the Custom or Shared Configuration, which can contain user’s WorkSpaces and WorkSets.

    To change the path of this Configuration, in the Configuration page, select the Custom Configuration (plus Delivered Configuration) radio button and then set the path in the Custom Configuration field. This Custom Configuration path is in turn written in the ConfigurationSetup.cfg file. The WorkSpaces created in this Configuration are displayed as Custom Configuration WorkSpaces in the Work Page.


    If you have a previous release of MicroStation CONNECT Edition installed, and have custom WorkSpaces created, then while upgrading you should point the Custom Configuration field to the folder that contains the WorkSpaceSetup.cfg file of your Configuration.

    If the custom WorkSpaces were created in the delivered Configuration folder (C:\ProgramData\Bentley\CONNECT Edition\Configuration), then you should point the Custom Configuration field to that location. While upgrading, the Custom Configuration field by default points to C:\ProgramData\Bentley\CONNECT Edition\Configuration.

    Regards
    Maria



    Maria Garcia