Hi everybody,

I've got a small problem with a vendor msi, but there are some strange things happening. I hope you have a hint for me.

If I open the Msi Package with Orca, the Product Code has the following value: {F74AA8E1-A4CD-4DCD-AF37-600D256B4F8F}.

After the installation, the value under uninstall in the registry has a different value: {D959FF07-D5AD-4C7B-BBE4-1C167A286195}.

The uninstall works, if i use the msi itself, msiexec /x {F74AA8E1-A4CD-4DCD-AF37-600D256B4F8F} doesn't work as i expected.

So I've done some research:

I've extractet the msi and found 2 mst file: 1031 and 1033. I've checked both and the 1031 had the {D959FF07-D5AD-4C7B-BBE4-1C167A286195} Value in the property table. So this is what the new product code is coming from.

So is there a solution, to ignore the embedded mst files? I've already removed them from the package, but the msi fails. Or is there a simple solution for just diasbling those embedded mst files?

I could export those mst's, edit the Product code with the original msi Product Code and reimport them....

Any Ideas?

Thanks very much!
0 Comments   [ + ] Show Comments

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.

Answers

0
Er...why not use the ProductCode for the installed product, i.e. MSIEXEC /X {D959FF07-D5AD-4C7B-BBE4-1C167A286195}?
Answered 02/22/2011 by: VBScab
Red Belt

Please log in to comment
0
Hehe thanks for your reply. Of Course i could use this for uninstall. It would even work. But I'm not sure, if that's the right way to do it. I'm not that msi-pro yet ;)

I've got a little bit confused.. I'm just not sure if that's the right way: install and uninstall with a different product code?

Just found a keyword: MSINEWINSTANCE, maybe this could be something?

I d'like to know if I'm doing a workaround, or if there's a common solution...
Answered 02/22/2011 by: Poochie
Senior Yellow Belt

Please log in to comment
0
To disable mst from being automatically loaded go to "Summary Information" and delete their corresponding language code from there.

If the msi is failing then .mst file contains modifications which are required. An approach would be to export the .mst files, adjust their product code as desired, still, as VBScab mentioned, why not just leave it as is and use the second code for uninstall.
An extra argument would be that being a vendor msi the productcode should be left alone as this could have something to do with previous and future versions of the package.
Answered 02/23/2011 by: package_aligator
Orange Belt

Please log in to comment
0
To disable mst from being automatically loaded go to "Summary Information" and delete their corresponding language code from there. No, no, no, NO!

Leave vendor MSIs alone.
Answered 02/23/2011 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: package_aligator

An approach would be to export the .mst files, adjust their product code as desired


I've done that. Exported the .mst files, modified the Product Code and reimported them. Worked perfectly.

@VBScab: Does this count as modifying the vendor msi? [;)]

Otherwise I'll use the uninstall Product Code as you mentioned.

Thanks
Answered 02/23/2011 by: Poochie
Senior Yellow Belt

Please log in to comment
0
Does this count as modifying the vendor msi?Er...yes!
Answered 02/23/2011 by: VBScab
Red Belt

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