When we come to ad-hoc fixes and trade-offs, there is no right or wrong. Once again, this solution may cause the least headache in my case, but it may not necessarily work for you. I inserted an installscript function right after RemoveExistingProducts custom action to scan and remove unwanted leftovers. After considering all side-effects, I also use one of those ad-hoc fixes. Some ad-hoc fixes have been proposed on the Internet as well, but they require some trade-offs in management later on.
It's too bad since there is still no official way to fix this case unless I convert the entire project to static components. That explains why the issue cannot be detected in our testing. The issue can be detected mostly on real systems in which data has been using daily and many other software installations has been done after ours. After researching around, I recognized the reason was that all those leftover files and folder in removal were dynamic-added components. Even worse, sometimes, upgrade is successful but software cannot function. Therefore, the file system was mixed randomly between old and new files after upgrading. I found that there were a lot of files and folders couldn't be removed from the target system. I couldn't figure it out until taking one piece of uninstallation log from the field. The number of reports are increasing weekly. However, from the field, there are still reports saying that upgrade is failed. All previous files are removed and new files are copied into target system correctly. The fact is that, my major upgrade works perfectly in in-house testing. I've observed a very tricky case in troubleshooting recently. MSI (c) (BC:AC) : MainEngineThread is returning 0 MSI (c) (BC:AC) : Cleaning up uninstalled install packages, if any exist
MSI (c) (BC:AC) : Grabbed execution mutex. Product Name: MySetup 2.5 64-bit Product Version: 2.5. MSI (c) (BC:AC) : Windows Installer installed the product. MSI (c) (BC:AC) : Product: MySetup 2.5 64-bit - Installation operation completed successfully. MSI (c) (BC!04) : PROPERTY CHANGE: Adding IS_MAJOR_UPGRADE property. It ends up with two program items in add/remove program after upgrading. With 4 digit version number in Major upgrade, installation log still says that IS_MAJOR_UPGRADE is set to Yes and upgrade is successful, but it's not a valid major upgrade.
0 kommentar(er)
