Ok, I got mine working fine now.
I'm not sure if you are using the same setup, but I'll post my changes (I had the same error)
Version: Professional
I'm using server side validation, if the serial is valid, install proceeds and I store the serial in a registry value called "LicenseID"
When installing over the previous version I wanted to have the serial automatically populated in the serial key box
(you can find the forum threads with my questions on that topic)
I used 2 entries in [Custom Behavior > Search] (named PIDKEY_PROPERTY & PRODUCTID_PROPERTY) and added a "new search" to each, with "add location > registry" for both
Added the info needed to get the "LicenseID" value from the registry
Then under [Custom Behavior > Custom Actions]
InstallUISequence
> FindRelatedProducts
and
InstallExecuteSequence
> FindRelatedProducts
Created 2 new "New Custom Action > Property set with formatted" and named then SET_PIDKEY and SET_PRODUCTID
(so i had a total of 4, 2 under each)
Under SET_PIDKEY
General Properties
-------------------------------------
Property Name: PIDKEY
Formatted Text: [PIDKEY_PROPERTY]
Execute Condition
--------------------------------------
Expression: PIDKEY_PROPERTY <> ""
Under SET_PRODUCTID
General Properties
-------------------------------------
Property Name: ProductID
Formatted Text: [PRODUCTID_PROPERTY]
Execute Condition
--------------------------------------
Expression: PRODUCTID_PROPERTY <> ""
Then ran an initial install (serial number field blank)

Then ran an upgrade install (serial number filled in with value from the registry)
I did set up one more thing under the [Deployment > Resources] tab
I took my Registy_LicenseID > LicenseID and set it to "permanent" so when the installer un-installs the previous version before installing the update, the key persists.
Hope this helps
I'm happy it worked for me and that I'm understanding this program a little better.
FOLLOW US
Get the latest news in Application Packaging