Re: [WiX-users] Upgrade doesn't install one component

[Rob Mensching]

Somewhere in the log it should explain why the Component was turned off.  Usually, it’s because the Condition is false.  If you don’t’ have a condition, often it is because the KeyPath was not new enough (or it is unversioned and the existing file was modified).   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Lalande Sent: Monday, October 30, 2006 18:51 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Upgrade doesn't install one component   I have successfully convinced my employer to migrate our installers from InstallShield to WiX. However, one of our products, when upgrading from the IS-authored previous version, neglects to install one of the components (the component does get installed on a fresh install).  When the application is launched after the upgrade, it appears to do a Repair and then the application starts.  When I look into installation directory, I can see that the component's KeyPath (which is a file) has now been installed. I have logged the upgrade and did a search for the component name in the log and found the log entry: MSI (s) (0C:CC) [20:24:58:633]: Component: ClientAPIProxy_dll; Installed: Absent;   Request: Local;   Action: Null What I notice unusual is that all the other component log entries have the value "Action:" field set to  "Local". Does this log entry indicate anything that could point me to the problem?

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users