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
- :
- Paths and settings gone in Change/Repair Mode
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
‎Jun 24, 2009
10:09 AM
Paths and settings gone in Change/Repair Mode
Hi everyone,
the installation of the features (products) I have in InstallShield works great.
Nevertheless when I go to Add/Remove Programs in Control Panel, click "Modify", choose "Modify" again and try to add/remove/update a feature,
all my selections and settings, which I chose during the installation, are gone! All the features in the Custom Setup dialog appear as unselected, also all path variables are empty. The Installer doesn't know where the source files are and what was (or wasn't) installed...
And of course I can't do anything and get only errors. 😞
Did I miss something to set up or this is standard behaviour?
What can be done in this case?
I am working with IS 2009 Pro and my project is a Basic MSI one.
Thanks in advance,
Vasil
the installation of the features (products) I have in InstallShield works great.
Nevertheless when I go to Add/Remove Programs in Control Panel, click "Modify", choose "Modify" again and try to add/remove/update a feature,
all my selections and settings, which I chose during the installation, are gone! All the features in the Custom Setup dialog appear as unselected, also all path variables are empty. The Installer doesn't know where the source files are and what was (or wasn't) installed...
And of course I can't do anything and get only errors. 😞
Did I miss something to set up or this is standard behaviour?
What can be done in this case?
I am working with IS 2009 Pro and my project is a Basic MSI one.
Thanks in advance,
Vasil
(7) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 25, 2009
02:07 AM
Anyone? :confused:
Please...
Please...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2009
03:07 AM
:confused: :confused:
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 30, 2009
09:23 PM
This behavior typically should not occur unless the product and feature registration actions in the installation were removed or conditioned out (RegisterUser, RegisterProduct, PublishProduct, and PublishFeatures) or if the Windows Installer configuration data was corrupted (possibly through modifying Windows Installer owned registry keys).
You should be able to verify the product and feature registration actions are properly included in the package by running full MSI validation (Build->Validate->Full MSI Validation Suite from InstallShield).
You should be able to verify the product and feature registration actions are properly included in the package by running full MSI validation (Build->Validate->Full MSI Validation Suite from InstallShield).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 01, 2009
03:15 AM
Attached is a screenshot of what I get after running the full validation...
Are these warnings the source of my problem? It doesn't make sense somehow... 😮
My custom action is scheduled before the registration actions. I think that's hoe it should be or I'm wrong? (second screenshot).
Thanks in advance
Are these warnings the source of my problem? It doesn't make sense somehow... 😮
My custom action is scheduled before the registration actions. I think that's hoe it should be or I'm wrong? (second screenshot).
Thanks in advance
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 01, 2009
04:33 PM
The validation output (assuming that is the complete output in the screenshot) does not contain any likely indications of what is causing this behavior.
The sequencing of your custom action should only matter if it depends on something being installed with the currently installing product.
Is this behavior occurring on multiple machines or only some? Also, can you attach verbose logs of the install and maintenance modes?
The sequencing of your custom action should only matter if it depends on something being installed with the currently installing product.
Is this behavior occurring on multiple machines or only some? Also, can you attach verbose logs of the install and maintenance modes?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 02, 2009
10:41 AM
This is occurring on every machine, on which I've already tested.
What exactly do you mean with "install and maintenance mode" and how to create such logs?
What exactly do you mean with "install and maintenance mode" and how to create such logs?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 06, 2009
10:50 AM
A log of a first time install can be created with the following command line:
setup.exe /v"/l*v C:\PathToLog\LogFile.log"
After the product is installed, a maintenance operation can be logged with the following command line:
msiexec.exe /I {ProductCode} /l*v C:\PathToLog\MaintenanceLog.log
setup.exe /v"/l*v C:\PathToLog\LogFile.log"
After the product is installed, a maintenance operation can be logged with the following command line:
msiexec.exe /I {ProductCode} /l*v C:\PathToLog\MaintenanceLog.log
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)