Hello Thomas,
Thank you for the provided config files. Unfortunately, that was not of much help as they are literally identical.
I've done some further investigations and here is what I have found:
First of all, the log file you have sent me is not from an upgrade process. The reason why I am saying this is because the
OLDPRODUCTS property is not set.
The
OLDPRODUCTS property represent a list with the
Product Codes of the older versions of your installation package. This property is set only in a package which upgrades another package.
In your case, the property is not set ==> the log can not be from an upgrade process.
If you have a look above, you will notice that I have said I was able to reproduce this when the search was failing - in my case, I made the search fail by deleting the config file.
Based on that, another scenario came to my mind -
to install the major version as a first time install (without a previous version installed). When doing so, I was able to reproduce the issue.
What I belive happens here is that you guys are installing the major version without a previous version already installed. That being the case, when the search is executed, the config file is not present on the machine ==> all the paths are wrongly set.
With that being said, could you please make a video in which you showcase the following:
1. install the older version
2. go to the install location and select the config file
3. install the newer version with the log file option (/L*V)
4. recheck the install location for the config file
5. open the log file and check for the APPDIR property
and then forward that video to me?
When you are testing this, please make sure (e.g. Control Panel) that the older version is installed.
Honestly, I can not think of any other scenario. The two config files you have sent me are identical and I can not see a reason why the search would fail on a PC and work on another.
Best regards,
Catalin
FOLLOW US
Get the latest news in Application Packaging