See if the log contains any of this type of thing:
MSI (s) (CC:24) [13:58:42:909]: Disallowing uninstallation of component:
{15239D33-DAE9-46F3-BD59-264A2068B3BC} since another client exists
They'll be before those Action: Null reports (which is why they might be
saying null).
Phil Wilson
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alexei
Sent: Wednesday, August 08, 2007 10:16 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] DLLs and uninstalls
The uninstall log yields the following, which I believe to show the
problem:
MSI (s) (3C:D8) [17:52:54:296]: Doing action: InstallValidate MSI (s)
(3C:D8) [17:52:54:296]: Note: 1: 2205 2: 3: ActionText Action ended
17:52:54: CostFinalize. Return value 1.
MSI (s) (3C:D8) [17:52:54:296]: Feature: InstallFeature; Installed:
Local;
Request: Absent; Action: Absent
MSI (s) (3C:D8) [17:52:54:296]: Component: LanMonExeComp; Installed:
Local;
Request: Absent; Action: Absent
MSI (s) (3C:D8) [17:52:54:296]: Component: LanMonCfgComp; Installed:
Local;
Request: Absent; Action: Absent
MSI (s) (3C:D8) [17:52:54:296]: Component: readerComp; Installed: Local;
Request: Absent; Action: Null
MSI (s) (3C:D8) [17:52:54:296]: Component: writerComp; Installed: Local;
Request: Absent; Action: Null
MSI (s) (3C:D8) [17:52:54:296]: Component: serverComp; Installed: Local;
Request: Absent; Action: Null
MSI (s) (3C:D8) [17:52:54:296]: Component: __LanMonExeComp65; Installed:
Null; Request: Absent; Action: Absent
MSI (s) (3C:D8) [17:52:54:296]: Component: __readerComp65; Installed:
Null;
Request: Absent; Action: Null
MSI (s) (3C:D8) [17:52:54:296]: Component: __serverComp65; Installed:
Null;
Request: Absent; Action: Null
MSI (s) (3C:D8) [17:52:54:296]: Component: __writerComp65; Installed:
Null;
Request: Absent; Action: Null
MSI (s) (3C:D8) [17:52:54:296]: Component: __LanMonExeComp66; Installed:
Null; Request: Absent; Action: Absent
MSI (s) (3C:D8) [17:52:54:296]: Component: __LanMonExeComp67; Installed:
Null; Request: Absent; Action: Absent
So as far as I can tell it knows that serverComp, readerComp and
writerComp are installed but performs no action? I'm pretty lost as to
why this should be.
While I was mucking about I've tried setting SharedDllRefCount="no" for
the components but that didn't help either.
Bob Arnson-6 wrote:
>
> Alexei wrote:
>> 1) So how would I find out is Windows Installer is keeping a
>> reference count somewhere?
>>
>
> Create a verbose log when install and uninstall:
>
> msiexec /l*vx install.log /i mymsi.msi ...
> msiexec /l*vx uninstall.log /x mymsi.msi
>
> Then look for logging around the CostFinalize and InstallValidate
> standard actions; it records when components won't be installed or
> uninstalled.
>
> --
> sig://boB
> http://joyofsetup.com/
>
>
--
View this message in context:
http://www.nabble.com/DLLs-and-uninstalls-tf4229019.html#a12057940
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
