[wix-users] Obtaining version for already installed 3rd party program

Bevan Weiss bevan.weiss at gmail.com
Wed Mar 21 04:14:47 PDT 2018

You're right, my first version did erroneously have a space in it.  I had
fixed that earlier in the day to be:
    <Property Id="CLEARSCADA_VER" Secure="yes" Hidden="no"
      <RegistrySearch Id="ClearSCADAVersionSearch"

                      Win64="yes" />

adding the Secure="yes" just in case it needed passing to the server for
something, and giving it a default value just so that I could get someone
doing some testing of the actual installed product for this specific
version anyway.

I'm no longer getting the same result in the log.  Although I'm not sure
that it's improved... now it doesn't seem to provide any error notes.

AppSearch: Property: CLEARSCADA_VER, Signature: ClearSCADAVersionSearch
MSI (c) (34:F0) [21:56:21:123]: Note: 1: 2262 2: Signature 3: -2147287038
Action ended 21:56:21: AppSearch. Return value 1.
MSI (c) (34:F0) [21:56:21:123]: Doing action: LaunchConditions

I'm logging with /L*vx, is there anything else that I could get some more
info from it?
AppSearch. Return value 1 indicates that the RegistrySearch isn't returning
a valid value right? Or it would be doing the PROPERTY CHANGE there I

Even when I hardcode the Key and Name in there it's still returning
'AppSearch. Return value 1'.

Any more ideas?


Bevan Weiss

On 21 March 2018 at 21:32, Nir Bar via wix-users <
wix-users at lists.wixtoolset.org> wrote:

> Your log says:
> AppSearch: Property: CLEARSCADA_VER, Signature: ClearSCADAVersionSearch
> MSI (c) (4C:98) [15:39:19:621]: Note: 1: 2262 2: Signature 3: -2147287038
> MSI (c) (4C:98) [15:39:19:621]: Note: 1: 1402 2:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Current
> Version\Uninstall\{2ACE38B2-F142-4EFE-9AC7-B25514E4930E} 3: 2
> Error 1402 says "Could not open key: [2]. System error [3]." which leads
> us to getting system error 2 (ERROR_FILE_NOT_FOUND).
> Is there a space in "Current Version"? It should be spaceless.
> Maybe ClearSCADA is installed in user context? If so, search in registry
> rook HKCU.
> Regarding the ComponentGroups-
> Maybe you can heat all components in a single go for one level higher and
> use the XSLT to condition each component with the version number taken from
> its folder name?
> --
> Nir Bar, Independent WiX Expert. Creator of-
> JetBA: WiX WPF Bootstrapper User Interface Framework
> JetBA++: WiX Native Bootstrapper User Interface Framework
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/

More information about the wix-users mailing list