[wix-users] Doing action: ADMIN vs. Doing action: INSTALL

Yves Langisch yves at langisch.ch
Tue Apr 12 15:26:40 PDT 2016


Apologies for the confusion. The customer seems to have specified /a instead of /i.

-
Yves

> On 13 Apr 2016, at 00:15 , Yves Langisch <yves at langisch.ch> wrote:
> 
> I have found the following entry in the log file which seems to force an admin installation (ACTION=ADMIN):
> 
> MSI (c) (C4:AC) [17:27:30:875]: Command Line: ACTION=ADMIN CURRENTDIRECTORY=C:\temp CLIENTUILEVEL=0 CLIENTPROCESSID=2500
> 
> My customer though ensures that he did not specify any additional parameter, just the following command to get the debug log from the MSI
> 
> msiexec "installer.msi" /l*vx Log.txt
> 
> Are the any system level configurations (registry entries, admin/non-admin user, …) which could lead to this additional parameter?
> 
> -
> Yves
> 
>> On 13 Apr 2016, at 00:01 , Yves Langisch <yves at langisch.ch> wrote:
>> 
>> Thanks for the clarification. As I’m not a WiX/MSI expert I still do not understand what can lead to an admin installation on some systems and a normal one on most other systems? All customers get the same bootstrap exe containing containing the MSI. They just double click the bootstrap installer.
>> 
>> -
>> Yves
>> 
>>> On 12 Apr 2016, at 23:34 , Phil Wilson <phil.wilson at mvps.org> wrote:
>>> 
>>> An Admin install isn't really an "install".It basically just unpacks all the
>>> files into the target location, and doesn't register the product, install
>>> services, or run custom actions and so on.  When people build patches from
>>> two products with (say) MsiMsp it requires two administrative images. That's
>>> the same "admin" as an admin install produces. It's nothing to do with
>>> administrator privilege either. 
>>> 
>>> Phil W 
>>> 
>>> -----Original Message-----
>>> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of
>>> Yves Langisch
>>> Sent: Tuesday, April 12, 2016 11:36 AM
>>> To: wix-users at lists.wixtoolset.org
>>> Subject: [wix-users] Doing action: ADMIN vs. Doing action: INSTALL
>>> 
>>> Hi all,
>>> 
>>> I've an MSI installer created with the WiX Toolset containing a custom
>>> action to install a device driver. For most customers that all works
>>> perfectly. There are a few  customers which have issues with the installer.
>>> The installer seems to run fine but at the end the custom action did not run
>>> and thus the device driver is missing.
>>> 
>>> Finally I've got a logfile from one customer with verbose logging enabled
>>> (/l*vx). I've compare the logfile to a successful installation. There are
>>> some main differences but I'm unable to explain their reason:
>>> 
>>> A successful installation looks like (filtered to Doing action and UI
>>> Sequence)
>>> 
>>> MSI (c) (E4:84) [19:51:08:064]: Doing action: INSTALL 
>>> MSI (c) (E4:84) [19:51:08:064]: UI Sequence table 'InstallUISequence' is
>>> present and populated.
>>> MSI (c) (E4:84) [19:51:08:064]: Doing action: FindRelatedProducts 
>>> MSI (c) (E4:84) [19:51:08:064]: Doing action: ValidateProductID MSI (c)
>>> (E4:84) [19:51:08:064]: Doing action: CostInitialize 
>>> MSI (c) (E4:84) [19:51:08:064]: Doing action: FileCost 
>>> MSI (c) (E4:84) [19:51:08:080]: Doing action: CostFinalize 
>>> MSI (c) (E4:84) [19:51:08:080]: Doing action: MigrateFeatureStates MSI (c)
>>> (E4:84) [19:51:08:080]: Doing action: ExecuteAction 
>>> MSI (s) (A8:DC) [19:51:14:814]: Doing action: INSTALL 
>>> MSI (s) (A8:DC) [19:51:14:814]: Doing action: FindRelatedProducts 
>>> MSI (s) (A8:DC) [19:51:14:814]: Doing action: ValidateProductID MSI (s)
>>> (A8:DC) [19:51:14:814]: Doing action: CostInitialize 
>>> MSI (s) (A8:DC) [19:51:14:814]: Doing action: FileCost 
>>> MSI (s) (A8:DC) [19:51:14:814]: Doing action: CostFinalize MSI (s) (A8:DC)
>>> [19:51:14:814]: Doing action: MigrateFeatureStates MSI (s) (A8:DC)
>>> [19:51:14:814]: Doing action: InstallValidate MSI (s) (A8:DC)
>>> [19:51:14:861]: Doing action: RemoveExistingProducts MSI (s) (A8:DC)
>>> [19:51:14:861]: Doing action: InstallInitialize MSI (s) (A8:DC)
>>> [19:51:14:877]: Doing action: ProcessComponents MSI (s) (A8:DC)
>>> [19:51:15:908]: Doing action: MsiUnpublishAssemblies MSI (s) (A8:DC)
>>> [19:51:15:908]: Doing action: UnpublishFeatures MSI (s) (A8:DC)
>>> [19:51:15:908]: Doing action: RemoveRegistryValues MSI (s) (A8:DC)
>>> [19:51:15:908]: Doing action: UnregisterClassInfo MSI (s) (A8:DC)
>>> [19:51:15:924]: Doing action: UnregisterExtensionInfo MSI (s) (A8:DC)
>>> [19:51:15:924]: Doing action: UnregisterProgIdInfo MSI (s) (A8:DC)
>>> [19:51:15:924]: Doing action: RemoveShortcuts MSI (s) (A8:DC)
>>> [19:51:15:924]: Doing action: RemoveFiles MSI (s) (A8:DC) [19:51:15:924]:
>>> Doing action: NetFxScheduleNativeImage MSI (s) (A8:DC) [19:51:26:473]: Doing
>>> action: InstallFiles 
>>> MSI (s) (A8:DC) [19:51:26:473]: Doing action: CreateShortcuts 
>>> MSI (s) (A8:DC) [19:51:26:487]: Doing action: RegisterClassInfo 
>>> MSI (s) (A8:DC) [19:51:26:487]: Doing action: RegisterExtensionInfo 
>>> MSI (s) (A8:DC) [19:51:26:487]: Doing action: RegisterProgIdInfo 
>>> MSI (s) (A8:DC) [19:51:26:487]: Doing action: WriteRegistryValues 
>>> MSI (s) (A8:DC) [19:51:26:487]: Doing action: SetCBFS_CA_Values
>>> MSI (s) (A8:DC) [19:51:26:487]: Doing action: InstallCBFS_CA MSI (s)
>>> (A8:DC) [19:51:26:502]: Doing action: InstallServices 
>>> MSI (s) (A8:DC) [19:51:26:502]: Doing action: RegisterUser 
>>> MSI (s) (A8:DC) [19:51:26:502]: Doing action: RegisterProduct 
>>> MSI (s) (A8:DC) [19:51:26:502]: Doing action: MsiPublishAssemblies MSI (s)
>>> (A8:DC) [19:51:26:502]: Doing action: NetFxExecuteNativeImageCommitUninstall
>>> MSI (s) (A8:DC) [19:51:26:502]: Doing action:
>>> NetFxExecuteNativeImageCommitInstall
>>> MSI (s) (A8:DC) [19:51:26:502]: Doing action: PublishFeatures 
>>> MSI (s) (A8:DC) [19:51:26:502]: Doing action: PublishProduct 
>>> MSI (s) (A8:DC) [19:51:26:502]: Doing action: InstallFinalize
>>> 
>>> vs. an unsuccessful
>>> 
>>> MSI (c) (C4:AC) [17:27:30:906]: Doing action: ADMIN 
>>> MSI (c) (C4:AC) [17:27:30:906]: UI Sequence table 'AdminUISequence' is
>>> present and populated.
>>> MSI (c) (C4:AC) [17:27:30:906]: Doing action: CostInitialize 
>>> MSI (c) (C4:AC) [17:27:30:922]: Doing action: FileCost MSI (c) (C4:AC)
>>> [17:27:30:922]: Doing action: CostFinalize MSI (c) (C4:AC) [17:27:31:250]:
>>> Doing action: ExecuteAction MSI (s) (A0:C0) [17:27:31:797]: Doing action:
>>> ADMIN MSI (s) (A0:C0) [17:27:31:797]: Doing action: CostInitialize MSI (s)
>>> (A0:C0) [17:27:31:797]: Doing action: FileCost MSI (s) (A0:C0)
>>> [17:27:31:797]: Doing action: CostFinalize MSI (s) (A0:C0) [17:27:31:812]:
>>> Doing action: InstallValidate MSI (s) (A0:C0) [17:27:31:843]: Doing action:
>>> InstallInitialize MSI (s) (A0:C0) [17:27:31:875]: Doing action:
>>> InstallAdminPackage MSI (s) (A0:C0) [17:27:32:312]: Doing action:
>>> InstallFiles MSI (s) (A0:C0) [17:27:32:328]: Doing action: InstallFinalize
>>> 
>>> Any ideas?
>>> 
>>> Thanks in advance!
>>> -
>>> Yves
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ____________________________________________________________________
>>> WiX Toolset Users Mailing List provided by FireGiant
>>> http://www.firegiant.com/
>>> 
>>> 
>>> 
>>> ____________________________________________________________________
>>> WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
>> 
>> 
>> ____________________________________________________________________
>> WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
> 
> 
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/



More information about the wix-users mailing list