files not being installed

[mheckmann]

Hi,

since a couple builds the installer started missing some files when installing our software. Weirdly enough once running the installer again and choosing "Repair", it would add the previously missing files.

In the Files and Folders section I have 3 synchronized Folders where the missing files reside. In the properties of each of these Folders I have the Option "Ensure that all files in this folder overwrite..." checked.
Now I am wondering, should I check the vital option on the files to really make sure they are installed? This brings to the problem though to how to set this option on new files that are added during the build of the installer?

Thx
Markus

[mihai.petcu]

Hi Markus,

Does this behavior manifest during an upgrade or a first time install? The "Ensure that all files in this folder overwrite any installed target files" option you enabled should ensure the existing files get overwritten during an upgrade.
Also, can you please generate an installation verbose log and send to us so we can see what's going on?

If you didn't already know, when a file marked as vital is not installed correctly, the installation will stop and rollback.

All the best,
Mihai

[mheckmann]

Hi Mihai,

this happens during an upgrade process. The missing file in this case is libLIVE.dll but going through the log it seems to be also removing a whole bunch of other files in the numpy folder..

I had the file libLIVE.dll set to be 'vital'. I didn't set all the other files as there are so many in as many subfolders. I would need an option to set the vital flag via command-line or globally like the overwrite flag is set on the folder...

The Log (MSI72AF) is attached. I also attached the log for the repair process when running the exact same installer again (which fixes all missing files..) - (MSIE1D6)
Thank you very much for looking at this.
cheers
Markus

[mihai.petcu]

Hi Markus,

The file you mentioned seems to be overwritten from the MSI72AF log file. Is this the correct upgrade installation log?

Code: Select all

MSI (s) (80:50) [00:08:32:584]: Executing op: FileCopy(SourceName=libLIVE.dll,SourceCabKey=libLIVE.dll,DestName=libLIVE.dll,Attributes=512,FileSize=102400,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,Version=65535.65535.65535.65535,Language=0,InstallMode=58982400,,,,,,,)
MSI (s) (80:50) [00:08:32:584]: File: C:\Program Files (x86)\Derivative\TouchDesigner088\bin\libLIVE.dll;   Overwrite;   Won't patch;   New file versioned - existing file unversioned

Also, please send us the project files (.AIP) as well so we can have more information to work with.

All the best,
Mihai

[mheckmann]

Hi Mihai,

yup, that's the file. I see further down in the log this line which confuses me:

Code: Select all

MSI (s) (80:40) [00:08:34:705]: Executing op: SetTargetFolder(Folder=C:\Program Files (x86)\Derivative\TouchDesigner088\bin\)
MSI (s) (80:40) [00:08:34:705]: Executing op: FileRemove(,FileName=libLIVE.dll,,ComponentId={E6DA9493-C069-4D37-B447-6A73FC7EB8E2})
MSI (s) (80:40) [00:08:34:705]: Verifying accessibility of file: libLIVE.dll

together with a bunch of other files which I then discovered are not installed either...

attached is the aip file.
Thx
Markus

[mihai.petcu]

Hello Markus,

Actually, we'll need both consecutive versions project files so we can compare the file settings. If they contain any confidential information you can send them by e-mail to support at advancedinstaller dot com.

All the best,
Mihai

[mheckmann]

Hi Mihai,

what we usually do is change the version via command line, create the installer and then revert back to the original aip file. I didn't revert the file this time so here is the latest aip and log (MSID885.LOG) for the upgrade install as well as the log for the repair (MSI7216.LOG) when running the same installer again and choosing the repair option.

It's the same here that when I use this file for a fresh install everything will be flawless yet if I install this ontop of a existing install to perform an update, it missis the libLIVE as well as some other files...

Does that help?

Thx
Markus

[mihai.petcu]

Hello Markus,

what we usually do is change the version via command line, create the installer and then revert back to the original aip file.

This is not a correct way to handle an update scenario. Comparing the two projects you sent (0.88.3800 vs. 0.88.3980) I found they have different Upgrade Codes. I'm surprised only a couple files manifest unexpected behavior and that the upgrade works at all.

The correct steps to handle upgrades are described in the following user guide articles:
For major upgrades : Upgrades Page (before building the .AIP files, a recommended approach is to use "Save as..." to store projects for each version)
For patches : Authoring a Windows Installer patch

All the best,
Mihai

[mheckmann]

Hello Mihai,

ah - my fault - we are setting the upgrade code via command-line as well and in general I'm following what is described on the Updates Page. So the first aip file I send to you was more like the "template" we have sitting in a git repository and run following commands on:

Code: Select all

   $(AIP_PATH) /edit $(AIPFILE) /SetVersion $(TVER2)
   $(AIP_PATH) /edit $(AIPFILE) /SetPackageName $(PACKAGE_NAME)
   $(AIP_PATH) /edit $(AIPFILE) /SetProductCode -langid 1033
   $(AIP_PATH) /edit $(AIPFILE) /SetProperty Product="$(SUFFIX4)"
   $(AIP_PATH) /edit $(AIPFILE) /AddMsm "C:\$(PF)\Common Files\Merge modules\Microsoft_VC80_CRT_x86.msm"
   $(AIP_PATH) /edit $(AIPFILE) /AddMsm "C:\$(PF)\Common Files\Merge Modules\policy_8_0_Microsoft_VC80_CRT_x86.msm"
   $(AIP_PATH) /edit $(AIPFILE) /SetProperty UpgradeCode="$(UPGRADECODE)"


This way making sure that the upgrade code is always the same...

While looking over the upgrade code page again I found though that somehow the setting for the upgrade order was:
install first then uninstall old version
which I guess was causing these problems...
Further investigation showed that this option is turned on by running the "Persistent User Data" Wizard. Here I was trying to keep Registry Keys around which are shared between several versions of our product but AdvancedInstaller would remove when updating:

For example a file extension is installed into HKEY_CLASSES_ROOT for our 32-bit version. Now I install our 64-bit version which adds in Keys to the file extension's Registry entry. When next running an update on the 32-bit version, the first occurring uninstall would remove the file extension from the registry completely and readd it but loosing the entries for the 64-bit version. Not sure how to handle this now...

cheers
Markus

[mihai.petcu]

Hi Markus,

Further investigation showed that this option is turned on by running the "Persistent User Data" Wizard.

If this is indeed the culprit then you can try upgrading to the latest Advanced Installer version and use the registry key Persistence operation instead.
This is a new feature which doesn't condition the upgrade installation order and is available starting with version 9.4.

All the best,
Mihai

[mheckmann]

Thanks, I'm trying out 9.4!
Just out of interest and to understand it more - where would I find information about the install first then uninstall order to see why some files would be uninstalled at the end that are contained in the new package? I'm guessing something in my configuration is wrong.

Thx
Markus

[mihai.petcu]

Hi Markus,

"Install new version first and then uninstall old version" option is kinda tricky and you should use the other method if you have a choice.
Most related information can be found in Windows Installer Upgrades article.

All the best,
Mihai

[mheckmann]

9.4 and the registry persistence option works great and seems to solve the issue.

Thanks for all the help
Markus