MSI keeps track of these in its own mysterious way, but that's what its APIs
are for. MsiEnumClients will tell you the products that a component guid is
using. For a complete list of every component on the system and its client
products, use this VBScript, save as .vbs
Option Explicit
Public installer, fullmsg, comp, a, prod, fso, pname, ploc, pid, psorce
Set fso = CreateObject("Scripting.FileSystemObject")
Set a = fso.CreateTextFile("comps.txt", True)
' Connect to Windows Installer object
Set installer = CreateObject("WindowsInstaller.Installer")
a.writeline ("MSI Components")
on error resume next
For Each comp In installer.components
a.writeline (comp & " is used by the product:")
for each prod in Installer.ComponentClients (comp)
pid = installer.componentpath (prod, comp)
pname = installer.productinfo (prod, "InstalledProductName")
a.Writeline (" " & pname & " " & prod & "and is installed at " & pid)
Next
Next
Phil Wilson
-----Original Message-----
From: Michael Owings [mailto:[EMAIL PROTECTED]
Sent: Friday, October 17, 2008 2:27 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Seriously borked install
Due to some kind of issue with a major upgrade breaking (To wix from an
existing IS install), my Wix install is broken. I'm getting the dreaded:
MSI (s) (BC:C8) [16:09:18:281]: Disallowing uninstallation of component:
{93426E57-F227-48BA-94D7-BCBC7A2E86D3} since another client exists
MSI (s) (BC:C8) [16:09:18:281]: Disallowing uninstallation of component:
{81862D8F-2FC6-41FE-8331-D2740CF13666} since another client exists
MSI (s) (BC:C8) [16:09:18:281]: Disallowing uninstallation of component:
{67AE89C8-A712-4D36-8145-578714FB1D95} since another client exists
MSI (s) (BC:C8) [16:09:18:281]: Disallowing uninstallation of component:
{598B1EF3-A060-4241-BA24-37107668CEE5} since another client exists
But there seems to be no way of finding the other clients, so I can
diagnose the problem. There used to be a program around called MsiSpy,
but that seems to be unavailable now.
Does anybody have any idea how to fix this kind of thing? The componenet
guids referenced above appear nowhere in the registry once the uninstall
is done.
How does WI keep track of this stuff?
Thanx -- m
--
Teleoperate a roving mobile robot from the web:
http://www.swampgas.com/robotics/rover.html
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
