Re: [WiX-users] MSP install issue
Hello Peter, thanks for the pointer. I gone through the link in your reply and it seems my MSP contains newer version of binary. MSI installs file with version: 4.1.29.0 MSP has the file with version: 4.1.30.0 Also creation date of older file is less then newer file. So something else is creating the mess. Also there is nothing like Won't patch or Won't Overwrite in the log file. Checked with different combinations. Thanks AK. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, February 08, 2011 7:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] MSP install issue I usually see this when someone has not updated the file version in the replacement file. The file versioning rules might help. http://msdn.microsoft.com/en-us/library/aa368599%28VS.85%29.aspx You should also look in the log for Won't patch or Won't Overwrite -Original Message- From: Arun Kumar [mailto:arun_jku...@persistent.co.in] Sent: 08 February 2011 13:23 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] MSP install issue Hi All, I have created an MSP that is supposed to update an binary of older version with newer version. But when I install this MSP it does not update the binary. Instead when I delete binary from INSTALLDIR and run the MSP, newer version binary gets installed. So the issue is why my MSP is not updating older version binary? I had also tried by setting REINSTALLMODE to vaums and voums as follows: msiexec.exe /p patch.msp /l*vx C:\patch.log REINSTALLMODE=vaums Still it doesn't work for me. Any pointers will be really helpful. Thanks, AK DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. - - The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSP install issue
Are there any SELMGR messages in the log? Phil Wilson -Original Message- From: Arun Kumar [mailto:arun_jku...@persistent.co.in] Sent: Wednesday, February 09, 2011 1:47 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] MSP install issue Hello Peter, thanks for the pointer. I gone through the link in your reply and it seems my MSP contains newer version of binary. MSI installs file with version: 4.1.29.0 MSP has the file with version: 4.1.30.0 Also creation date of older file is less then newer file. So something else is creating the mess. Also there is nothing like Won't patch or Won't Overwrite in the log file. Checked with different combinations. Thanks AK. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, February 08, 2011 7:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] MSP install issue I usually see this when someone has not updated the file version in the replacement file. The file versioning rules might help. http://msdn.microsoft.com/en-us/library/aa368599%28VS.85%29.aspx You should also look in the log for Won't patch or Won't Overwrite -Original Message- From: Arun Kumar [mailto:arun_jku...@persistent.co.in] Sent: 08 February 2011 13:23 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] MSP install issue Hi All, I have created an MSP that is supposed to update an binary of older version with newer version. But when I install this MSP it does not update the binary. Instead when I delete binary from INSTALLDIR and run the MSP, newer version binary gets installed. So the issue is why my MSP is not updating older version binary? I had also tried by setting REINSTALLMODE to vaums and voums as follows: msiexec.exe /p patch.msp /l*vx C:\patch.log REINSTALLMODE=vaums Still it doesn't work for me. Any pointers will be really helpful. Thanks, AK DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. - - The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb
Re: [WiX-users] MSP install issue
Ok, I see from an earlier message that you have got SELMGR messages (and why oh why do people delete older text?) You can't delete components - you broke the rules - that's why the patch isn't working. The update will go into (confusingly named) advertised mode and update nothing. Using MSIENFORCEUPGRADECOMPONENTRULES http://msdn.microsoft.com/en-us/library/aa370093(v=VS.85).aspx should give you an error instead. Phil Wilson -Original Message- From: Wilson, Phil Sent: Wednesday, February 09, 2011 12:44 PM To: General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] MSP install issue Are there any SELMGR messages in the log? Phil Wilson -Original Message- From: Arun Kumar [mailto:arun_jku...@persistent.co.in] Sent: Wednesday, February 09, 2011 1:47 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] MSP install issue Hello Peter, thanks for the pointer. I gone through the link in your reply and it seems my MSP contains newer version of binary. MSI installs file with version: 4.1.29.0 MSP has the file with version: 4.1.30.0 Also creation date of older file is less then newer file. So something else is creating the mess. Also there is nothing like Won't patch or Won't Overwrite in the log file. Checked with different combinations. Thanks AK. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, February 08, 2011 7:07 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] MSP install issue I usually see this when someone has not updated the file version in the replacement file. The file versioning rules might help. http://msdn.microsoft.com/en-us/library/aa368599%28VS.85%29.aspx You should also look in the log for Won't patch or Won't Overwrite -Original Message- From: Arun Kumar [mailto:arun_jku...@persistent.co.in] Sent: 08 February 2011 13:23 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] MSP install issue Hi All, I have created an MSP that is supposed to update an binary of older version with newer version. But when I install this MSP it does not update the binary. Instead when I delete binary from INSTALLDIR and run the MSP, newer version binary gets installed. So the issue is why my MSP is not updating older version binary? I had also tried by setting REINSTALLMODE to vaums and voums as follows: msiexec.exe /p patch.msp /l*vx C:\patch.log REINSTALLMODE=vaums Still it doesn't work for me. Any pointers will be really helpful. Thanks, AK DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. - - The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute
[WiX-users] MSP install issue
Hi All, I have created an MSP that is supposed to update an binary of older version with newer version. But when I install this MSP it does not update the binary. Instead when I delete binary from INSTALLDIR and run the MSP, newer version binary gets installed. So the issue is why my MSP is not updating older version binary? I had also tried by setting REINSTALLMODE to vaums and voums as follows: msiexec.exe /p patch.msp /l*vx C:\patch.log REINSTALLMODE=vaums Still it doesn't work for me. Any pointers will be really helpful. Thanks, AK DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSP install issue
I usually see this when someone has not updated the file version in the replacement file. The file versioning rules might help. http://msdn.microsoft.com/en-us/library/aa368599%28VS.85%29.aspx You should also look in the log for Won't patch or Won't Overwrite -Original Message- From: Arun Kumar [mailto:arun_jku...@persistent.co.in] Sent: 08 February 2011 13:23 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] MSP install issue Hi All, I have created an MSP that is supposed to update an binary of older version with newer version. But when I install this MSP it does not update the binary. Instead when I delete binary from INSTALLDIR and run the MSP, newer version binary gets installed. So the issue is why my MSP is not updating older version binary? I had also tried by setting REINSTALLMODE to vaums and voums as follows: msiexec.exe /p patch.msp /l*vx C:\patch.log REINSTALLMODE=vaums Still it doesn't work for me. Any pointers will be really helpful. Thanks, AK DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. - - The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSP install issue
Check A Verbose Log. Palbinder Sandher Software Deployment Engineer 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: Arun Kumar [mailto:arun_jku...@persistent.co.in] Sent: 08 February 2011 13:23 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] MSP install issue Hi All, I have created an MSP that is supposed to update an binary of older version with newer version. But when I install this MSP it does not update the binary. Instead when I delete binary from INSTALLDIR and run the MSP, newer version binary gets installed. So the issue is why my MSP is not updating older version binary? I had also tried by setting REINSTALLMODE to vaums and voums as follows: msiexec.exe /p patch.msp /l*vx C:\patch.log REINSTALLMODE=vaums Still it doesn't work for me. Any pointers will be really helpful. Thanks, AK DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MSP install issue
Hello.
I'm also working with Arun on this issue. Looking at the log file for the
patch I do find the following entries:
MSI (c) (FC:1C) [11:15:22:615]: SELMGR: ComponentId
'{F048496A-AC80-440E-B376-BF490FE5BED0}' is registered to feature 'Complete',
but is not present in the Component table. Removal of components from a
feature is not supported!
MSI (c) (FC:1C) [11:15:22:615]: SELMGR: Removal of a component from a feature
is not supported
...
MSI (s) (74:98) [11:15:23:256]: SELMGR: ComponentId
'{F048496A-AC80-440E-B376-BF490FE5BED0}' is registered to feature 'Complete',
but is not present in the Component table. Removal of components from a
feature is not supported!
MSI (s) (74:98) [11:15:23:256]: SELMGR: Removal of a component from a feature
is not supported
...
MSI (s) (74:98) [11:15:25:365]: Patch Modified Files List:
MSI (s) (74:98) [11:15:25:365]: File = ourfile.dll: Final State = Install
MSI (s) (74:98) [11:15:25:365]: Dumping binary patch manager data...
MSI (s) (74:98) [11:15:25:365]: The file represented by File table key
'ourfile.dll' has no eligible binary patches
MSI (s) (74:98) [11:15:25:365]: Dumping binary patch manager data...
The actual patch file wxs is shown below:
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Patch
AllowRemoval=yes
Manufacturer=Our company
MoreInfoURL=http://www.ourcompany.com/;
DisplayName=AddOn001
Description=AddOn001
Classification=Update
Media Id=5000 Cabinet=patch.cab
PatchBaseline Id=patch/
/Media
PatchFamilyRef Id=SamplePatchFamily/
/Patch
Fragment
PatchFamily Id='SamplePatchFamily' Version='1.0.0.0' Supersede='yes'
ComponentRef Id=AgTBaseMath_1_CDSBase_CDSPool/
ComponentRef Id=IQProductsCompId/
/PatchFamily
/Fragment
/Wix
The component AgTBaseMath_1_CDSBase_CDSPool is the component which contains
our DLL ('ourfile.dll') that needs replacing.
Any ideas on what we should be focusing on? The patch gets installed (shows
up in Add/Remove Programs) but our dll does not get updated. Any help would be
greatly appreciated. I can always email the entire log file in anyone is
interested..
Thanks,
Robert Ortega
==
Hi All,
I have created an MSP that is supposed to update an binary of older version
with newer version.
But when I install this MSP it does not update the binary.
Instead when I delete binary from INSTALLDIR and run the MSP, newer version
binary gets installed.
So the issue is why my MSP is not updating older version binary?
I had also tried by setting REINSTALLMODE to vaums and voums as follows:
msiexec.exe /p patch.msp /l*vx C:\patch.log REINSTALLMODE=vaums
Still it doesn't work for me.
Any pointers will be really helpful.
Thanks,
AK
Re: [WiX-users] MSP install issue
From: Peter Shirtcliffe pshirtcliffe@sd... - 2011-02-08 13:36
I usually see this when someone has not updated the file version in the
replacement file.
The file versioning rules might help.
http://msdn.microsoft.com/en-us/library/aa368599%28VS.85%29.aspx
You should also look in the log for Won't patch or Won't Overwrite
=
-Original Message-
From: Arun Kumar [mailto:arun_jku...@persistent.co.in]
Sent: 08 February 2011 13:23
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] MSP install issue
Hi All,
I have created an MSP that is supposed to update an binary of older version
with newer version.
But when I install this MSP it does not update the binary.
Instead when I delete binary from INSTALLDIR and run the MSP, newer version
binary gets installed.
So the issue is why my MSP is not updating older version binary?
I had also tried by setting REINSTALLMODE to vaums and voums as follows:
msiexec.exe /p patch.msp /l*vx C:\patch.log REINSTALLMODE=vaums
Still it doesn't work for me.
Any pointers will be really helpful.
Thanks,
AK
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
