• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 463
  • Last Modified:

Uninstallation is not proper when an upgrade is applied

I have a previous version of the product (Validity Sensors with version 2.7.44 ) installed in platform windows xp, when i installed the latest version of the product (version 2.8.104) on the existing installation , it is updating the windows/system32 folder but if i go and see in the control panel the ADD/Remove shows two entries one with Validity Sensors 44 and the  other one with Validity Sensor 104.. My problem is that i want to have only one entry in the control panel with the latest version and the previous entry should not appear ... I tried to edit the .msi files using ORCA and tried many possibilities but i couldnt resolve , please help me .. I am not able to attch the .mis files here , pls suggest how can i send the .mis files so that someone can check that . I want to have some changes in the latest vesrion of the .msi file  rather than the previous version of the .msi file..Thanks a lot....
0
prasant_hyd
Asked:
prasant_hyd
  • 12
  • 11
1 Solution
 
prasant_hydAuthor Commented:
I have tried with being the Upgradecode remainign same and productcode is different . and i added removepreviousversion=true
Still it didnt remove the previous entry from add/remove..
0
 
Vadim RappCommented:
Check if there's an entry in the Upgrade table of the new package.

If there is, zip both msi's in one zip file, upload on rapidshare.com , or www.2shared.com , and give the URL.
0
 
prasant_hydAuthor Commented:
Hi thanks..
Yes the new package has an upgrade table ....and they share the same upgrade code..
I have uploaded the .msi zip files .. here is the link....
http://www.2shared.com/file/4221574/1ef41e0f/msi-44.html
http://www.2shared.com/file/4221580/9e01c6d9/msi-104.html
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
Vadim RappCommented:
ok, will take a look within next 2 hours
0
 
prasant_hydAuthor Commented:
Hi I have uploaded  one more .mis firl , that is the version -2.7.39
My main requirement is that it shud upgrade from 2.7.39 to 2.9.104 , you can ignore the 2.7.44 version...
the link for the .msi file is
http://www.2shared.com/file/4221665/72aea181/msi-39.html
0
 
Vadim RappCommented:
problem 1:
in version 104, that upgrade has max version = 2.7.1, which is lower than 2.7.39.

problem 2: even with #1 corrected, it did not upgrade because in the version 104:

current install is per-machine.  Related install for product '{567E8236-C414-4888-8211-3D61608D57AE}' is per-user.  Skipping...

i.e. v.39 is installed per-user, and 104 per-machine. No upgrade.

Also, here's some additional upgrade-related information that was generated - I have no idea how valid it is, but you may find it valuable.

Registry key 'ValRegEntry1.016EAFC7_DA3A_457E_A8D0_20F4EC53194F' is a new resource that needs to be added to a new component and assigned to a new subfeature.

File 'WinUSBCoInstaller_amd64.dll.016EAFC7_DA3A_457E_A8D0_20F4EC53194F' is a new resource that needs to be added to a new component and assigned to a new subfeature.

File 'WinUSBCoInstaller.dll.016EAFC7_DA3A_457E_A8D0_20F4EC53194F' is a new resource that needs to be added to a new component and assigned to a new subfeature.

File 'WdfCoInstaller01005_amd64.dll.016EAFC7_DA3A_457E_A8D0_20F4EC53194F' is a new resource that needs to be added to a new component and assigned to a new subfeature.

File 'WdfCoInstaller01005.dll.016EAFC7_DA3A_457E_A8D0_20F4EC53194F' is a new resource that needs to be added to a new component and assigned to a new subfeature.

File 'vfs201.inf.016EAFC7_DA3A_457E_A8D0_20F4EC53194F' is a new resource that needs to be added to a new component and assigned to a new subfeature.

File 'vfs201.cat.016EAFC7_DA3A_457E_A8D0_20F4EC53194F' is a new resource that needs to be added to a new component and assigned to a new subfeature.

Component 'ValDriverFiles3.016EAFC7_DA3A_457E_A8D0_20F4EC53194F' exists in the previous version and the keypath does not exist in the current install. The component's contents will be deleted during an upgrade.

Component 'ValDriverFiles2.016EAFC7_DA3A_457E_A8D0_20F4EC53194F' exists in the previous version and the keypath does not exist in the current install. The component's contents will be deleted during an upgrade.

Component 'ValDriverFiles1.016EAFC7_DA3A_457E_A8D0_20F4EC53194F' exists in the previous version and the keypath does not exist in the current install. The component's contents will be deleted during an upgrade.
0
 
prasant_hydAuthor Commented:
Hi Thanks ..
Unfortunately it didnt work for me ..Please help me..
As suggested by you i did the following
1: For prob #1 :
In version 104 i changed the upgrade which has the previous value 2.7.1 , i changed to 2.8.2

