I am little confused about why I am getting this upon self-heal or manual repair attempts. If everything is compressed within the MSI (its a straight forward capture with no external files added...) then why does it need to look back to the source files for repair?? It is critical that i avoid this situation as my client does not want this and is using SMS to deploy and doesnt want any self-healing other then locally on the PC. i have combed the SDK for helpful information regarding resiliency and source directories, but dont really know what i need to check for or modify within my MSI's using either Package Studio or Orca...any timely help would be hugely appreciated. Thanks[:@][:(]
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
My first step would be to identify what is being repaired (self-healed). Look in the event viewer to find out which component is being repaired. Once you've identified which component is being repaired. I usually make that component it's own feature.
Answered 12/21/2005 by: urban_diver
Orange Senior Belt

Please log in to comment
0
I forgot to mention. Does your package contain any HKCU entries? If so, are they needed?
Answered 12/21/2005 by: urban_diver
Orange Senior Belt

Please log in to comment
0
unfortunatly it does contain them (Lotus Approach-crap) and i set-off the self-heal using the repair tab in control panel. i guess what i need to know is how i can make my packages entirely self-sufficient on the PC to which they were deployed. In otherwords i am told that healing to any outside sources is not permissable, and further more they are trying to heal to the packaging machine on which they were built and test-deployed from anyway. Thanks for your response so far...
Answered 12/22/2005 by: broeder52
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity