This isn't a direct WiX question but there may be something that I am missing
in the WiX code that can avoid this. I notice in the log towards the end if the
installation process it looks like:
MSI (s) (10:E8) [09:03:36:243]: Executing op:
ActionStart(Name=PublishProduct,Description=Publishing product information,)
MSI (s) (10:E8) [09:03:36:243]: Executing op: CleanupConfigData()
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-21-484763869-1993962763-1801674531-3563\Products\B83F86C8F37076D4AB308F355B532FE1\Patches
3: 2
MSI (s) (10:E8) [09:03:36:243]: Executing op:
RegisterPatchOrder(Continue=0,SequenceType=1,Remove=0)
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Products\B83F86C8F37076D4AB308F355B532FE1\Patches 3: 2
MSI (s) (10:E8) [09:03:36:243]: Executing op:
ProductPublish(PackageKey={3339230E-FA27-4A24-B887-EF30441391C7})
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1 3: 2
MSI (s) (10:E8) [09:03:36:243]: Executing op:
UpgradeCodePublish(UpgradeCode={529189FE-FD0E-44FF-8DA6-B4FB5CC7A78B})
MSI (s) (10:E8) [09:03:36:243]: Executing op:
SourceListPublish(,,,,NumberOfDisks=1)
MSI (s) (10:E8) [09:03:36:243]: Note: 1: 1402 2:
UNKNOWN\Installer\Products\B83F86C8F37076D4AB308F355B532FE1\SourceList 3: 2
MSI (s) (10:E8) [09:03:36:243]: Executing op: ProductPublishClient(,,)
MSI (s) (10:E8) [09:03:36:243]: Executing op:
SourceListRegisterLastUsed(SourceProduct={8C68F38B-073F-4D67-BA03-F853B535F21E},LastUsedSource=C:\Temp\)
MSI (s) (10:E8) [09:03:36:243]: Entering
CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (10:E8) [09:03:36:243]: Specifed source is already in a list.
I looks like the installer is trying to write to a registry path started by
UNKNOWN. Is there something in the WiX code that generates this .msi that would
cause this that I can avoid? Also, how can I interpret the 'Note 1: 1402'? I
see this throughout the install log and I am just curious as to what it means.
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
