I have been using MicroStation CONNECT since its first release. I've had no problems with installation or configuration until Update 17.
I'm attempting to install and use Update 17 with a custom configuration location. That location was in use successfully with Update 16. I specified the configuration location (L:/Bentley/CONNECT/LA Solutions/) during installation.
When I start MicroStation Update 17 I see this page...
When I click the WorkSpace button, I see this...
MicroStation can't see my existing workspace or worksets.
When I click the Create WorkSpace button, MicroStation crashes. Clearly, I did something unexpected during installation. Can anyone provide inspiration?
I've attempted to install Update 17 several times. On previous failures, I deinstalled and returned to Update 16, which contined to work properly. This latest time, I uninstalled Update 16 and cleaned out the configuration folder (C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration) before installing Update 17.
C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration
Hello Jon, have you made any progress with this?
Marc Thomas said: have you made any progress with this?
It took a lot of work!
I manually uninstalled Update 16 and removed its folder. I then did a fresh install of Update 17 leaving the configuration as delivered. Subsequently I modified the configuration to point to my network config. folder. But why did I have to go through that unwanted rigmarole? Sixteen previous versions of MicroStation CONNECT have behaved as expected.
There remains stuff hanging around from previous, fully working, versions of MicroStation CONNECT. For example, a few years ago I installed ProjectWise Explorer, which adds pw.cfg to MicroStation's config/appl folder. Even though I no longer use PW Explorer, that file magically reappears (it causes a PW login dialog to appear when starting MicroStation). Given that I deleted the entire MicroStation folder before installing a fresh copy of Update 17, how did that file get there?
Regards, Jon Summers LA Solutions
Using the Manage Configuration feature could have avoided this. However I can anticipate you observing a) why do I need to use thsi new thing just to carry on as I did before, and b) where was I told about the feature...
There are some notes about it in Configuration Tips - Manage Configuration Utility. It's a neat tool that enables the use of multiple configurations so is useful in various scenarios, for instance having a current production configuration alongside a totally separate development configuration.
In response to a number of requests, we are working on a variable that will turn the feature off for the 17.1 release.
Regarding ProjectWise; pw.cfg is installed by all applications. It could be that there is a residual registry entry, either HKEY_LOCAL_MACHINE\SOFTWARE\Bentley\ProjectWise\Path or HKEY_CURRENT_USER\SOFTWARE\Bentley\ProjectWise\Path that is invoking the PW login dialog. Delete these if they exist.
Also check for two folders:C:\Program Files\Bentley\ProjectWise\binC:\Program Files (x86)\Bentley\ProjectWise\bin
Delete them if they exist.
All of that should have been cleared out by uninstalling PW Explorer but maybe the clear up failed? I'm guessing.
I have PW Explorer installed, to avoid the prompt I set a Windows user variable:
Marc Thomas said:Using the Manage Configuration feature could have avoided this
The Manage Configuration feature led to MicroStation abruptly crashing. That's why I took the long route to completely uninstalling Update 16, removing its directory, and installing a fresh Update 17.