Hi,

I am working on BCM Intercarrier application.

I need to do major upgrade for the previous version of BCM Intercarrier application.
This is a setup captured application. (Including newer and older version applilcations)

According to our standards we need to give the attribute value as 517, Major version is the curren application version, min version column should be empty, Langugage is the previous version launguage.

Older version: 91.01.48
New version : 92.01.27

I have kept the remove existing products in between install validate and install initialilze.
I have added one property in Upgrade table and the same has been reflected in secure custom properties.

But after doing upgrade it is uninstalling the previous application but it is not installing the new version application.
When I install the newer version application alone then it is getting installed.

Could any body help on this?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Generate Log and analyse what it says
Answered 11/10/2009 by: mekaywe
Brown Belt

Please log in to comment
0
Hi,

I have checked the log file.
It is showing the below information.

MSI (s) (D4:D0) [15:13:53:684]: Disallowing installation of component: {AD96B6EE-470B-4EB3-B18C-19BB05B5D0DA} since the same component with higher versioned keyfile exists
MSI (s) (D4:D0) [15:13:53:684]: Disallowing installation of component: {AD0667C2-58BA-4A3E-8914-A82789DAA6AB} since the same component with higher versioned keyfile exists
MSI (s) (D4:D0) [15:13:53:684]: Disallowing installation of component: {27F9CE4B-14E9-47E9-9B71-F7D2BBD51144} since the same component with higher versioned keyfile exists
MSI (s) (D4:D0) [15:13:53:684]: Disallowing installation of component: {9FF15636-9C5F-43FA-8B70-B888B4F8F667} since the same component with higher versioned keyfile exists
MSI (s) (D4:D0) [15:13:53:700]: Disallowing installation of component: {10048713-2C96-11D2-9A97-006097C4E452} since the same component with higher versioned keyfile exists
MSI (s) (D4:D0) [15:13:53:700]: Disallowing installation of component: {474F61F1-7342-11D2-A199-00A0C90AB50F} since the same component with higher versioned keyfile exists
MSI (s) (D4:D0) [15:13:53:700]: Disallowing installation of component: {997FA962-E067-11D1-9396-00A0C90F27F9} since the same component with higher versioned keyfile exists
MSI (s) (D4:D0) [15:13:53:700]: Disallowing installation of component: {3207D1B1-80E5-11D2-B95D-006097C4DE24} since the same component with higher versioned keyfile exists
MSI (s) (D4:D0) [15:13:53:700]: Doing action: SetARPINSTALLLOCATION
Action ended 15:13:53: MigrateFeatureStates. Return value 1.
MSI (s) (D4:D0) [15:13:53:700]: PROPERTY CHANGE: Adding ARPINSTALLLOCATION property. Its value is 'C:\Program Files\AMS\ic\CCB Client Suite\'.
Action start 15:13:53: SetARPINSTALLLOCATION.
MSI (s) (D4:D0) [15:13:53:700]: Doing action: InstallValidate
Action ended 15:13:53: SetARPINSTALLLOCATION. Return value 1.
MSI (s) (D4:D0) [15:13:53:700]: Feature: CCBIntercarrier; Installed: Absent; Request: Local; Action: Local
MSI (s) (D4:D0) [15:13:53:700]: Component: OprWFResrcView32ims.dll; Installed: Absent; Request: Local; Action: Null
MSI (s) (D4:D0) [15:13:53:700]: Component: PsmProviderBOC32ims.dll; Installed: Absent; Request: Local; Action: Null
MSI (s) (D4:D0) [15:13:53:700]: Component: it_atli4_vc60cios.dll; Installed: Absent; Request: Local; Action: Local
MSI (s) (D4:D0) [15:13:53:700]: Component: CcmSupplementalObjectsBOCClient32ims.dll; Installed: Absent; Request: Local; Action: Null
MSI (s) (D4:D0) [15:13:53:700]: Component: it_cfr_handler4_vc60cios.dll; Installed: Absent; Request: Local; Action: Local
MSI (s) (D4:D0) [15:13:53:700]: Component: licenses.txt; Installed: Absent; Request: Local; Action: Local
MSI (s) (D4:D0) [15:13:53:700]: Component: OprCalEngineBOC32ims.dll; Installed: Absent; Request: Local; Action: Null



But the file versions are same in both old and new applications.
Only the size of the applications are diffent.
Answered 11/10/2009 by: sanhivi
Second Degree Green Belt

Please log in to comment
0
What do you mean by " Size of applications are different " ?
Why not try for a Minor Upgrade ?
Answered 11/10/2009 by: mekaywe
Brown Belt

Please log in to comment
0
Version of the files are same but size is different.
As per our standards we need to do major upgrade only.
Answered 11/10/2009 by: sanhivi
Second Degree Green Belt

Please log in to comment
0
Version of the files are same but size is different

this is kind of weird...
You could always try overriding the file versions in your MSI, make sure they're set to a higher version than the previous package.
Answered 11/10/2009 by: pjgeutjens
Red Belt

Please log in to comment
0
ask VF to go to hell ... lol:)
Answered 11/10/2009 by: mekaywe
Brown Belt

Please log in to comment
0
Did you take an "one shot" snapshot of both the new and older version installations?
This looks absurd... If you had taken a snaphot of only the new version, there should not be a conflict of component GUID with the older version.
Answered 11/10/2009 by: jinxngoblins
Senior Yellow Belt

Please log in to comment
0
I sense that both versions have the same product code. If so, please generate a new product code for "New version : 92.01.27" and see if that helps.
Answered 11/10/2009 by: PackageExpert
Blue Belt

Please log in to comment
0
if you're still looking, could you do a little experiment and change 517 to 516? (exclude MigrateFeatureStates functionality)
See what that gives...
Answered 11/11/2009 by: pjgeutjens
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity