| Author |
Message |
michalk
Joined: 29 Aug 2014
Posts: 211
|
|
 Installation path changed by update process |
 |
Usually I install programs into custom directory located on other partition than system one.
I noticed, that SA updater installs the newer version into default its directory (c:\Program Files (x86)\SQL Assistant 7\) instead of the one chosen for previous installations. IMO installer should re-use the path.
|
|
| Wed Oct 21, 2015 4:05 am |
  |
 |
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7948
|
|
| |
|
I believe it actually does, or at least it's supposed to do that, but if the program has been installed in multiple places, it picks the first one it finds in the registry. To update an instance in a customized location, please download the setup from the web site and run it manually not using check for updates function.
|
|
| Thu Oct 22, 2015 1:10 am |
|
|
michalk
Joined: 29 Aug 2014
Posts: 211
|
|
| |
|
Hello
I've checked registry settings, make sure they point properly to current installation location (in my case D:\_programs\SQL Assistant 7\". Unfortunately the updater is still trying to install SA into "Program files (x86)\SQL Assistant 7\" dir.
Even installer itself suggests program files directory, while there is SA already installed so it should know its location.
|
|
| Mon Mar 07, 2016 5:29 am |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7948
|
|
| |
|
Hello. I'm going to log this as an issue in our support system. It requires further investigation.
|
|
| Mon Mar 07, 2016 10:16 am |
|
|
michalk
Joined: 29 Aug 2014
Posts: 211
|
|
| |
|
After some while, I can confirm none has been improved (incl. recent two v9 builds)
Still, installer run in update mode (spawned by SA itself) silently installs into "Program Files (x86)" directory, while previous build was in another location.
When starting installer in install mode, it shows "Program Files (x86)" directory as default path.
After year of waiting, it's starts to be a bit annoying.
with regards
|
|
| Thu Nov 03, 2016 11:25 am |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7948
|
|
| |
|
I'm so sorry for the inconvenience. This ticket isn't yet handled. It's still in the queue.
|
|
| Thu Nov 03, 2016 12:17 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7948
|
|
| |
|
Actually, I have missed some notes in the related ticket. there were some related changes in 9.0.176, which if I understand them correctly, may resolve the issue at hand. would you please give it a try and upgrade to the latest build?
|
|
| Fri Nov 04, 2016 9:35 am |
|
|
michalk
Joined: 29 Aug 2014
Posts: 211
|
|
| |
|
I'm on 9.0.176.
If something has been improved, it didn't show up while updating to this version.
|
|
| Fri Nov 04, 2016 9:44 am |
|
|
michalk
Joined: 29 Aug 2014
Posts: 211
|
|
| |
|
I can confirm, the issue has been fixed in build 9.0.185.
I've checked update as well as installation process.
Thank you
|
|
| Mon Nov 21, 2016 10:50 am |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7948
|
|
| |
|
Thank you very much for confirming that
|
|
| Mon Nov 21, 2016 11:54 am |
|
|
|
