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: Auto Repair mode triggered???
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 02, 2008
10:07 AM
Auto Repair mode triggered???
Is there any way to find out what is triggering the msi auto repair mode of our product?
We have been having various administrators calling support stating that after they push out our product install and then the user logs in an starts up various apps, some not having anything to do with our app, it will trigger the msi auto repair and perform a repair of our app. If they do not hit Cancel on the repair then then the app starts up and it is fine, where as if they Cancel the the auto repair will contine to happen when launching these apps until it have been completed.
Is there any way to log or detect what could be causing the auto repair to ocurr so that we may be able to look into having it fixed?
Any help would be appreciated.
We have been having various administrators calling support stating that after they push out our product install and then the user logs in an starts up various apps, some not having anything to do with our app, it will trigger the msi auto repair and perform a repair of our app. If they do not hit Cancel on the repair then then the app starts up and it is fine, where as if they Cancel the the auto repair will contine to happen when launching these apps until it have been completed.
Is there any way to log or detect what could be causing the auto repair to ocurr so that we may be able to look into having it fixed?
Any help would be appreciated.
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 02, 2008
11:21 AM
Yes, the Event Viewer. It will list the product name and the component GUID which is causing the application to go for auto-repair.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 02, 2008
12:01 PM
Okay thanks,
I have one question.
I had one of the testing people use the even viewer and it basically stated that a registry key did not exist under our key in the HKEY_CURRENT_USER section of the registry.
So if the install is pushed out in all user mode, meaning for anyone that logs onto the machine, then for each new user that logs onto the machine the auto-repair mode will be triggered so that this key could be created under their user key. Would that be the case here?
If so then I should not have this key created under the HKEY_CURRENT_USER sections, even though the validation stated that I should create the key there....
thanks for your help.
I have one question.
I had one of the testing people use the even viewer and it basically stated that a registry key did not exist under our key in the HKEY_CURRENT_USER section of the registry.
So if the install is pushed out in all user mode, meaning for anyone that logs onto the machine, then for each new user that logs onto the machine the auto-repair mode will be triggered so that this key could be created under their user key. Would that be the case here?
If so then I should not have this key created under the HKEY_CURRENT_USER sections, even though the validation stated that I should create the key there....
thanks for your help.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 02, 2008
12:44 PM
Not sure if I understood the question correctly, but for all-users type installation, the application has to self-repair if there are per-user keys. If this key is not required and you want to avoid self-healing then its best to remove it.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 02, 2008
01:00 PM
Okay thanks,
So as long as I have any keys that go into the per-user keys then it will cause the auto-repair mode. I'll have to double check the keys that I have there and if they are not needed or can be move to our HKEY_LOCAL_MACHINE registry keys then I'll have to do that.
Thanks again.
So as long as I have any keys that go into the per-user keys then it will cause the auto-repair mode. I'll have to double check the keys that I have there and if they are not needed or can be move to our HKEY_LOCAL_MACHINE registry keys then I'll have to do that.
Thanks again.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 03, 2008
09:47 AM
Right. Or perhaps if it's reasonable, take it out of the install and have the application create the HKCU key when the user first runs it, or first sets the option away from the default, or similar.