1605 error on upgrade

[Andrew Stickler]

My latest version of my product performs a major upgrade of the earlier
product. I use the 'RemoveRelatedProducts' action, scheduled after
InstallFinalize to uninstall the older product.

During the install process, after the InstallFiles action, I detect whether
any files were in use (via ReplacedFilesInUse property) and force a reboot.
(I have later CAs that require the newest versions of my files in place).
After the reboot, the install continues and completes successfully, however,
RemoveRelatedProducts fails with error 1605 (This action is only valid for
products that are currently installed.).

From the MSI log file, I can see that after the reboot, the related product
was indeed present.

Is this a known problem? Is there any solution?

Thanks,
Andrew

[Andrew Stickler]

I have just solved this problem.

I had 2 entries in the upgrade table, both for the same upgrade code, one
set to detect only. The MIGRATE property (which I assume is used by
RemoveExistingproducts) contain the same GUID twice and consequently tried
to remove this product twice, failing the second time.

I saw this on Windows 98 and Windows ME, both with MSI 1.1. I have never
experienced this on NT or W2K, but may have been using MSI 2.0 in those
cases.

I suspect this is an MSI bug, but decided the best approach was to work
around it. The 'detect-only' entry was just a generic entry to allow my to
know my product was installed, so I have moved this into a CA that calls
MsiEnumRelatedProducts(), using the UpgradeCode.

Hope this helps,
Andrew

"Andrew Stickler" <and...@kist.getridofthisbit.demon.co.uk> wrote in message
news:O6E6FTmlCHA.2000@tkmsftngp04...