Been trying to package Hyena and have come across something rather odd.
Whenever a non-admin runs it for the 1st time it attempts to go back to the source msi.
I have determined that it is the creation of a folder under appdatafolder that is the cause of it.

Problem is I need that folder to exists in the package so I can use a duplicate file entry to coy a file in there when self healing occurs.

I have stri[pped everything out of the package to the point where it does not go to the source but the instant I add that folder it breaks it.
why on earth does it need the source just to create a single empty folder?!?
And is there any way around this?

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 contend that its not your folder creation that is requiring the source - it must be something else.

You mentionned a duplicate file? Is it being copied to this folder? If so, does this file have an MsiFileHash table entry?

Are you using HKCU keypaths for your "per-user" components?

Is the ResolveSource action being used in your MSI?
Answered 07/28/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
I should look into the event viewer and control which component that has triggered the "profile-fix" repair and then go through the components contens for the missing link that could be a HKCU or profile pointer.
Answered 07/28/2005 by: AngelD
Red Belt

Please log in to comment
Thanks for the reply guys,

At the point where I add the folder and it does not work I have not added the duplicate file entry.

tried a slightly different route.

Started a package from scrath, added the programfiles, a few classes root reg entries and one Current user key path.

And it tries to go back to the source...
I have never had any problems adding hkcu entries in my packages in the past so I am quite perplexed.
event viewer shows this warning:
"The resource 'HKEY_CURRENT_USER\Software\Adkins Resource\Hyena\Win32\' does not exist."
and then this:
"Detection of product '{EE072A75-7AA5-4C51-BD4A-D170AD0EB95A}', feature 'SystemToolsHyena6.3' failed during request for component '{F1696C32-DBEA-4084-A127-88E994F16060}'"

Anyways, this is going on the backburner for now.
Answered 07/28/2005 by: emuringer
Senior Yellow Belt

Please log in to comment
"The resource 'HKEY_CURRENT_USER\Software\Adkins Resource\Hyena\Win32\' does not exist."
and then this:
"Detection of product '{EE072A75-7AA5-4C51-BD4A-D170AD0EB95A}', feature 'SystemToolsHyena6.3' failed during request for component '{F1696C32-DBEA-4084-A127-88E994F16060}'"


My 2 cents on this one is.

Check you do not have the v option set in the Property table under REINSTALLMODE. The REINSTALLMODE is "omus" by default, adding a v would cause the msi to run from the source package and re-cache the local package.

In a self healing situation all registry keys should be installed from the locally cached msi. Was the empty folder in the msi that caused the eventvwr msg you posted above? If so I would remove it and see if just running the HKCU reg keys causes the application to require the source files.

If all else fails to find the problem you could look into Active Setup to sortout your problems...

Good Luck...Nik
Answered 07/28/2005 by: Nikolas
Senior Yellow Belt

Please log in to comment
This will happen by default because you have HKCU keys involved.

Remove them and it won't happen. If the app needs those HKCU keys then a self repair will be prompted every time a new user runs the advertised shortcut.

Make sure your msi is available on a network share or DFS link so that the self repair completes.

the only other thing that MAY be happening is the EXE file actually looking for install information in th registry.....I have seen this happen in a few apps now......where the coder has embedded the installer GUIDS in the app as part of some sort of security measure. Check your tables for the GUID {F1696C32-DBEA-4084-A127-88E994F16060} and also check that your package has the product GUID of {EE072A75-7AA5-4C51-BD4A-D170AD0EB95A}
Answered 07/29/2005 by: MSIMaker
Second Degree Black Belt

Please log in to comment