Self Healing Component.
I have an application that keeps self healing. I know which component is causing to self heal.
I guess if that component does not have a key path then self heal would not take place?
Not sure how to change that in wise?
Thank you.
I guess if that component does not have a key path then self heal would not take place?
Not sure how to change that in wise?
Thank you.
0 Comments
[ + ] Show comments
Answers (17)
Please log in to answer
Posted by:
kiptek
14 years ago
or alternatively, fix the reason it is healing rather than "shooting" the patient to fix the broken leg...
Posted by:
anonymous_9363
14 years ago
Kips, I don't suppose it's beyond the realms of possibility that a keypath may have been set incorrectly, or perhaps it may no longer be required to be a keypath. In either case, removing it is a valid action, I think.
To do so, find the component's entry in the Component table (the Event Viewer entry will have contained the component ID, use that to locate the entry) and clear the cell in the 'KeyPath' column for that row.
To do so, find the component's entry in the Component table (the Event Viewer entry will have contained the component ID, use that to locate the entry) and clear the cell in the 'KeyPath' column for that row.
Posted by:
kiptek
14 years ago
I guess if that component does not have a key path then self heal would not take place?
Ian, it is very possible. When we get into suppositions...
It is this line that leads me to believe that the apropos due diligence has not been done.
Posted by:
anonymous_9363
14 years ago
Kips, I am now into the 3rd year with this client. 1,093 apps and NOT ONE has been QA'd, even on a peer-to-peer basis. Only now, now that the frantic activity is dying down, is there talk of a QA process.
Life on the edge, eh?
Life on the edge, eh?
Posted by:
kiptek
14 years ago
Life on the edge for sure. most places that also claim a QA process do a half a$$ed job anyway, so you are not alone in that predicament... But 3 yrs & 1K apps later... Sheesh!
Posted by:
ogeccut
14 years ago
I know which component is self healing. If i set file key path to none, then file is not coming down.
Maybe dropping a file in the different component? For some reason file was not coming down as well?
Thanks for help
Maybe dropping a file in the different component? For some reason file was not coming down as well?
Thanks for help
Posted by:
ogeccut
14 years ago
OK, i am working with a vendor msi and creating an mst. There is a CA inside a vendor msi that deletes one of the folders after InstallFinalaze. And then self healing takes place on those deleted files/components.
Not sure what is the proper way to fix this?
Thank you.
Not sure what is the proper way to fix this?
Thank you.
Posted by:
turbokitty
14 years ago
Haha.. that's a great CA. I wonder if it runs at the end of the repair too?
Posted by:
ogeccut
14 years ago
I am going in each component and creating a registry key so it wont self heal on the deleted file. Not sure if that is proper or the best approach?
Posted by:
turbokitty
14 years ago
Why is it deleting that file? Is the CA doing anything else?
You can remove the CA with your MST if it's not necessary, but be sure you know what you're changing first.
You can remove the CA with your MST if it's not necessary, but be sure you know what you're changing first.
Posted by:
ogeccut
14 years ago
The CA is running a dll file. Writing some registry keys and deleting a directory. Not sure if its doing anything else.
Thanks for reply.
Thanks for reply.
Posted by:
anonymous_9363
14 years ago
Not sure if its doing anything else.How come? How hard is it to find out?
Find out, condition-out the CA and reproduce the rest of its behaviour in your own CA(s).
Posted by:
jcarri06
14 years ago
Wow...a CA that deletes folders/files to ensure self healing takes place every time the application is launched?? incredible...Well, one thing you could do is create a CA yourself to create/add those files and thus counter it without touching anything else the CA's dll may be doing...gosh this sounds ugly, lol.
- Jay
- Jay
Posted by:
jmcfadyen
14 years ago
best approach is not to delete a keypath but rather remove the component code. This in turn means the component will not be removed on uninstall so its a catch 22 situation.
Posted by:
ashwinchokhani
14 years ago
i guess ur keypath is a empty folder and the entry of tht empty folder is not entered in create folder table.. and we know one thing msi wont create empty folder unless and untill uski entry is not in create folder table..thts why its trigering self repair all the time..
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.