I've repackage EPMClient (Smartlab) however I'm getting some warnings when I launch the application.

1. Detection of product '<component number>' feature 'Complete' failed during request for component '<component number 2>'

2. Detection of product '<component number>' feature 'Complete' component '<component number 2>' failed. The resource 'HKCU_<key>' does not exist.

Now the application partially loads (brings up a splash screen prompting a user name and password), then begins to load for quite some time and dies (closes itself). When I check the event viewer, there are a ton of warnings. Most of the warnings are duplicates, almost like it was getting stuck in a loop bringing up the same warnings.

I was wondering if someone could tell me how to resolve these two warnings (espeically warning 1), as it may help me to get this applications running. Event viewer warning 2 is odd, because the Key it mentions does exist.

I'm on WinXP professional, using Wise package studio professional and I'm somewhat new to the repackaging process.

If more information is requies please let me know.

Many thanks in advance for those who reply.
0 Comments   [ + ] Show 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.


Does anyone know where I should start to resolve this problem?

Answered 11/09/2005 by: number3
Yellow Belt

Please log in to comment
It sounds like your MSI package is in a bit of a mess. Ensure that everything in the MSI package (files and registry keys etc) are meant to be there, and NOT overwritting anything that is already "part of Windows"...

Check the resources in the components listed in Event Viewer.

All and all, just go over your MSI package again. If you're new at this, then I'd suggest using something like "PackageCleaner" that will let you know what files/registry keys should and shouldn't be in a MSI package.


PS: Your issue "2." is normal. Its just saying that this HKCU_<key> (that is set as a keypath for this particular component) doesn't exist, so its going to do a component level repair and write that registry key.
Answered 11/14/2005 by: brenthunter2005
Fifth Degree Brown Belt

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