Self Healing...
Could there me any other cause for a package to self heal apart from a corrupt package?
maybe something to do with user specific settings?
it could work fine for every user except one? and self heals everytime the app is launched...
Any reasons why?
checked event viewer, file mon, regmon... kinda dumbfounded [&:]
Thanks
Ty.
maybe something to do with user specific settings?
it could work fine for every user except one? and self heals everytime the app is launched...
Any reasons why?
checked event viewer, file mon, regmon... kinda dumbfounded [&:]
Thanks
Ty.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
Secondlaw
17 years ago
Could be that one of your components keypaths are being modified by something. For an example... If you have a file set to a keypath and the application removes that file every time it's launched, it will force a self repair. I would check your keypaths.
Posted by:
turbokitty
17 years ago
Agreed, it should say in the Event Viewer which component is being repaired. Then open your MSI and search for that component GUID.
Posted by:
kj_95376
17 years ago
There are mainly 2 reasons why a package self heals after launching it everytime or after you restart the Computer and launch the application.
The main reason is usually Rights issues if you are in a locked down environment.
The second issue is an empty or broken Component.
The first thing I would do after installing this package and before running the application is clear all events from the Event Viewer under Application portion.
Then open the application and check your event viewer for the error.
To check if it is a rights issue, install the application from the command line as a local Administrator then run it, if you do not get the Windows Installer Window or it only runce once even after you restart the Computer then you have a rights issue.
Use RegMon and FileMon to find Access Denied issues in this case and then you can add the proper rights into your package.
KJ
Wise Packager
The main reason is usually Rights issues if you are in a locked down environment.
The second issue is an empty or broken Component.
The first thing I would do after installing this package and before running the application is clear all events from the Event Viewer under Application portion.
Then open the application and check your event viewer for the error.
To check if it is a rights issue, install the application from the command line as a local Administrator then run it, if you do not get the Windows Installer Window or it only runce once even after you restart the Computer then you have a rights issue.
Use RegMon and FileMon to find Access Denied issues in this case and then you can add the proper rights into your package.
KJ
Wise Packager
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.