On 08/04/2010 05:02 PM, Pally Sandher wrote: > Apologies, I read "patching system"& assumed it was MSPs not Major > Upgrade MSIs. > > Point still stands though. If it works fine without using wpkg but > breaks when using wpkg, the problem isn't WiX or Windows Installer& > it's unlikely to be your package. > > From your log: > > MSI (s) (78:4C) [20:14:06:466]: Product not registered: beginning > first-time install > MSI (s) (78:4C) [20:14:06:466]: Determined that existing product (either > this product or the product being upgraded with a patch) is installed > per-user. > MSI (s) (78:4C) [20:14:06:467]: PROPERTY CHANGE: Deleting ALLUSERS > property. Its current value is '1'. > > That means the package being upgraded (your version 0.3.0) has been > installed as per-user not per-machine& you're now trying to upgrade it > using a per-machine package. I don't know if that's possible as I've > never had to work with per-user packages but it doesn't seem likely to > me. I was/am confused about the message: Determined that existing product ... the message is somehow ambiguous to me. I interpreted that as the 0.3.0 was installed per-machine, and the upgrade 0.5.0 is applied per-user
What is also odd when i have installed 0.3.0 using msiexec /i package.msi using administrator account the log indicated: MSI (s) (DC:88) [20:08:33:878]: Product installation will be elevated because user is admin and product is being installed per-machine. Which would suggest to me that it was done per-machine. Why the 0.5.0 upgrade thinks the 0.3.0 was installed per-user? > > If you install the 0.3.0 package on a machine by using msiexec /i > <package.msi> & then use the new one to upgrade launching it in the same > manner does it work or is it the same problem as above? No problems there. Regards Luk > > 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 > > -----Original Message----- > From: Lukasz Zalewski [mailto:lu...@eecs.qmul.ac.uk] > Sent: 04 August 2010 15:52 > To: General discussion for Windows Installer XML toolset. > Cc: Pally Sandher > Subject: Re: [WiX-users] msi upgrade problems per-user vs per-machine > contextfailure > > Hi Palbinder > On 08/04/2010 11:50 AM, Pally Sandher wrote: >> Sounds to me like your original package is installed in a per-user >> context but your patching system is forcing everything to run as >> per-machine. If you want to force a package to always be per-machine, >> set InstallScope="perMachine" in your Package Element (see >> http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm) but that >> obviously only applies to the original MSI, not the update MSP. > Its not the MSP update but full msi installation (with version number > increased (from 0.3.0 to 0.5.0). I have tried adding > InstallScope="perMachine" but that does not make any difference > > The original is installed per-machine, i.e. this is from its log: > MSI (s) (DC:88) [20:08:33:878]: Product installation will be elevated > because user is admin and product is being installed per-machine. > > There is the link to the wix file used: > http://code.google.com/p/wpkg-gp/source/browse/trunk/Installer/wpkg-gp.w > xs > >> >> However it doesn't sound like WiX or Windows Installer are the cause >> of your problem if you can manually apply your patch using msiexec > /update. >> Try asking wpkg.org for help with their patch management software. > I don't think its the problem with wpkg, as for example tortoiseSVN > update goes according to plan (i know one can't compare like for like) > > Thx > > Luk >> >> 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 >> >> -----Original Message----- >> From: Lukasz Zalewski [mailto:lu...@eecs.qmul.ac.uk] >> Sent: 03 August 2010 20:57 >> To: wix-users@lists.sourceforge.net >> Subject: [WiX-users] msi upgrade problems per-user vs per-machine >> contextfailure >> >> Hi all, >> I'am trying to upgrade existing package through major upgrade. >> The upgrade is done through wpkg (wpkg.org) patching system and it >> runs using machine account. >> When i run the upgrade using Administrator account (interactively) all > >> goes smoothly. However when the upgrade is applied through the >> patching system it goes wrong i.e. the following appears in the logs >> (which i believe is the cause of my problems): >> MSI (s) (78:4C) [20:14:06:466]: Determined that existing product >> (either this product or the product being upgraded with a patch) is >> installed per-user. >> >> and then >> MSI (s) (78:4C) [20:14:06:555]: FindRelatedProducts: current install >> is per-user. Related install for product >> '{A70E99ED-87C6-4142-88A7-8491459494A2}' is per-machine. Skipping... >> >> I have found various post regarding similar errors which conclude that > >> cross-context installation is not possible. What i want to do is to >> force the install to be in per-machine context. I have added >> ALLUSERS=1 property to the wix file, tried running msiexec with /jm >> flag and event passed ALLUSERS=1 as a parameter to the installer. >> Still the installation is per-user and the ALLUSERS initially set to 1 > is unset: >> MSI (s) (78:4C) [20:14:06:467]: PROPERTY CHANGE: Deleting ALLUSERS >> property. Its current value is '1'. >> >> I'm 100% sure that the previous version >> ({A70E99ED-87C6-4142-88A7-8491459494A2}) is installed per-machine. >> Initially i thought it was a problem with patching system, but i have >> tested upgrade process of other application and the update is >> correctly installed using per-machine mode. >> >> I have used orca to look at the various properties (of my two packages > >> and the other application packages), and do not see anything massively > >> out of ordinary. The installer script is also quite basic. I'm quite >> new to wix so any help would be much appreciated >> >> The wix version is 3.0 and machine that the package is being updated >> on is Windows7 x64. I have attached zipped log file from the failed >> upgrade. >> >> Many thanks >> >> Lukasz >> >> >> >> ---------------------------------------------------------------------- >> -------- The Palm PDK Hot Apps Program offers developers who use the >> Plug-In Development Kit to bring their C/C++ apps to Palm for a share >> of $1 Million in cash or HP Products. Visit us here for more details: >> http://p.sf.net/sfu/dev2dev-palm >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
