Dear Advanced Installer Support Team,
One of our customers just reported a problem for us: they are not able to install the latest version of our product - it was built by AI 13.6 - because one of our LaunchConditions always fails, although it should not. The LaunchCondition looks like this:
Condition:
(OriginalDatabase ~>< "x64" EQV VersionNT64) OR (PATCH ~>< "x64" EQV VersionNT64)
Description:
Please use the 64-Bit package for installations on a 64-Bit system!
It´s important to mention that this LaunchCondition was not touched by us for a while now. Obviously we installed our product on many different OS´ in many different ways, but the we´ve never seen this problem in the past. This LaunchCondition was always working as expected. Since the customer tried to install our product on several 32-bit and 64-bit Microsoft Windows 7 Professional N (version: 6.1.7601, build: 7601) machines, we alse tried to install it on the same OS, but the installation works on our side.
From the logfiles he attached I can see that our package has been distributed by System Center Configuration Manager, the path of our EXE looks the following: C:\Windows\ccmcache\5\TheClient.exe. This might make the difference. Apart from this I can see few more interesting things in the logfiles:
1. Logfile 1 (V93040NB03_MSI3E4D.log) seems to be the main logfile, it calls the process of C:\Windows\ccmcache\5\TheClient.exe.
2. Logfile 1 ends with FatalError.
3. Logfile 2 (V93040NB03_MSIc260c.log) seems to be the dependent logfile, it calls the process of C:\Windows\SysWOW64\msiexec.exe.
4. Logfile 2 contains the source of the problem, please find the following snipplet in it:
"
MSI (s) (74:98) [09:05:51:442]: Doing action: LaunchConditions
Action ended 09:05:51: DetectReportingSvcPath. Return value 1.
Action start 09:05:51: LaunchConditions.
MSI (s) (74:98) [09:05:51:442]: Product: Therefore™ 2017 Client -- Please use the 64-Bit package for installations on a 64-Bit system!
Action ended 09:05:51: LaunchConditions. Return value 3.
"
That´s why the customer is not able to install the product.
5. In Logfile 2 I see that the installation path is correct: C:\ProgramData\Therefore\Install\17.0.1\TheClient.x64.msi -> it´s visible in the beginning of the file. But lower I see some lines which are quite weird for me, for example
"MSI (s) (74:98) [09:05:51:062]: Original package ==> C:\Windows\ccmcache\4\TheClient.msi"
or
"MSI (s) (74:98) [09:05:51:091]: Package name retrieved from configuration data: 'TheClient.msi'"
or
"MSI (s) (74:98) [09:05:51:122]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'C:\Windows\ccmcache\4\TheClient.msi'."
I don´t understand why our 32-bit package (TheClient.msi) appears in this logfile at all. We should see TheClient.x64.msi everywhere. The test machine was a 64-bit machine, that´s why the x64 package is used in the beginning of logfile 2, which is correct. Despite of the 64-bit architecture, the OriginalDatabase property is changed to 'C:\Windows\ccmcache\4\TheClient.msi', although it should be 'C:\Windows\ccmcache\4\TheClient.x64.msi'. Do you have any idea why this happens? Naturally the incorrect value of OriginalDatabase leads the LaunchCondition to be failing few lines lower.
Note: Few weeks ago we already reported a problem with LaunchConditions that occurs in AI 13.6 only: http://www.advancedinstaller.com/forums ... 995#p92995. Do you think the current issue is somehow related to that one?
Please advise us something! Thanks in advance!
Best regards,
Zsolt
FOLLOW US
Get the latest news in Application Packaging