6 replies to this topic

[ClarkMichael]

I have a simple install
Run setup program installs
run setup again select remove and near the compleation of the project I get the error 2720 2.

if I run setup using the following flags the uninstall complete as expected
setup /V"/L*v removelog.log REMOVE=ALL REINSTALLMODE=omvus"

It seems that if I add the "v" Don't use the cahced copy of the installation the uninstallation works fine.

Anyone have any ideas, I can provide more information if needed.

[luke_s]

Error 2720 is - Error opening sourcelist key. Error: '[2]'

So im tipping thats why the uninstall works if you dont use the cached source.

This is probably just a "red herring", but if it starts to appear on multiple machines then i would look into the issue further.

You could also either look in the event viewer or verbose log for extra information.

[Stefan Krueger]

Error code 2 means file not found.
If you generate a log without setting REINSTALLMODE, you should see in the log where it is actually looking for the msi file. This could also be a permission issue.

[ClarkMichael]

Here is what I got from the Log

MSI (s) (70:0C) [10:59:54:990]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\98E77D4A2996F004694D2E9A9C621F77\Patches 3: 2
MSI (s) (70:0C) [10:59:54:990]: Executing op: SourceListRegisterLastUsed(SourceProduct={A4D77E89-6992-400F-96D4-E2A9C926F177},LastUsedSource=F:\DOCUME~1\mclark\LOCALS~1\Temp\_is22AB\)
MSI (s) (70:0C) [10:59:54:990]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (70:0C) [10:59:54:990]: OpenWritableAdvertisedProductKey failed with 2
MSI (s) (70:0C) [10:59:54:990]: Note: 1: 2720 2: 2
DEBUG: Error 2720: Error opening sourcelist key. Error: '2'

Doesn't tell me much

[Stefan Krueger]

Hmm, it seems to look for patches of this product in the registry but cannot open the key in question. Does that key exist? Could it be a permission problem?

[ClarkMichael]

The product has no patches installed, as a matter of the process is simple.

run setup
runsetup again and select remove and the error occurs,

and the keys do exist in the registry.

Look Like I'm going to start a binary chop of things and see what's happening. Just sure would be nice if msi provided better error reporting. I can never make heads or tails out of the lof files.

Thanks
Michael

[ClarkMichael]

I resolved the issue..... Seems I was calling a custom action that set features unconditionally, and I shhould have the condition to Not Installed.

Thanks all for your help


-Michael Clark
RSA Security