11/27/2009 2479 views
hi all,

i have a conflict between 2 packages that i'm not able to fix with the conflict manager. CM does not find any conflict but there is one.

if i installed both packages separately, they both work. if i installed them together, one of them starts displaying error messages.

since CM can't help me, is there some other tool or way that i can detect the conflict and fix it?

thanks guys!

PS: I'm out until monday so it's possible i don't reply until then. thanks!
0 Comments   [ + ] Show comments


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

All Answers

really don't understand the conflict here
why do you want to run 2 msi's at the same time

install one first then install the oher

you cannot run 2 msi's at the same time

if you don't want to do that then you can try nesting the msi but remember this is a bad practise as you will need to think about upgrades , patching etc

not sure what version of windows installer you have but you can also look at chaining
Answered 11/27/2009 by: cygan
Fifth Degree Brown Belt

i meant that after having installed both msi one after the other, the execution of the app gives errors. of course, i don't run the installation of both at the same time.

i have a package for uPerform that, when installed, runs perfectly.

i have a package for Open Workbench that also works perfectly.

but if i install both on a computer, which has happened today, then Open Workbench, when started, give a runtime error. so there is a conflict somewhere.

i'm trying to make them co-exist on the computer without that glitch.

Answered 11/27/2009 by: kardock
Second Degree Green Belt

What kind of runtime error do you get?
Answered 11/27/2009 by: AngelD
Red Belt

Procmon should help you out.

You may need to look into isolating one of the apps, I'm surprised CM isn't throwing up conflicts... do the packages use the selfreg tables or merge modules at all?
Answered 11/28/2009 by: MSIPackager
3rd Degree Black Belt

the runtime error if from the application. something was broken after installing the second package.

i'll try procmon!

Answered 11/30/2009 by: kardock
Second Degree Green Belt

Check your CM settings, make sure that they are set up correctly. Perhaps change your file and registry conflict settings from "Warnings and errors only" to "Normal conflicts plus informational". Also make sure you don't have any specific directories or files excluded from detection.
Answered 11/30/2009 by: elgwhoppo
Senior Purple Belt