Advanced Updater cannot install single EXE created by AI 12.8 - Advanced Installer Community
Zsolt Kollarits
Posts: 409
Joined: Fri May 29, 2015 10:36 am

Advanced Updater cannot install single EXE created by AI 12.8

Dear Advanced Installer Support,

Please let me report an issue to you, that is a very critical one for use due to our release date, a quick solution would be highly appreciated!

We upgraded to Advanced Installer 12.8 a few days ago to use your latest version for our next release. Our release will happen in the next week. While testing your Advanced Updater mechanism we noticed that EXE packages generated by AI 12.8 cannot be installed by the old versions of our product. (The old version is generated by AI 12.7 back that time.) An error appears in the Advanced Updater dialog right after we click on the "Next" button, the error is saying that the update failed to be installed.

At this point I checked the EventViewer for error messages and I found a Windows Installer error code: 1639 -> Invalid command line arguments. Here are the last few messages of the EventViewer, the first one is the oldest one:
Beginning a Windows Installer transaction: <path to msi>/TheClient.x64.msi. Client Process Id: 1348.
Product: <Product name> -- Installation failed.
Windows Installer installed the product. Product Name: <Product Name>. Product Version: 14.0.1. Product Language: 1033. Manufacturer: <Corporation>. Installation success or error status: 1639.
Ending a Windows Installer transaction: <path to msi>\TheClient.x64.msi. Client Process Id: 1348.
Windows Installer installed the product. Product Name: <Product Name>. Product Version: 14.0.1. Product Language: 1033. Manufacturer: <Corporation>. Installation success or error status: 0.

When seeing this messages I decided to remove the command line arguments from the updates config file. I tried to do it in 2 ways:
1. Manually removed the line of "NoGUICommandLineSwitch = /exenoui /qn" from the updates config file.
2. Found a hint at your webpage to use "aiemptyfield" content in the NoGUICommandLineSwitch field of your Advanced Updater project so I used that string.
Both ways had the same effect on the behavior and partially fixed the original problem:
- Windows Installer error 1639 is gone.
- The new version of our product is successfully installed on the end PC.
- BUT Advanced Updater dialog is never getting dismissed when deleting NoGUICommandLineSwitch or putting aiemptyfield into it. The dialog stays forever on the screen.

Please note that changing the version number of our .aip project back to 12.7.2, opening it by AI 12.7.2 and generating our EXE by that AI version creates a file that can be installed by Advanced Updater without any error messages in the EventViewer. Also we can keep our default
"NoGUICommandLineSwitch = /exenoui /qn"
line in the updates config file, everything runs as expected. That´s the reason why we´re highly confident our problem are caused by AI 12.8.

Could you please try to reproduce this behavior on your side if possible? Please install a product generated by AI 12.7.0 to a PC, then create a single EXE file (+ the corresponding updates config file) by AI 12.8 for the same product and try to install it by Advanced Updater. Hopefully you will see the Windows Installer error in EventViewer.

Due to our release date, this problem is really something we´d need to fix asap!

Please let me know if you have any questions!

Kind regards,
Zsolt
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Advanced Updater cannot install single EXE created by AI 12.8

Hello Zsolt,

We have tested your scenario but we are unable to replicate it.Can you please send us a sample project that replicates this behaviour? This will help us greatly to provide a solution in the shortest possible time.

Also, no similar issue was reported by other users.

Best regards
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Zsolt Kollarits
Posts: 409
Joined: Fri May 29, 2015 10:36 am

Re: Advanced Updater cannot install single EXE created by AI 12.8

Hi Dan,

After a lot of investigation I figured out the reason why it happens:
- if we use a space in the name of the folder where the update exe and update config files reside, the updater reports error 1639
- if the update folder name does not contain a space on the server side, the update can be installed without any problems

Please remember, the problem happens only if the update config file is created by AI 12.8. So basically there are 2 requirements of seeing the bug:
- create the update config by AI 12.8
- insert your update into a folder that contains a space in its name

For example at some point of my testing I wanted to test if the update path could cause the 1639 error message or not. I performed the following steps:

1. Copied the EXE of our product and the belonging update config into the folder of "C:\ProgramData\<ProductName>\Updates\FromServer\Update 2016".
2. Launched the update mechanism from the command line by triggering your Updater.exe in the following way:
TheUpdater.exe /checknow -url "file://C:\ProgramData\<ProductName>\Updates\FromServer\Update 2016\UpdateConfig.txt"
By using this command the update installation was failed.
3. Renamed the "Update 2016" folder to "Update2016".
4. Launched the update mechanism from the command line by triggering your Updater.exe in the following way:
TheUpdater.exe /checknow -url "file://C:\ProgramData\<ProductName>\Updates\FromServer\Update2016\UpdateConfig.txt"
By using this command the update installation was successful.

