About Shobha_Dashotta

Shobha_Dashotta · ‎Jan 03, 2017

Hi, We need to support installation of our product into directories with unicode characters in the path ( non-English multi-byte). We are using IS 2013 and the installation summary shows '?????' as the install path and the installation fails when it tries to access the install path. I read that the unicode support has been added since IS 2015. I am trying the IS 2016 trial version but the problem persists. How do I enable the non-english character support in my Installer? Thanks Shobha

Shobha_Dashotta · ‎Mar 25, 2015

Thanks Dan for the response. That won't work for our requirement I have a working upgrade now. All the upgrade paths are now supported. After spending days of efforts on this, I realized that when I added the entry in the upgrade table a custom action ( rather a IS standard action) ISSETALLUSERS got added . I removed that custom action. Also, not sure if it helped but the ism has a table called " Installshield", the entry there for "OnUpgrade" was 0. I made it 2 since 2 is the value for an UpgradeFrom property. With these two changes in place, I was able to also upgrade from 1.0.1.x to 1.0.1.y. Regards Shobha

Shobha_Dashotta · ‎Mar 20, 2015

I have referred to that. The weird part is that before I added the support of "upgrade" from 5.x , the upgrade of 1.0.1.x to 1.0.1.y was working fine with no entries in the upgrade table. If the windows Installer not using the fourth bit for comparison then it shouldn't have considered earlier too. Thanks Shobha

Shobha_Dashotta · ‎Mar 17, 2015

Thanks Michael. Finally the the software upgrades from a previous (higher) version to a newer (lower) version with success. These are some of the other things I had to do after changing the product code. 1. Even if it is a major upgrade, we did not want to uninstall everything and then install but that was happening. So in a custom action after InstallValidate, I unset the value of REMOVE property as it was getting set to ALL. A custom action UnistallCommit had that condition set. 2. In the upgrade table, added the major upgrade item and set it any earlier version. 3. The install was happening fine but, something was going wrong in the end and this would rollback everything. After hours and hours digging through logs and looking online, I changed the sequence of the RemoveExistingProduct to above CostFinalize. This made the upgrade run successfully. Both the upgrade paths 5.x.y to 1.0.1 and 1.0.0 to 1.0.1 are now supported. But now, I am unable to upgrade from 1.0.1.x to 1.0.1.x+y. The installer does not complain and I guess that's because it is comparing the first three fields only. This was happening earlier. How can I fix that ? Thanks Shobha

Shobha_Dashotta · ‎Mar 06, 2015

Hi, I want to be able to support "downgrade" in my installer. Essentially, need to support upgrade from the older 5.X version to the new 1.0 version. It is not a major upgrade so we are not changing the product code. But, the standard message of "Another version of the product is already installed ...." is displayed. I made changes to the Upgrade table and made the min and max versions as " ALL VERSIONS". I even tried to remove the custom Action IsPreventDowngrade from the Install Sequence. But it continues to block the upgrade. Any idea how I can make this possible? Thanks Shobha

Shobha_Dashotta · ‎Mar 02, 2015

We are facing the same issue. Did anyone find a solution to it? Thanks Shobha

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:10 PM

Support for non-English characters in install path

Re: Need to disable ISPreventDowngrade

Re: Need to disable ISPreventDowngrade

Re: Need to disable ISPreventDowngrade

Need to disable ISPreventDowngrade

Re: IS2013 Upgrade to previous version not working

Support for non-English characters in install path

Re: Need to disable ISPreventDowngrade

Re: Need to disable ISPreventDowngrade

Re: Need to disable ISPreventDowngrade

Need to disable ISPreventDowngrade

Re: IS2013 Upgrade to previous version not working