This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Components aren't installed when installing a new version over an existing product
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 31, 2011
07:57 PM
Components aren't installed when installing a new version over an existing product
Hello,
when I am installing a newly build installer(new files/binaries) over an existing product (same GUID) - none of my Components gets installed.
Here is a MSI log around "InstallValidate" action...
*************************************************************
MSI (s) (F4:98) [17:17:24:953]: Doing action: InstallValidate
Action 17:17:24: InstallValidate. Validating install
Action start 17:17:24: InstallValidate.
MSI (s) (F4:98) [17:17:24:953]: Feature: My_Feature_Files; Installed: Advertise; Request: Reinstall; Action: Reinstall
MSI (s) (F4:98) [17:17:24:953]: Component: Help; Installed: Local; Request: Null; Action: Null
MSI (s) (F4:98) [17:17:24:953]: Component: PixelSystemReg1; Installed: Local; Request: Null; Action: Null
MSI (s) (F4:98) [17:17:24:953]: Component: SystemReg1; Installed: Local; Request: Null; Action: Null
MSI (s) (F4:98) [17:17:24:953]: Component: SystemReg2; Installed: Local; Request: Null; Action: Null
...
*************************************************************
Result was the same when I tried install over:
1) interactively
2) command-line and specifying "REINSTALL=ALL REINSTALLMODE=voums" swtiches.
e.g. setup.exe /s /v"REINSTALL=ALL REINSTALLMODE=voums /l*v c:\Msilog.log"
Any clues or assistances to resolve this would be appreciated.
Thanks,
Vinay
when I am installing a newly build installer(new files/binaries) over an existing product (same GUID) - none of my Components gets installed.
Here is a MSI log around "InstallValidate" action...
*************************************************************
MSI (s) (F4:98) [17:17:24:953]: Doing action: InstallValidate
Action 17:17:24: InstallValidate. Validating install
Action start 17:17:24: InstallValidate.
MSI (s) (F4:98) [17:17:24:953]: Feature: My_Feature_Files; Installed: Advertise; Request: Reinstall; Action: Reinstall
MSI (s) (F4:98) [17:17:24:953]: Component: Help; Installed: Local; Request: Null; Action: Null
MSI (s) (F4:98) [17:17:24:953]: Component: PixelSystemReg1; Installed: Local; Request: Null; Action: Null
MSI (s) (F4:98) [17:17:24:953]: Component: SystemReg1; Installed: Local; Request: Null; Action: Null
MSI (s) (F4:98) [17:17:24:953]: Component: SystemReg2; Installed: Local; Request: Null; Action: Null
...
*************************************************************
Result was the same when I tried install over:
1) interactively
2) command-line and specifying "REINSTALL=ALL REINSTALLMODE=voums" swtiches.
e.g. setup.exe /s /v"REINSTALL=ALL REINSTALLMODE=voums /l*v c:\Msilog.log"
Any clues or assistances to resolve this would be appreciated.
Thanks,
Vinay
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 31, 2011
10:43 PM
Hi Vinay,
Some component rules are being violated in the new build. Hence the behavior you are seeing. Refer to this article for more information --> http://blogs.msdn.com/b/heaths/archive/2006/01/23/516457.aspx.
I hope this helps.
Thanks!
Some component rules are being violated in the new build. Hence the behavior you are seeing. Refer to this article for more information --> http://blogs.msdn.com/b/heaths/archive/2006/01/23/516457.aspx.
I hope this helps.
Thanks!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 01, 2011
12:52 PM
Hi Alpesh,
you are correct. Our new build violated some components rules -- we removed some files/modules no longer needed in new build. Unfortunately, they were installed previously.
The reference article was helpful.
Thanks,
Vinay
you are correct. Our new build violated some components rules -- we removed some files/modules no longer needed in new build. Unfortunately, they were installed previously.
The reference article was helpful.
Thanks,
Vinay