I guess my problem is that i've created an msi for winzip, as an example. It deploys fine, appeared to work fine, but after deployment when you try to open the application it always brings up a dialog looking for the source files...which are on a share...self healing right...

I have some ideas but i'm green...any help is appreciated.
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


i would suggest looking at the Altiris Forums (altiris.com/support/forum)
Even if you're not using Wise the Wise discussion board has some ways to stop unwanted self healing (and to use self healing to avoid errors like you're getting). In a nutshell, it involves putting all Per User registry keys into a top level feature. That way, when a new user launches any advertised entry point into the app, it'll check and see if the per user keys are there. If not, it'll write them.
Answered 02/10/2006 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
i will thank you.

I will say this...i've created about 6 msi packages, and they are all giving me this same sort of problem. If try to start from the icon in start menu it prompts for souce files. If i goto the location on c:\program filies\program dir, and execute the .exe...i have no problems...it is is only when trying to start from start menu, or right clicking a desktop icon...not a pretty package, i know...
Answered 02/10/2006 by: f
Senior Yellow Belt

Please log in to comment
You can find out which component is causing a repair by looking at the application log in event viewer - look for MsiInstaller as the source (with a red cross against it) and open the item, it will report 2 guids (globally unique identifier) - the first will be the product code (identifying the package) and the second the component which is has a broken keypath and therefore causing the repair...

Sounds like you need to validate you packages - you can do this in Wise or in other tools (recommend Orca which is free and part of the windows installer SDK).

Hope this helps,
Answered 02/10/2006 by: MSIPackager
Third Degree Black Belt

Please log in to comment