Self Heal not working
I have this problem from time to time in Wise Studio 5.0.
I isolate my HKCU entries under their own component. Most of the time self heal works just wonderfully upon the user launching the shortcut after the application is installed under an admin account.
But sometimes it just doesn't work. I've checked everything I can think of, but the shortcut just doesn't trigger the repair.
I currently built two packages for two slightly different versions of the same software. Followed the same procedure for each, yet the newer version does not trigger a repair.
Any ideas?
I isolate my HKCU entries under their own component. Most of the time self heal works just wonderfully upon the user launching the shortcut after the application is installed under an admin account.
But sometimes it just doesn't work. I've checked everything I can think of, but the shortcut just doesn't trigger the repair.
I currently built two packages for two slightly different versions of the same software. Followed the same procedure for each, yet the newer version does not trigger a repair.
Any ideas?
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
slocko
19 years ago
How exactly can you tell if the shortcut is advertised? In Wise if I look at the shortcut detail page, the advertised box is greyed out. But it's also greyed out on the shortcut that is working in the older package.
I guess it is possible that there is another entry point via a file extension, but it sure doesn't look that way to me.
I do also remember other times in other packages, where the box is available to check, but checking to make it advertised, doesn't make a difference.
I guess it is possible that there is another entry point via a file extension, but it sure doesn't look that way to me.
I do also remember other times in other packages, where the box is available to check, but checking to make it advertised, doesn't make a difference.
ORIGINAL: Ilikebananas
Hi slocko,
For the intended repair to work you need: an advertised entrypoint (a shortcut isn't always advertised) which needs to be in the same, or in a child feature of the feature where component you want to repair resides. And of course the component to be repaired needs a missing keypath at the time the entrypoint is called.
You can realy overlook the fact that the entrypoint (shortcut) is not always advertised, I surely did a few times... [:'(]
Posted by:
slocko
19 years ago
By the way, my fix is always to copy the physical lnk file to a directory in the package, and then create an advertised shortcut to the physical lnk file. That always works.
Posted by:
sean_c_roberts
19 years ago
Quick-kill solution:
In your MSI... create a NEW shortcut with all the same info as the old shortcut and MAKE SURE the Advertised checkbox IS checked.
Then test self-repair again...
(then delete the old shortcut)
In your MSI... create a NEW shortcut with all the same info as the old shortcut and MAKE SURE the Advertised checkbox IS checked.
Then test self-repair again...
(then delete the old shortcut)
Posted by:
schieb
18 years ago
I recently added a config file component (part of the users ApplicaitonData folder) to the main app's exe feature which now triggers the proper self heal. One odd problem i have is that this file is recongized for the Administrator account i installed with, as well as any new users that log on then self heal to the proper file. However when i log in with a different administrator account it self heals and installs a generic cfg file. Why would this work for users, but not any admins besides the one that installed it?
Thanks,
Brandon
Thanks,
Brandon
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.