Problem:Self Healing everytime the system reboots
Hello..
I have a package which installs fine and also works fine...but everytime the system is rebooted...the package starts to self heal itself...
I don't understand this because after the initial install...the package works fine...so..definitely its not missing any important dlls or reg...this happens only after reboot of the machine...
Looks like some kind of log file...or something...
Could anyone please let me know how could I find out what the problem is....did anyone encounter anything like this before..?
Any suggestions would be highly appreciated.
Regards.
Prash
I have a package which installs fine and also works fine...but everytime the system is rebooted...the package starts to self heal itself...
I don't understand this because after the initial install...the package works fine...so..definitely its not missing any important dlls or reg...this happens only after reboot of the machine...
Looks like some kind of log file...or something...
Could anyone please let me know how could I find out what the problem is....did anyone encounter anything like this before..?
Any suggestions would be highly appreciated.
Regards.
Prash
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
AngelD
18 years ago
Is this a vendor msi or did you create it?
Look in the eventviewer, this will state which product, feature and component thats triggering the self-healing.
There seems to be some rubbish in the package, maybe some temp file/registry triggering this.
Or this package may remove resources used by another package and that package is trying to self-heal.
You can also log the repair and see whats happning in the whole chain.
Post what you get from the log(s) if you need some more help.
Look in the eventviewer, this will state which product, feature and component thats triggering the self-healing.
There seems to be some rubbish in the package, maybe some temp file/registry triggering this.
Or this package may remove resources used by another package and that package is trying to self-heal.
You can also log the repair and see whats happning in the whole chain.
Post what you get from the log(s) if you need some more help.
Posted by:
praschat12
18 years ago
Hello..
Thank you for the suggestion. There is a log file in the Windows folder where it writes something while the installation of the package...also after the installation is complete..it deletes that file...
Now...when I see in the package....it is a set as a key file...is it because it is a key file...everytime the machine reboots..that file is not present...so...it tries to self heal...???
Rather clearing the key file...keeping as a regular file...hopefully it works..? any suggestions..???
Regards.
Prash
Thank you for the suggestion. There is a log file in the Windows folder where it writes something while the installation of the package...also after the installation is complete..it deletes that file...
Now...when I see in the package....it is a set as a key file...is it because it is a key file...everytime the machine reboots..that file is not present...so...it tries to self heal...???
Rather clearing the key file...keeping as a regular file...hopefully it works..? any suggestions..???
Regards.
Prash
Posted by:
AngelD
18 years ago
Hi praschat12,
if it's this log file thats triggering the repair you could:
1. Remove the keypath for the component, if the component holds other resources you could use one of these instead as the keypath.
2. If the log file isn't required to exist then remove the file.
if it's this log file thats triggering the repair you could:
1. Remove the keypath for the component, if the component holds other resources you could use one of these instead as the keypath.
2. If the log file isn't required to exist then remove the file.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.