[wix-users] Property "ClientProcessId" is missing in nested uninstall

Rob Mensching rob at firegiant.com
Tue Feb 20 09:44:53 PST 2018


Yep. This is why we say the things we say about undocumented properties. Don't use them. They may or may not break you in the future.

_____________________________________________________________
 Short replies here. Complete answers over there: http://www.firegiant.com/

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Roland Kieslinger via wix-users
Sent: Tuesday, February 20, 2018 12:07 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Roland Kieslinger <rkieslinger at rzl.at>
Subject: Re: [wix-users] Property "ClientProcessId" is missing in nested uninstall

Ok. Thank you guys.

I need to know, if my msi was getting started by a bootstrapper or standalone. If started from a bootstrapper, I need the process id of the bootstrapper to get the user token of this process so I can impersonate the user later (for accessing network shares and stuff). This is not recommended, I know and I simply can pass an argument from my bootstrapper to my msi rather than using "CLIENTPROCESSID" and "MSICLIENTUSESEXTERNALUI". Since a few months, I've never had a problem using these properties and I thought, it's an good idea to use these ones, rather than creating them again. Also I appreciated, that these properties were getting passed to the nested uninstall. Anyways. I'll stop using them and instead pass my own property to the msi.


-----Ursprüngliche Nachricht-----
Von: Hoover, Jacob [mailto:Jacob.Hoover at greenheck.com] 
Gesendet: Montag, 19. Februar 2018 18:39
An: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Roland Kieslinger <rkieslinger at rzl.at>
Betreff: RE: Property "ClientProcessId" is missing in nested uninstall

If they are not documented, then they are internal to Windows Installer. While they may be available at times, I would not rely upon them... Because they are not documented.

The real question is, why do you care if they exist or not?  What are you trying to accomplish?

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Roland Kieslinger via wix-users
Sent: Monday, February 19, 2018 11:36 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Roland Kieslinger <rkieslinger at rzl.at>
Subject: Re: [wix-users] Property "ClientProcessId" is missing in nested uninstall

So no chance to find the reason why?

I tried it a few times again, and sometimes I get the properties passed, and sometimes not?!

-----Ursprüngliche Nachricht-----
Von: Rob Mensching [mailto:rob at firegiant.com] 
Gesendet: Montag, 19. Februar 2018 18:19
An: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Roland Kieslinger <rkieslinger at rzl.at>
Betreff: RE: Property "ClientProcessId" is missing in nested uninstall

IIRC, those properties are not documented by the Windows Installer.

_____________________________________________________________
 Short replies here. Complete answers over there: http://www.firegiant.com/

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Roland Kieslinger via wix-users
Sent: Monday, February 19, 2018 8:48 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Roland Kieslinger <rkieslinger at rzl.at>
Subject: [wix-users] Property "ClientProcessId" is missing in nested uninstall

Hello!

I chained a msi in my custom burn bootstrapper. If I do a MajorUpgrade (Schedule="afterInstallExecute"), I always got the following arguments via command line in my old uninstalling msi:

...
Aktion gestartet um 16:08:46: RemoveExistingProducts.
...
Command Line: UPGRADINGPRODUCTCODE={A1212C08-B8D4-4486-A5C4-474E5945F403} CLIENTPROCESSID=968 CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 REMOVE=ALL ...

Suddenly, since the last version I built, I don't get the properties "CLIENTPROCESSID" and "MSICLIENTUSESEXTERNALUI" anymore.

What could be the reason? I checked everything, I just added a few files to the msi, nothing else?!

Desperate me.

____________________________________________________________________
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