The components were not removed because another product (or product version
installed side-by-side) installed them. Removing the files does not
unregister the products. You need to identify which other products installed
those components and uninstall those products (or at least uninstall the
features that installs those components).
Programmatically, use MsiEnumClients() (native) or
ComponentInstallation.ClientProducts (managed / DTF).
On Fri, Apr 24, 2009 at 2:37 AM, Mark Sinnathamby <mr...@eurocenter.lk>wrote:
> Hi,
> I checked the log file as to why the database and the windows service were
> not getting uninstalled and found these two lines in the log file:
>
> MSI (s) (2C:B4) [14:39:46:741]: Disallowing uninstallation of component:
> {F8A6AD08-15F7-4BEC-AC9E-A1091F2B0D41} since another client exists
>
> MSI (s) (2C:B4) [14:39:46:741]: Disallowing uninstallation of component:
> {017A23A2-C71D-4442-A93B-C3B5C4F25A11} since another client exists
>
> These component guid's correspond exactly to the database and service
> components in my product.wxs file. What does this message mean? Do I already
> have these components before installation? I delete the database before an
> installation because it is not getting uninstalled, but cannot do anything
> about the service. Even though the service doesn't get uninstalled, the
> installer proceeds smoothly each time, even with the service selected in the
> feature tree. How can I go about solving this problem?
> Thanks,
> Mark.
>
>
> -----Original Message-----
> From: wix-users-requ...@lists.sourceforge.net [mailto:
> wix-users-requ...@lists.sourceforge.net]
> Sent: Friday, April 24, 2009 2:21 PM
> To: wix-users@lists.sourceforge.net
> Subject: [!! SPAM] WiX-users Digest, Vol 35, Issue 107
>
> Send WiX-users mailing list submissions to
> wix-users@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/wix-users
> or, via email, send a message with subject or body 'help' to
> wix-users-requ...@lists.sourceforge.net
>
> You can reach the person managing the list at
> wix-users-ow...@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WiX-users digest..."
>
>
> Today's Topics:
>
> 1. Re: Using DTF to merge a merge module into an msi package
> (Rob Mensching)
> 2. Re: Using DTF to merge a merge module into an msi package
> (Rob Mensching)
> 3. Re: Wix Coder forums (Rob Mensching)
> 4. Re: Reference custom directory (Brian Bakkebo)
> 5. Re: Using DTF to merge a merge module into an msi package
> (Frank Neumann)
> 6. database and windows service not getting uninstalled
> (Mark Sinnathamby)
> 7. Re: database and windows service not getting uninstalled
> (Rob Mensching)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 23 Apr 2009 23:33:12 -0700
> From: Rob Mensching <r...@wixtoolset.org>
> Subject: Re: [WiX-users] Using DTF to merge a merge module into an msi
> package
> To: General discussion for Windows Installer XML toolset.
> <wix-users@lists.sourceforge.net>
> Message-ID: <49f15d28.3020...@wixtoolset.org>
> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
>
> WiX toolset uses COM interop to talk to mergemod.dll.
>
> Richard wrote:
> > In article <
> 139942f2536b7c4fbde6b44132f80c84286210a...@na-exmsg-c111.redmond.corp.microsoft.com
> >,
> > Jason Ginchereau <jason...@microsoft.com> writes:
> >
> >
> >> The real logic for merging merge modules is in mergemod.dll, which DTF
> >> does n ot attempt to use or expose. So I would not recommend using DTF
> for
> >> this purpos e, unless you augment it with the object model of
> mergemod.dll
> >> using COM intero p. I don't have any example code for doing that in C#.
> >>
> >
> > Has anyone tried using COM interop to talk to mergemod.dll?
> >
> > I knwo when I tried to use COM interop to talk to msi.dll's automation
> > interface, it didn't work properly.
> > --
> > "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for
> download
> >
> > <http://www.xmission.com/~legalize/book/download/index.html<http://www.xmission.com/%7Elegalize/book/download/index.html>
> >
> >
> > Legalize Adulthood! <http://blogs.xmission.com/legalize/>
> >
> >
> ------------------------------------------------------------------------------
> > Stay on top of everything new and different, both inside and
> > around Java (TM) technology - register by April 22, and save
> > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> > 300 plus technical and hands-on sessions. Register today.
> > Use priority code J9JMT32. http://p.sf.net/sfu/p
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 23 Apr 2009 23:35:30 -0700
> From: Rob Mensching <r...@wixtoolset.org>
> Subject: Re: [WiX-users] Using DTF to merge a merge module into an msi
> package
> To: General discussion for Windows Installer XML toolset.
> <wix-users@lists.sourceforge.net>
> Message-ID: <49f15db2.7030...@wixtoolset.org>
> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
>
> Database.Merge is to merge two MSI files together not to "do the merge
> process for a Merge Module". There is a collection of other interfaces
> for doing that.... not sure that DTF exposes it but you can see the WiX
> toolset does it.
>
> Frank Neumann wrote:
> > Christopher,
> >
> > you perfectly described the situation: Using WiX is not an option
> > because the MSIs/MSMs I have to deal with, are provided by a third
> > party. In addition the merge action should be automated because it has
> > to be done again when new releases are available. InstallShield would do
> > the job here but I am not an expert in InstallShield automation.
> >
> > The DTF's Database Merge method looks promising: Unfortunately there are
> > no arguments to provide a root directory and primary feature. Orca
> > offers these options when using the "Merge Module" command.
> > Do you know how to circumvent that problem?
> >
> > Thank you for your help,
> >
> > Frank
> >
> >
> > Christopher Painter schrieb:
> >
> >> DTF is meant for creating build automation / installer authoring tools
> also. My guess is he has an MSI that wasn't built using WiX and he'd like
> to use DTF to merge a module (perhaps built using WiX, perhaps not ) into
> the database.
> >>
> >> DTF's Database class has a merge method to handle this. You can also
> look at the MSI Windows Platform SDK example ( WiMerge.vbs ) for a general
> overview of how this is used. The examples are in VBScript using the
> WindowsInstaller.Installer automation interface but it'll port over to
> C#/DTF pretty easy.
> >>
> >>
> >> Christopher Painter, Author of Deployment Engineering Blog
> >> Have a hot tip, know a secret or read a really good thread that deserves
> attention? E-Mail Me
> >>
> >>
> >> --- On Tue, 4/21/09, Frank Neumann <frank.neumann.karlsho...@web.de>
> wrote:
> >>
> >>
> >>
> >>> From: Frank Neumann <frank.neumann.karlsho...@web.de>
> >>> Subject: [WiX-users] Using DTF to merge a merge module into an msi
> package
> >>> To: wix-users@lists.sourceforge.net
> >>> Date: Tuesday, April 21, 2009, 8:29 AM
> >>> I consider using DTF to merge a merge
> >>> module (msm) into an msi package.
> >>> Would you recommend DTF for this purpose? Where can I find
> >>> additional information (tutorial, examples) for it?
> >>>
> >>> Regards,
> >>>
> >>> Frank
> >>>
> >>>
> >>>
> ------------------------------------------------------------------------------
> >>> Stay on top of everything new and different, both inside
> >>> and
> >>> around Java (TM) technology - register by April 22, and
> >>> save
> >>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San
> >>> Francisco.
> >>> 300 plus technical and hands-on sessions. Register today.
> >>> Use priority code J9JMT32. http://p.sf.net/sfu/p
> >>> _______________________________________________
> >>> WiX-users mailing list
> >>> WiX-users@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/wix-users
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
> ------------------------------------------------------------------------------
> > Stay on top of everything new and different, both inside and
> > around Java (TM) technology - register by April 22, and save
> > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> > 300 plus technical and hands-on sessions. Register today.
> > Use priority code J9JMT32. http://p.sf.net/sfu/p
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 23 Apr 2009 23:39:17 -0700
> From: Rob Mensching <r...@wixtoolset.org>
> Subject: Re: [WiX-users] Wix Coder forums
> To: General discussion for Windows Installer XML toolset.
> <wix-users@lists.sourceforge.net>
> Message-ID: <49f15e95.4000...@wixtoolset.org>
> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
>
> How is that really different than this mailing list?
>
> MacDiarmid, James D wrote:
> > Would anyone know of any forums or coding sites kinda like CodeGuru,
> > DevShed, etc that would be dedicated to Install Development using Wix?
> > If not, there might be some benefit to having such a forum or site. I
> > guess the question would be would anyone be interested in such a site?
> >
> >
> >
> > Jim
> >
> ------------------------------------------------------------------------------
> > Stay on top of everything new and different, both inside and
> > around Java (TM) technology - register by April 22, and save
> > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> > 300 plus technical and hands-on sessions. Register today.
> > Use priority code J9JMT32. http://p.sf.net/sfu/p
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 24 Apr 2009 08:59:43 +0200
> From: Brian Bakkebo <bbakk...@gmail.com>
> Subject: Re: [WiX-users] Reference custom directory
> To: "General discussion for Windows Installer XML toolset."
> <wix-users@lists.sourceforge.net>
> Message-ID:
> <e3a05b420904232359k20e9cff1m9ff11e3009a34...@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi dkijc,
> I think you can do this, but a little unclear about the storing of icons
> somewhere else? Are you actually installing a program also or just icons?
>
> For storing the icons part you have a question in the installer I assume
> and
> it asks to download latest icons or choose a directory? If user answers
> yes, then go to web and download icons to a folder. The question is
> wouldnt
> you want to do this after they define the INSTALLDIR in the install? Then
> you can use this dialog set and modify it:(WixUI_InstallDir does not allow
> the user to choose what features to install, but it adds a dialog to let
> the
> user choose a directory where the product will be installed.)
>
> Therefore you can download the icons right to the install directory and
> reference them there. If this all sounds ok, then if you already have the
> INSTALLDIR Variable assuming it is set up as the last node directory and
> will look something like this in your .wxs <Directory Id="INSTALLDIR"
> Name="YourProgramName">. Then you can reference it as a shortcut for
> example as such:
> <Shortcut Id="ApplicationStartMenuShortcut" Name="YourProgramNam"
> Description="YourProgramNam" Target="[INSTALLDIR]YourProgramName.exe"
> WorkingDirectory="INSTALLDIR">. Or using it for other things, etc.
>
> Since I am not quite sure about what you want to accomplish it is hard to
> say, but I think this is sort of what you want.
>
>
>
>
> Med vennlig hilsen /Regards
> Brian
>
>
>
>
> 2009/4/23 dkijc <wwjdat2...@yahoo.com>
>
> >
> > Hi Pally,
> >
> > Thank you so much for your response! That gives me hope haha.
> > I was actually reading the blog by Neil and had a question.
> > I understand I can get the directory to be set but that's an installation
> > directory.
> > Can I create a custom directory OR can I actually use the INSTALLDIR (or
> > whatever it is called)
> > and when the installation is run can I trick the installer so instead of
> > using the directory for installation folder actually snatch that
> directory
> > to be stored in a variable within our code so our application knows where
> > to
> > look for the thumbnails?
> >
> > We can fetched the thumbnails over the web just fine but now our
> > application
> > is deployed in the same machine where we fetch the thumbnails so instead
> of
> > going through a loop with http request we can easily look for thumbnails
> in
> > the local machine. The reason for asking the path for the folder is
> because
> > thumbnails are not always stored in the same folder, as that is a
> > preference
> > that a user can set.
> >
> > The problem I was having was when I created a custom dialog (using
> > orca)that
> > asks whether the use wants our application to fetch the thumbnail over
> the
> > web or just from their local machine. Opening a browse dialog works fine
> > but
> > every time I chose a folder and press 'ok' I'd get '2707' (target not
> > specified). And wasn't sure exactly what was causing the problem. I'm
> > assuming it probably has to do with custom action and was wondering if
> WiX
> > had a better way of going about it.
> >
> > So my question still remains, is it possible to create a custom ID or
> > variable to store the directory (which is not meant for installation but
> > only purpose is to pass down the directory path into our code).
> >
> > I really hope that made sense... haha
> >
> > thanks, again!
> >
> >
> > 1. The web stuff I'm not sure about. It's likely possible using custom
> > actions as with most things. Someone else may have tried something
> > similar but I don't think pulling arbitrary files off a web server is
> > supported by default in the Windows Installer.
> >
> > 2. Very possible using standard Windows Installer UI controls. Have a
> > look at the InstallDirDlg.wxs in the WiX 3.0 sources which does pretty
> > much what you're trying to here except you'd need to hook it into the
> > radio buttons first. You can even use the BrowseDlg in WiXUI without
> > modification for your browse button. Neil Sleightholm's blog on
> > customizing the WiXUI at
> > http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
> > should help point you in the right direction.
> >
> > Personally I'd tackle it as 2 separate issues and get the second part
> > working as you'd like it to first, as the web stuff looks like it could
> > take a lot of time to get working right but that's me and I could be
> > wrong.
> >
> > Good luck
> >
> > Palbinder Sandher
> > Software Deployment & IT Administrator
> > T: +44 (0) 141 945 8500
> > F: +44 (0) 141 945 8501
> >
> > http://www.iesve.com
> > **Design, Simulate + Innovate with the <Virtual Environment>**
> > Integrated Environmental Solutions Limited. Registered in Scotland No.
> > SC151456
> > Registered Office - Helix Building, West Of Scotland Science Park,
> > Glasgow G20 0SP
> > Email Disclaimer
> >
> >
> > --
> > View this message in context:
> > http://n2.nabble.com/Reference-custom-directory-tp2670501p2685638.html
> > Sent from the wix-users mailing list archive at Nabble.com.
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Crystal Reports - New Free Runtime and 30 Day Trial
> > Check out the new simplified licensign option that enables unlimited
> > royalty-free distribution of the report engine for externally facing
> > server and web deployment.
> > http://p.sf.net/sfu/businessobjects
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 24 Apr 2009 09:47:22 +0200
> From: Frank Neumann <frank.neumann.karlsho...@web.de>
> Subject: Re: [WiX-users] Using DTF to merge a merge module into an msi
> package
> To: wix-users@lists.sourceforge.net
> Message-ID: <1665028...@web.de>
> Content-Type: text/plain; charset=iso-8859-15
>
> I followed your suggestions and used "MergeMod.dll" via COM interop in my
> little repackaging tool. This works perfectly.
>
> After the successful merge I still have to do a couple of steps to patch
> the resulting msi:
>
> 1. Extract the merge module's cab file
> 2. Insert the cab file into the "_Streams" table of the msi
> 3. Insert a record into the "Media" table of the msi using the appropriate
> "LastSequence" number
>
> Thanks a lot for your hints!
>
> Frank
>
> Richard schrieb:
> > In article <
> 139942f2536b7c4fbde6b44132f80c84286210a...@na-exmsg-c111.redmond.corp.microsoft.com
> >,
> > Jason Ginchereau <jason...@microsoft.com> writes:
> >
> >> The real logic for merging merge modules is in mergemod.dll, which DTF
> >> does n ot attempt to use or expose. So I would not recommend using DTF
> for
> >> this purpos e, unless you augment it with the object model of
> mergemod.dll
> >> using COM intero p. I don't have any example code for doing that in C#.
> >
> > Has anyone tried using COM interop to talk to mergemod.dll?
> >
> > I knwo when I tried to use COM interop to talk to msi.dll's automation
> > interface, it didn't work properly.
>
> ____________________________________________________________________
> Psssst! Schon vom neuen WEB.DE MultiMessenger geh?rt?
> Der kann`s mit allen: http://www.produkte.web.de/messenger/?did=3123
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 24 Apr 2009 13:31:10 +0530
> From: Mark Sinnathamby <mr...@eurocenter.lk>
> Subject: [WiX-users] database and windows service not getting
> uninstalled
> To: "wix-users@lists.sourceforge.net"
> <wix-users@lists.sourceforge.net>
> Message-ID:
> <223dcf904de0de4a8efd75d982f549158850041...@eccolex01.ec.int>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi,
> I have created an msi installation pack with Wix, using my own custom UI
> library. I have added the maintenance dialogs in this library as well.
> When I install the product, Which consists of a database a windows service
> and some executables, everything gets installed without any problems.
> When I try to uninstall, the uninstallation proceeds without any problem,
> but I find that the windows service and the database are still there after
> uninstalling. (the executables and shortcuts are uninstalled successfully).
> Is this a common problem when you create your own UI library? What is wrong
> here?
> Thanks,
> Mark.
>
>
>
> ------------------------------
>
> Message: 7
> Date: Fri, 24 Apr 2009 01:50:42 -0700
> From: Rob Mensching <r...@wixtoolset.org>
> Subject: Re: [WiX-users] database and windows service not getting
> uninstalled
> To: General discussion for Windows Installer XML toolset.
> <wix-users@lists.sourceforge.net>
> Message-ID: <49f17d62.3030...@wixtoolset.org>
> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
>
> No, something else is probably wrong. A verbose log file will probably
> show a Component not going to Absent (and why).
>
> Mark Sinnathamby wrote:
> > Hi,
> > I have created an msi installation pack with Wix, using my own custom UI
> library. I have added the maintenance dialogs in this library as well.
> > When I install the product, Which consists of a database a windows
> service and some executables, everything gets installed without any
> problems.
> > When I try to uninstall, the uninstallation proceeds without any problem,
> but I find that the windows service and the database are still there after
> uninstalling. (the executables and shortcuts are uninstalled successfully).
> Is this a common problem when you create your own UI library? What is wrong
> here?
> > Thanks,
> > Mark.
> >
> >
> ------------------------------------------------------------------------------
> > Crystal Reports - New Free Runtime and 30 Day Trial
> > Check out the new simplified licensign option that enables unlimited
> > royalty-free distribution of the report engine for externally facing
> > server and web deployment.
> > http://p.sf.net/sfu/businessobjects
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
>
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensign option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
>
> ------------------------------
>
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> End of WiX-users Digest, Vol 35, Issue 107
> ******************************************
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensign option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Heath Stewart
Deployment Technologies Team, Microsoft
http://blogs.msdn.com/heaths
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
