always self repair or finishing install when user launch app
Hi,
I build an MSI from an installshield using Wise for a custom application. It installs fine but when a user launch it, there is always that progress bar like if the application was self repairing of finishing the installation (like some offices apps do on first lunch, gatering information..etc.. )
I always get this progress bar and the application starts just fine.
Do you have an idea where i should look to fix this kind of issue?
Thanks,
Bob
I build an MSI from an installshield using Wise for a custom application. It installs fine but when a user launch it, there is always that progress bar like if the application was self repairing of finishing the installation (like some offices apps do on first lunch, gatering information..etc.. )
I always get this progress bar and the application starts just fine.
Do you have an idea where i should look to fix this kind of issue?
Thanks,
Bob
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
This sounds like expected behaviour.
- Does the MSI have any HKEY_CURRENT_USER registry entries?
- When you say you 'always get this progress bar', do you mean you get it every time the same user launches the app or only once when each new user launches it?
- Does the MSI have any HKEY_CURRENT_USER registry entries?
- When you say you 'always get this progress bar', do you mean you get it every time the same user launches the app or only once when each new user launches it?
Posted by:
unreal2me
15 years ago
Hi,
Thanks for the reply.
Yes, i get this every time the application is start by the same user and any user.
Thanks,
Bob
Thanks for the reply.
Yes, i get this every time the application is start by the same user and any user.
Thanks,
Bob
Posted by:
AngelD
15 years ago
Find out which resources that gets installed during a repair of the broken component(s) and verify that the application doesn't remove them in some how during launch. If this happens change the keypath of the affected component(s). Could also be a permission problem where you could use the tool included in Ian's signature ;)
Posted by:
jmcfadyen
15 years ago
also check the application event log to determine which component is triggering the repair function.
it will list a component GUID of the offending component. From there you can track the keypath back to the target file / reg key that is instantiating the repair function.
posibbly a corrupt component ID as well.
it will list a component GUID of the offending component. From there you can track the keypath back to the target file / reg key that is instantiating the repair function.
posibbly a corrupt component ID as well.
Posted by:
Inabus
15 years ago
Sounds to me like you have a badly authored MSI which has something in it that shouldnt be, like DHCP or Time information. Therefore it changes, app runs, installs again to put it back to how it was, as stated, check eventlog as it will show that a self repair was instigated and why.
Also kick off a manual repair using logging.
P
Also kick off a manual repair using logging.
P
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.