It seems to be Windows checking for existing products (I think reading rather
than writing) and 1402 is just the boring MSI error "Could not open key" beause
of system error 2 ("no file"). It's likely to be "unknown" because at that
point in the logging it doesn't know (or care) whether it's referring to the
per-user's installed products or the system's, one being in HKCU the other
somewhere like HKCR.
Phil Wilson
-----Original Message-----
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Tuesday, March 08, 2011 7:42 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Installer question. What does UNKNOWN and Note mean?
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
*** Confidentiality Notice: This e-mail, including any associated or attached
files, is intended solely for the individual or entity to which it is
addressed. This e-mail is confidential and may well also be legally privileged.
If you have received it in error, you are on notice of its status. Please
notify the sender immediately by reply e-mail and then delete this message from
your system. Please do not copy it or use it for any purposes, or disclose its
contents to any other person. This email comes from a division of the Invensys
Group, owned by Invensys plc, which is a company registered in England and
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X
7AW (Registered number 166023). For a list of European legal entities within
the Invensys Group, please go to
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77.
You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
recept...@invensys.com. This e-mail and any attachments thereto may be subject
to the terms of any agreements between Invensys (and/or its subsidiaries and
affiliates) and the recipient (and/or its subsidiaries and affiliates).
------------------------------------------------------------------------------
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
