I have just installed Update 8 using CONNECTION Client but it has overwritten all my custom files!!
Why has it done this?
Why doesn't it remember that we have a server location to pint to?
Why don't we get the option to point to a server location when using CC for the upgrade?
Whys is this always so difficult?
but it has overwritten all my custom files
what files specifically ? and where are these files located ?
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
ConfigurationSetup.cfg in "C:\ProgramData\Bentley\MicroStation CONNECT Edition\Configuration"
are you setting multiple variables here or just the _USTN_CUSTOM_CONFIGURATION ?
Just the following which is generated by the installer:
[General]_USTN_CUSTOM_CONFIGURATION=I:/CONNECT-workspace/
[SetConfiguration]%if !defined (_USTN_USER_CONFIGURATION)%if defined (_USTN_CUSTOM_CONFIGURATION) && ($(_USTN_CUSTOM_CONFIGURATION) != "") && exists ($(_USTN_CUSTOM_CONFIGURATION))_USTN_CONFIGURATION = $(_USTN_CUSTOM_CONFIGURATION)%endif%endif
Any news for this issue?
It took some time, but I went thru the same steps. I had update 7 installed and using a custom configuration. I opened the connection client and upgraded to update 8. I had no issues. It came thru and recognized my custom configuration.
Now - if I had some additional variables in the ConfigurationSetup.cfg - these were removed/overwritten. This is not where this should be edited and added to - this should only be for redirecting the configuration root directory.
I am a bit confused though - initially you mention "but it has overwritten all my custom files"
but later mention one file and one variable.
Tim Hickman said:
am a bit confused though - initially you mention "but it has overwritten all my custom files"
but later mention one file and one variable
At the time I didn't know the extent of the problem caused by the CE upgrade. In the end I un-installed and re-installed picking the custom configuration, which then worked. All I can say is that when I upgraded to U8 it didn't recognise our network location as all out custom tools, etc where missing. It went back to a default install. This is not good it you want us to use CC for the upgrades. At the moment I don't trust CE enough to do this properly. This is why some of our CE installs are only probably U4!! Get this right and CC is the way to go but not at the moment!
I have tried the update several times and in each case it has worked - so I am unable to reproduce the issue.
But I do have some thoughts as to possible problems.
1. There were extra variables in the ConfigurationSetup.cfg which were overwritten. (not recommended)
2. There were modified configuration files in the delivered configuration directory structure. (not recommended)
3. The "configuration" option was not selected during the update to redirect MicroStation to the custom configuration.
Now with option 3 - I do agree that this should not be needed during an upgrade, but this is how it was developed. I have mentioned (argued) that this should not be needed, but as you see it is still functioning this way.
My guess Stuart is that you did not select the configuration option during the update, so your custom configuration was never added back to the ConfigurationSetup.cfg.