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
- :
- Is there any way to log what happens on a self repair?
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
‎Sep 18, 2008
03:38 AM
Is there any way to log what happens on a self repair?
I've got an application that when I double click on the shortcut to run the application, Installshield jumps in and does something before the application loads.
Is there any way to log what actually happens or finding out what needs correcting?
Thanks
Brian
Is there any way to log what actually happens or finding out what needs correcting?
Thanks
Brian
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 18, 2008
03:57 AM
You can enable Windows Installer Logging on the machine and then fish for the log created on repair. Cheers!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 18, 2008
05:02 AM
Thanks for the help - I've managed to generate the log file and locate it (file attached).
As far as I can tell its indicated that a reinstall was requested, but I can't see any reason for the reinstall request.
Do you know why an reinstall would be automatically requested, or where there is an article about it.
Thanks
Brian
As far as I can tell its indicated that a reinstall was requested, but I can't see any reason for the reinstall request.
Do you know why an reinstall would be automatically requested, or where there is an article about it.
Thanks
Brian
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 18, 2008
05:26 AM
From the log I can see that a component in the feature "Clue2Enterprise" requested the repair. You need to check the event viewer also: you might find that a componet having GUID {} is broken or missing. If that's the case, ideintify that component be looking in the registry or by looking for the GUID in your project file.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 18, 2008
05:56 AM
Superb - I've found my problem, well, two actually.
1. A file that didn't strictly need to be included had some problem with it - so deleted that.
2. One of my components (Clue2.exe) was using Extract COM at Build, and also set values in HKEY_CLASSES_ROOT and HKEY_LOCAL_MACHINE. Some of the keys where almost certinally duplicated.
Thanks for all the help
Brian
1. A file that didn't strictly need to be included had some problem with it - so deleted that.
2. One of my components (Clue2.exe) was using Extract COM at Build, and also set values in HKEY_CLASSES_ROOT and HKEY_LOCAL_MACHINE. Some of the keys where almost certinally duplicated.
Thanks for all the help
Brian
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 18, 2008
05:57 AM
Glad I could help.
Good luck!
Good luck!
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)