Major Upgrade
[hr] We have a package to upgrade which just installs a PSLicence.xml (not versioned) file to a sub-folder of allusers applicationdata. The exisiting package was done in-house by a predecessor. I've created a new MSI in WISE with a new Package and Product Code and incremented the product version. The new MSI has a different name to keep with our naming standards. I've used the previous package's upgrade code in the new upgrade table as below:
{304A5217-AF36-4A50-98F9-B127051E8CC2} 2.0.0 3.0.0 1033 261 UPGRADE_1
The upgrade appears to work at first but on checking the xml file and sub folders are not there. The log seems to suggest that the file is copied as required but then removed afterwards. Repairing the install puts the file back as expected.
MSI (s) (54:B0) [13:39:52:869]: Executing op: ChangeMedia(,MediaPrompt=Please insert the disk: [ProductName] LABEL,MediaCabinet=Cabs.w1.cab,BytesPerTick=32768,CopierType=2,ModuleFileName=C:\WINDOWS\Installer\1fe4a.msi,,,,,IsFirstPhysicalMedia=1)
MSI (s) (54:B0) [13:39:52:869]: Executing op: FileCopy(SourceName=PSLICE~1.XML|PSLicence.xml,SourceCabKey=PSLicence.xml,DestName=PSLicence.xml,
Attributes=0,FileSize=146090,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,
HashPart1=1124213334,HashPart2=-439749084,HashPart3=-973851377,HashPart4=467277008,,)
MSI (s) (54:B0) [13:39:52:869]: File: C:\Documents and Settings\All Users\Application Data\ESRIUK\LicenceStore\PSLicence.xml; Overwrite; Won't patch; Existing file is unversioned and unmodified - hash doesn't match source file
MSI (s) (54:B0) [13:39:52:869]: Source for file 'PSLicence.xml' is compressed
MSI (s) (54:B0) [13:39:52:869]: Re-applying security from existing file.
MSI (s) (54:B0) [13:39:52:869]: Verifying accessibility of file: PSLicence.xml
Further down the log is the old MSI component being removed:
MSI (s) (54:98) [13:39:54:275]: Executing op: FileRemove(,FileName=PSLicence.xml,,ComponentId={05B86293-D430-4410-ACB2-1159677A2D78})
What am I doing wrong here?
{304A5217-AF36-4A50-98F9-B127051E8CC2} 2.0.0 3.0.0 1033 261 UPGRADE_1
The upgrade appears to work at first but on checking the xml file and sub folders are not there. The log seems to suggest that the file is copied as required but then removed afterwards. Repairing the install puts the file back as expected.
MSI (s) (54:B0) [13:39:52:869]: Executing op: ChangeMedia(,MediaPrompt=Please insert the disk: [ProductName] LABEL,MediaCabinet=Cabs.w1.cab,BytesPerTick=32768,CopierType=2,ModuleFileName=C:\WINDOWS\Installer\1fe4a.msi,,,,,IsFirstPhysicalMedia=1)
MSI (s) (54:B0) [13:39:52:869]: Executing op: FileCopy(SourceName=PSLICE~1.XML|PSLicence.xml,SourceCabKey=PSLicence.xml,DestName=PSLicence.xml,
Attributes=0,FileSize=146090,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,
HashPart1=1124213334,HashPart2=-439749084,HashPart3=-973851377,HashPart4=467277008,,)
MSI (s) (54:B0) [13:39:52:869]: File: C:\Documents and Settings\All Users\Application Data\ESRIUK\LicenceStore\PSLicence.xml; Overwrite; Won't patch; Existing file is unversioned and unmodified - hash doesn't match source file
MSI (s) (54:B0) [13:39:52:869]: Source for file 'PSLicence.xml' is compressed
MSI (s) (54:B0) [13:39:52:869]: Re-applying security from existing file.
MSI (s) (54:B0) [13:39:52:869]: Verifying accessibility of file: PSLicence.xml
Further down the log is the old MSI component being removed:
MSI (s) (54:98) [13:39:54:275]: Executing op: FileRemove(,FileName=PSLicence.xml,,ComponentId={05B86293-D430-4410-ACB2-1159677A2D78})
What am I doing wrong here?
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
Posted by:
dunnpy
13 years ago
I've used Wise in the past and had to move the 'removeexistingproducts' action up the sequence so that the old installation is effectively uninstalled before your new package is installed.
See here and here on the Symantec Support site for further information and the exact reasoning.
Hope that helps,
Dunnpy
Damn! Ian (VBSCab) beat me to the answer - again [:D]
See here and here on the Symantec Support site for further information and the exact reasoning.
Hope that helps,
Dunnpy
Damn! Ian (VBSCab) beat me to the answer - again [:D]
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.