LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrading with application installer removes exe

We have a LabVIEW 2018 project where we are building an executable and installer. Every time we create a new release the customer can just run the installer to upgrade. But all of a sudden, when the customer tries to upgrade one of our latest builds, during the upgrade the installer will remove to the exe and won't place the new one. We can reproduce this problem on our own systems. When we try the installer on a fresh machine, or after we manually delete te previous version, it works just fine, so this is the work around we are using now, but this is certainly not what we want to give to our customer.

 

We have looked in the logs, and the line where the clean install places the exe does not exist in the upgrade log.

 

The part in the installation log where the exe files are copied looks like this:

MSI (s) (EC:DC) [17:12:12:408]: Executing op: FileCopy(SourceName=CUSTOM~1.EXE|CustomerApplication.exe,SourceCabKey=CustomerApplication.EXE.1.5FE20081F6D441A199F0AA4953D2E5C3,DestName=CustomerApplication.exe,Attributes=16384,FileSize=21331400,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,Version=1.0.0.38,Language=0,InstallMode=126353408,,,,,,,)
MSI (s) (EC:DC) [17:12:12:408]: File: C:\Program Files (x86)\VI Technologies\CustomerApplication.exe;	To be installed;	Won't patch;	No existing file
MSI (s) (EC:DC) [17:12:12:408]: Source for file 'CustomerApplication.EXE.1.5FE20081F6D441A199F0AA4953D2E5C3' is compressed
MSI (s) (EC:DC) [17:12:12:565]: Executing op: FileCopy(SourceName=CUSTOM~1.ALI|CustomerApplication.aliases,SourceCabKey=CustomerApplication.ALIASES.2.5FE20081F6D441A199F0AA4953D2E5C3,DestName=CustomerApplication.aliases,Attributes=16384,FileSize=38,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,Language=0,InstallMode=126353408,,,,,,,)
MSI (s) (EC:DC) [17:12:12:565]: File: C:\Program Files (x86)\VI Technologies\CustomerApplication.aliases;	To be installed;	Won't patch;	No existing file
MSI (s) (EC:DC) [17:12:12:565]: Source for file 'CustomerApplication.ALIASES.2.5FE20081F6D441A199F0AA4953D2E5C3' is compressed
MSI (s) (EC:DC) [17:12:12:574]: Executing op: FileCopy(SourceName=CUSTOM~1.INI|CustomerApplication.ini,SourceCabKey=CustomerApplication.INI.3.5FE20081F6D441A199F0AA4953D2E5C3,DestName=CustomerApplication.ini,Attributes=16384,FileSize=333,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,Language=0,InstallMode=126353408,,,,,,,)
MSI (s) (EC:DC) [17:12:12:574]: File: C:\Program Files (x86)\VI Technologies\CustomerApplication.ini;	To be installed;	Won't patch;	No existing file

 

And the upgrade log looks like this

MSI (s) (C0:B4) [17:19:17:296]: Executing op: FileCopy(SourceName=CUSTOM~1.ALI|CustomerApplication.aliases,SourceCabKey=CustomerApplication.ALIASES.2.A6608538A0A743239CF9E6178EFF77BD,DestName=CustomerApplication.aliases,Attributes=16384,FileSize=38,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,Language=0,InstallMode=126353408,,,,,,,)
MSI (s) (C0:B4) [17:19:17:296]: File: C:\Program Files (x86)\VI Technologies\CustomerApplication.aliases;	To be installed;	Won't patch;	No existing file
MSI (s) (C0:B4) [17:19:17:296]: Source for file 'CustomerApplication.ALIASES.2.A6608538A0A743239CF9E6178EFF77BD' is compressed
MSI (s) (C0:B4) [17:19:17:403]: Executing op: FileCopy(SourceName=CUSTOM~1.INI|CustomerApplication.ini,SourceCabKey=CustomerApplication.INI.3.A6608538A0A743239CF9E6178EFF77BD,DestName=CustomerApplication.ini,Attributes=16384,FileSize=333,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,Language=0,InstallMode=126353408,,,,,,,)
MSI (s) (C0:B4) [17:19:17:403]: File: C:\Program Files (x86)\VI Technologies\CustomerApplication.ini;	To be installed;	Won't patch;	No existing file
MSI (s) (C0:B4) [17:19:17:403]: Source for file 'CustomerApplication.INI.3.A6608538A0A743239CF9E6178EFF77BD' is compressed

 

The copy action of the executable is just not showing up in the log, there are no errors reported.

 

We have no idea how this happened, but we would like to know if this is fixable.

Message 1 of 2
(752 Views)

Hello,

Was this issue fixed? 

0 Kudos
Message 2 of 2
(185 Views)