I resolved this issue. I was using a really old version of Advanced Installer 15.9. I upgraded my projects to the latest 22 and the issue seemed to go away.
I created an installer and enabled the updater feature. When I test the updater, it fails to perform the update. The new installer is located on the web server along with the updater text file. I also enabled the install support service as recommended.
I'm using the AI CLI to automate my builds. I have a "single EXE setup (resources inside)" package type. is there a way to get (via the CLI) the path to the EXE that was generated from the build?
In Windows, you can create a scheduled task and assign it so it is run by a group (such as Administrators). In AI you can only choose a user. So the task will run if any user of that group is logged-in.
I would like the ability to create a scheduled task that has no interval or schedule set. It is a task that I want to be able to execute manually by the user and not a specific date or time. There is no option for this.
I created a scheduled task item that is set to run by a user account that is created upon install. However, that task doesn't run because the user account does not have enough rights to run the task. I get an error: "The user account does not have permission to run the task". However, the task has ...
My installer has been working fine for months until I got a report from one user. He has a system configured with a directory junction using the following command:
MKLINK c:\users d:\users /J
When he launches my installer (has not proceeded yet, just launched), the installer creates some folders ...
The problem (i think) is that the precondition is setting a return code to Windows Installer. Anyone calling my msi will display an error because of the return code.
FOLLOW US
Get the latest news in Application Packaging