Obviously I tried to reproduce it in a sample project, however I couldn't. I used a paths with spaces - actually I had the update for my Sample project in the exact same folder where the update for our product was located. The update for sample project was always installed without any problems.

I compared the update config files (our product's update config, sample project's update config), also played with that file, tried to achieve the update failure of the Sample project, but nothing helped. Updating our product was failing, while sample updated was working even if the update config files were almost the same.

Could you please advise me something? Could you please check if you added any modification to your Updater feature in AI 12.8 that might cause our problem with whitspaces characters in update paths?

Best regards,
Zsolt
onclethomas
Posts: 1
Joined: Wed Apr 27, 2016 8:00 am

Re: Advanced Updater cannot install single EXE created by AI 12.8

Hi,

I can completely confirm the experiences of Zsolt Kollarits.

I also create a setup package "Single EXE setup (with resources inside)" and run it as part of an auto updater inside the application. The setup package is downloaded to the system default download folder and run with the command line /passive. Since AI 12.8 this does not work anymore. The log file points to the following (marked line):

Code: Select all

MSI (s) (C8:58) [08:55:40:777]: PROPERTY CHANGE: Adding AI_SETUPEXEPATH property. Its value is 'D:\Eigene Dateien\Documents\<product>\deploy\<product>_setup_0.9.exe'.
MSI (s) (C8:58) [08:55:40:777]: PROPERTY CHANGE: Adding SETUPEXEDIR property. Its value is 'D:\Eigene Dateien\Documents\<product>\deploy\'.
MSI (s) (C8:58) [08:55:40:777]: PROPERTY CHANGE: Adding EXE_CMD_LINE property. Its value is '/exenoupdates  /noprereqs  /passive /L*V "D:\config_msi.log" '.
MSI (s) (C8:58) [08:55:40:777]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '16708'.
MSI (s) (C8:58) [08:55:40:777]: PROPERTY CHANGE: Adding CHAINERUIPROCESSID property. Its value is '16708Chainer'.
---->  MSI (s) (C8:58) [08:55:40:777]: PROPERTY CHANGE: Adding AI_UNINSTALLER property. Its value is 'CURRENTDIRECTORY="D:\Eigene'.    <----
MSI (s) (C8:58) [08:55:40:777]: Note: 1: 1708 
MSI (s) (C8:58) [08:55:40:777]: Product: <product> -- Installation failed.

MSI (s) (C8:58) [08:55:40:777]: Das Produkt wurde durch Windows Installer installiert. Produktname: <product>. Produktversion: 0.9. Produktsprache: 1033. Hersteller: <...>. Erfolg- bzw. Fehlerstatus der Installation: 1639.

MSI (s) (C8:58) [08:55:40:779]: MainEngineThread is returning 1639
Info 1639. Ungültiges Befehlszeilenargument. Ausführliche Befehlszeilenhilfe finden Sie im SDK des Windows-Installationsprogramms.
DATEIEN\DOCUMENTS\_AES
Running the setup from a path without spaces is fine. Same goes when I create a single msi with resources inside setup and run the msi from anywhere (even the faulty path from above).

Conclusion is: Bootstrapper is buggy.

cheers
Thomas
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Advanced Updater cannot install single EXE created by AI 12.8

Hello all,

Thank you for your feedback.

We have further investigate this and indeed, this is an Advanced Installer issue that will be fixed in the next version. If you want the fix earlier you can download the ExternalUi.zip file from the following link.

Then, extract the file to the following path and rebuild your project:

Code: Select all

C:\Program Files (x86)\Caphyon\Advanced Installer 12.8\stubs\x86\
Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
R.Mueller
Posts: 202
Joined: Thu Aug 02, 2012 3:31 pm

Re: Advanced Updater cannot install single EXE created by AI 12.8

Hi Dan,

is there an estimated release date for this upcoming version?

Regards,

Roland
Zsolt Kollarits
Posts: 409
Joined: Fri May 29, 2015 10:36 am

Re: Advanced Updater cannot install single EXE created by AI 12.8

Hi Dan,

Thanks very much for your fixture, it seems to be working in our side!

Best regards,
Zsolt
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Advanced Updater cannot install single EXE created by AI 12.8

Hi,

@Roland: The next version of Advanced Installer is expected to be released at the end of May. Until then you can download the fixed ExternalUi file.

@Zsolt: Thank you for your feedback.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”