2: For prob #2
I found that the ALLUSERS property in both 39 and 104 .msi file has the value 1 .. so i didnt change anything , pls tell me what shud i put the ALLUSER value for 104 version..

Actually it updates the dlls and binary in WINDOWS\system32  .. But in ADD/REMOVE Programs still i find twi entries
I want to have an entry showing Validity Sensors Softweare which has the version 104 and the previous entry shud be eliminated ... pls help
0
 
Vadim RappCommented:
You need to look into per-user / per-machine issue. Produce detailed installation log (google for installer logging), and look in the log.
0
 
Vadim RappCommented:
look at the last Set Property in the UI sequence.
0
 
prasant_hydAuthor Commented:
Hi ,
I tried to enable to see the log but i cudnt see the log file ..
ANyways what is that i have to check in the Property UI Sequence
0
 
prasant_hydAuthor Commented:
I actually changed the version in 104 and when i tired upgarding from 44 to 104 it removed the 44 version from control panel but i want this to happen from i try to upgrade from 39 to 104...
In 39 it s per user but the ALLUSERS property is set to 1 , same in 104 too..
pls guide
0
 
prasant_hydAuthor Commented:
Onething i want to as is that if a product has been installed with "per-user" then if the latest version with "per-machine" has been installed on top of it.. what could be the possible problems , onething i see is that in control panel Add/remove i find two entries
0
 
Vadim RappCommented:
> what is that i have to check in the Property UI Sequence

In the version 39, that's where ALLUSERS property is cleared. That's why it's installed per-user.

> I tried to enable to see the log but i cudnt see the log file ..

you can generate it where you want by running

msiexec /l*v c:\install.log /i "c:\my path\mypackage.msi"

> what could be the possible problems , one thing i see is that in control panel Add/remove i find two entries
none.

However, those warnings that I posted earlier, probably do indicate potential problems. Would be better to look into that. Depends though on the audience that is supposed to run this installation.
0
 
Vadim RappCommented:
one more thought about leaving both installations: check what happens if the user installs new version into another directory; so new files don't overwrite old ones.
0
 
prasant_hydAuthor Commented:
Hi ,
I installed the version 39 first then on top of this i installed version 104..
i have attched the log files in
http://www.2shared.com/file/4228080/e5c24bb8/39install.html
http://www.2shared.com/file/4228081/92c57b2e/104install.html
i couldnt conclude anything from this log... plz help..
i will try to install ner version in a different directroy and update you the results ..
Need you suggestion....thanks
0
 
Vadim RappCommented:
suggestion on what? as you saw, I already produced those very logs, and found in the log of 104 the line that said why it skipped the upgrade - because old version was installed per-user. I also told you why it was installed per-user - because there was Set Property statement in the script that actually specified that. If version 39 is what's installed, then the only way to upgrade it is to install version 104 per-user as well. See http://community.acresso.com/showthread.php?t=184281 as an example.
0
 
prasant_hydAuthor Commented:
I appreciate your patience in answering my questions..
Well i even tried putting ALLUSER="" and then ALLUSERS=2 .. in 104 version and installed over 39 version..
The thing is that i still saw 2 entries in the Add/Remove ..

But when i installed and on top of that i installed 104, i saw only one entry in Add/Remove showing the latest i.e 104.. the changes i made in 44 is  that i changed the Max version to be 2.8 earlier it was 2.7.1.. hence it worked ..
In 39 also i am doing the same.. But still 2 entries are there in Add/Remove..

I dont want two entries at any case , i.e the biggest problem for me ...

0
 
Vadim RappCommented:
I did not see v.44, maybe this statement does not exist in 44. In 39, it does exist -see the picture. Even though ALLUSERS property initially exists in the table PROPERTY, this action forcefully sets it to empty value.


Capture-11-06-00001.png
0
 
prasant_hydAuthor Commented:
Thats correct that means in 39 its per user..
thats the reason i chaged the ALLUSER to be "" then 2 too in 104..
How can i make the action to force 104 to per user even if whatever is the value of ALLUSERS in the Property section........
0
 
prasant_hydAuthor Commented:
I have never worked in either installshield or any windows packaging tools  before , this cuold be a silly things but as the customer doestn accept it and its an urgent issue , i am in a dilema and asking you.
0
 
Vadim RappCommented:
Remove SET PROPERTY ALLUSERS=1 from the script and property ALLUSERS itself from version 104.

If you can't, consider hiring someone who can - for example, click on my nickname for contact information.
0
 
prasant_hydAuthor Commented:
Hi,
Thanks. The problem is that the previous version(39) has already been installed "per user" and the latest(104) is " per machine" . I want to know if we can migrate from "per user" to " per machine" ..
If we can then how ?? What are the possible drawback..

0
 
Vadim RappCommented:
it appears you asked this and I answered in http:Q_23897799.html
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 12
  • 11
Tackle projects and never again get stuck behind a technical roadblock.
Join Now