Fatal error when build msp

[ficco2024]

Hello there,

I am getting a fatal error when building msp from old.msi to new.msi, while old.msi never change and new.msi build without error.
Here is the log:

aella@BUILDMASTER-WIN C:\Program Files\Git\root\ws\5.3.0>"c:\Program Files (x86)\Caphyon\Advanced Installer 21.7.1\bin\x86\AdvancedInstaller.com" /build "aella_deploy\msi\wds.1.aip" -buildslist "DefaultBuild"

Checking builds status
Build required.


[ DefaultBuild ]
Building package: C:\Program Files\Git\root\ws\5.3.0\output\x64\wds.msi
Prepare build
Detecting MSI incompatible resources
Preparing files
Creating CAB file(s)
Preparing binaries
Creating MSI database
Inserting CAB file(s) into MSI
Writing Summary Information
Validating MSI

Total build time: 58 sec.

Build finished successfully.

......

aella@BUILDMASTER-WIN C:\Program Files\Git\root\ws\5.3.0>set adv_com_path="c:\Program Files (x86)\Caphyon\Advanced Installer 21.7.1\bin\x86\AdvancedInstaller.com"

aella@BUILDMASTER-WIN C:\Program Files\Git\root\ws\5.3.0>set version=5.3.0

aella@BUILDMASTER-WIN C:\Program Files\Git\root\ws\5.3.0>set file_name=Windows_Sensor_4.3.7_5.3.0-x64.msp

aella@BUILDMASTER-WIN C:\Program Files\Git\root\ws\5.3.0>set arch=x64

aella@BUILDMASTER-WIN C:\Program Files\Git\root\ws\5.3.0>set base_branch=5.3.0

aella@BUILDMASTER-WIN C:\Program Files\Git\root\ws\5.3.0>set project_file_path="aella_deploy\msi\wds_patch.1.aip"

aella@BUILDMASTER-WIN C:\Program Files\Git\root\ws\5.3.0>set generated_msp="C:\Program Files\git\root\ws\5.3.0\aella_deploy\msi\patch_output\Windows_Sensor_4.3.7_5.3.0-x64.msp"

aella@BUILDMASTER-WIN C:\Program Files\Git\root\ws\5.3.0>set final_msp_pkg="C:\Program Files\git\root\ws\5.3.0\Windows_Sensor_4.3.7_5.3.0-x64.msp"

aella@BUILDMASTER-WIN C:\Program Files\Git\root\ws\5.3.0>set output_dir="C:\Program Files\git\root\ws\5.3.0\aella_deploy\msi\patch_output"

aella@BUILDMASTER-WIN C:\Program Files\Git\root\ws\5.3.0>set msp_log_file="C:\Program Files\git\root\ws\5.3.0\aella_deploy\msi\patch_output\msp_build.log"

aella@BUILDMASTER-WIN C:\Program Files\Git\root\ws\5.3.0>rmdir /S /Q "C:\Program Files\git\root\ws\5.3.0\aella_deploy\msi\patch_output"
The system cannot find the file specified.

aella@BUILDMASTER-WIN C:\Program Files\Git\root\ws\5.3.0>if "x64" == "x86" (echo "No patch for 32bit" ) else ("c:\Program Files (x86)\Caphyon\Advanced Installer 21.7.1\bin\x86\AdvancedInstaller.com" /build "aella_deploy\msi\wds_patch.1.aip" )
Notification: Project converted from a previous version (18.3). After saving it with the current version of Advanced Installer (21.7.1) you will not be able to open it in previous versions.
Notification: A backup file will be automatically created on save and will be located next to the .aip you just opened. The backup file will be named "wds_patch.1.back(18.3).aip".

Checking builds status
Build required.

Building package: C:\Program Files\Git\root\ws\5.3.0\aella_deploy\msi\patch_output\Windows_Sensor_4.3.7_5.3.0-x64.msp
Running MSI patch compatibility tests
WARNING: Sequence changed. Sequence of file "aella_ctrl_win_srv.exe_1" changed in upgraded "C:\Program Files\git\root\ws\releases\5.3.0\Windows-x64.msi".
......
WARNING: Different authoring tools versions. The target "C:\Program Files\git\root\ws\releases\4.3.7\Windows-x64.msi" was built with "Advanced Installer 18.3 build e2a0201b" and the upgraded "C:\Program Files\git\root\ws\releases\5.3.0\Windows-x64.msi" was built with "Windows Agent Sensor".

Analyzing the MSI files found that the resulting patch might not apply correctly. The target or upgraded MSI broke some of the patch rules.

Creating PCP database
Windows Installer administrative installation failed. Installation can fail if MSI package contains chained packages. Fatal error during installation.

Build finished because an error was encountered.

And one day later, this process returns back to normal, and this is the log

aella@BUILDMASTER-WIN C:\Program Files\Git\root\ws\5.3.0>"c:\Program Files (x86)\Caphyon\Advanced Installer 21.7.1\bin\x86\AdvancedInstaller.com" /build "aella_deploy\msi\wds.1.aip" -buildslist "DefaultBuild"

Checking builds status
Build required.


[ DefaultBuild ]
Building package: C:\Program Files\Git\root\ws\5.3.0\output\x64\wds.msi
Prepare build
Detecting MSI incompatible resources
Preparing files
Creating CAB file(s)
Preparing binaries
Creating MSI database
Inserting CAB file(s) into MSI
Writing Summary Information
Validating MSI

Total build time: 57 sec.

Build finished successfully.

......
Notification: Project converted from a previous version (18.3). After saving it with the current version of Advanced Installer (21.7.1) you will not be able to open it in previous versions.
Notification: A backup file will be automatically created on save and will be located next to the .aip you just opened. The backup file will be named "wds_patch.1.back(18.3).aip".

Checking builds status
Build required.

Building package: C:\Program Files\Git\root\ws\5.3.0\aella_deploy\msi\patch_output\Windows_Sensor_4.3.7_5.3.0-x64.msp
Running MSI patch compatibility tests
WARNING: Sequence changed. Sequence of file "aella_ctrl_win_srv.exe_1" changed in upgraded "C:\Program Files\git\root\ws\releases\5.3.0\Windows-x64.msi".
......
WARNING: Different authoring tools versions. The target "C:\Program Files\git\root\ws\releases\4.3.7\Windows-x64.msi" was built with "Advanced Installer 18.3 build e2a0201b" and the upgraded "C:\Program Files\git\root\ws\releases\5.3.0\Windows-x64.msi" was built with "Windows Agent Sensor".

Analyzing the MSI files found that the resulting patch might not apply correctly. The target or upgraded MSI broke some of the patch rules.

Creating PCP database
Creating MSP

***** Log starting: 2024-09-06 03:29:50 *****

So could someone tell me what could be the root cause? Thank you very much

[Daniel]

Hi and welcome to our forums,

I cannot say why this happens. Maybe the patch project incorrectly caches the target and upgraded MSI files.

Can you try to use the rebuild command when building your patch project? This will force a target and upgraded MSI images refresh.

Just use a build command like this: AdvancedInstaller.com" /rebuild "patchProject.aip" and see if this fixes the issue.

All the best,
Daniel