Installation failed on many systems - Advanced Installer Community
Fulgan
Posts: 101
Joined: Mon Feb 27, 2012 10:42 am

Installation failed on many systems

Hello,

My first deployment test using AI failed miserably: many of the users who used it have an impossible to understand file write error of a non-executable file. Of course, on my own system, it works perfectly.

I have attached the AIP and a sample verbose log.
Attachments
install.txt
(454.49 KiB) Downloaded 471 times
WinEUR.aip
(294.01 KiB) Downloaded 715 times
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Installation failed on many systems

Hi,

I looked over the files that you attached, but the verbose log file is not complete. Can you please send me a full verbose log of the installation, so I can see more details about the error that your users encounter?

Also, I noticed that the "Per-user only" installation type option is set in the "Install Parameters" page of your project while it is set to be installed in the "C:\GIT\WinEUR" location. It may happen that some non-administrator users do not have permissions to write directly on the Windows drive and that is why the file write error may appear. Can you try to use the default path ([AppDataFolder][ProductName]) and see if the error persists?

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Fulgan
Posts: 101
Joined: Mon Feb 27, 2012 10:42 am

Re: Installation failed on many systems

Hello,

I checked the log and it is complete: there is nothing left in my local log. I created the log by using the /lv option. Do you need it with /lx ?
Also, I noticed that the "Per-user only" installation type option is set in the "Install Parameters" page of your project while it is set to be installed in the "C:\GIT\WinEUR" location. It may happen that some non-administrator users do not have permissions to write directly on the Windows drive and that is why the file write error may appear. Can you try to use the default path ([AppDataFolder][ProductName]) and see if the error persists?
I can guarantee 100% that ACLs aren't the issue here: the failing file is actually created but at 0 bytes. I tried to grant full access to the base folder anyway (as a test) and I have the same result.

I can't change the destination folder though: that is the location where the app must be deployed by default. The only common thing I could find on all "failing" installs is that there was already a version of the app deployed there (using a different installer that doesn't rely on msiexec or even simply copied from a network location.

Edit Actually, scratch that: all tests (working and non-working) were done on machine having an install in the target location already.
Edit2 I have attached anotgher log crfeated with /lx this time
Attachments
install.zip
(20.96 KiB) Downloaded 927 times
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Installation failed on many systems

Hi,

Can you select the "Per-machine only" option for your package and see if the problem persists? If so, can you send me a download link to support at advancedinstaller dot com, so I can test your package and investigate the problem?

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Fulgan
Posts: 101
Joined: Mon Feb 27, 2012 10:42 am

Re: Installation failed on many systems

When installer installer is running with the "Per-machine only" option, the issue does not appear (at least, it worked on one machine where the previous package failed).

That being said, the main reason why I'm rewriting the installer is to get rid of the mandatory elevation so that is no solution. It doesn't explain the behavior of the installer either.

I will send you a link to the failing installer.

Thank you for your help,
regards,
Stephane
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Installation failed on many systems

Hello Stephane,

I tested the installer that you sent me by email on a Windows 10 64-bit machine and it was installed without any problem on both administrator and standard user accounts. However, since the installer worked with the "Per-machine only" option on a machine where it previously failed, it seems that it does not have the necessary permissions on that machine when it is installed per-user.

Please keep in mind that, as I mentioned above, the recommended installation path for a per-user package is the following: [AppDataFolder][Manufacturer]\[ProductName]

Can you try that path and see if the problem persists?

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Fulgan
Posts: 101
Joined: Mon Feb 27, 2012 10:42 am

Re: Installation failed on many systems

Hello and thanks again,

if the issue was simply an ACL one, then there wouldn't be a 0-byte file created in the target location when the installer failed. As I mentioned, the failure only occurred on some machines, not all of them (I don't have any issue on my local machine, for instance). Furthermore, I have tested simply unzipping the file on the failing machine and it works as well.

I can try installing the application in a different location but, as I explained, the result isn't going to be relevant: that folder must be the default destination (the product has been distributed in that folder since 1994 using a different installer technology).
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Installation failed on many systems

Hello Stephane,

In the log file it is mentioned that the installer cannot write into the "C:\GIT\WinEUR\formats\AchCVFUT.EP3" file. Does this error appear during an upgrade of your application or it appears during a fresh install, too?

It may also occur if some files are detected as a security threat by the anti-virus. Can you try to disable it during the installation of your product and see if the problem persists?

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Fulgan
Posts: 101
Joined: Mon Feb 27, 2012 10:42 am

Re: Installation failed on many systems

Hello,
In the log file it is mentioned that the installer cannot write into the "C:\GIT\WinEUR\formats\AchCVFUT.EP3" file. Does this error appear during an upgrade of your application or it appears during a fresh install, too?
I have a limited set of systems were we performed the installation test so I'm not sure.

In the 3 cases that I investigated directly, it was an upgrade of the product but not from this installer. All were local deployment using an old installer (written with InstallShield 6 so not using MSI).
It may also occur if some files are detected as a security threat by the anti-virus. Can you try to disable it during the installation of your product and see if the problem persists?
I have already tried that and it isn't the issue. The AV does not detect anything and the problem persist when no AV is running.
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Installation failed on many systems

Hello Stephane,

If those files are already on the machine from an older version, please make sure that they are not kept in use during the upgrade and that there is no restriction that do not let the new package modify them.

Does the problem also appear when a fresh install is performed?

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Fulgan
Posts: 101
Joined: Mon Feb 27, 2012 10:42 am

Re: Installation failed on many systems

If those files are already on the machine from an older version, please make sure that they are not kept in use during the upgrade and that there is no restriction that do not let the new package modify them.
These files aren't locked.
Does the problem also appear when a fresh install is performed?
No. There is no problem either if the installation is performed in a path that does not exists (e.g. c:\git2\wineur).

It seems only to be an issue if the target files already exists.

Edit: Manually starting the installer as admin (from an admin command-line, running "msiexec -i wineur.msi") will let it overwrite the target files correctly as well.

It is as if the file was created in the context of the current user but content was written in the context of a different one.
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Installation failed on many systems

Hello,

This seems like a permissions problem since the package can be installed correctly with administrator rights, but cannot be installed without them.

However, isn't the old version of the product uninstalled before the installation of the new one (this is the normal behavior of a Windows Installer package)? In this case, the files should not be present in that folder during the installation of the new version.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Fulgan
Posts: 101
Joined: Mon Feb 27, 2012 10:42 am

Re: Installation failed on many systems

This seems like a permissions problem since the package can be installed correctly with administrator rights, but cannot be installed without them.
Yes, but with a catch: if I provide a ZIP of the application instead of a MSI, the user can also simply unpack it in the destination folder.
However, isn't the old version of the product uninstalled before the installation of the new one (this is the normal behavior of a Windows Installer package)?
No. The old system didn't use windows installer and it's not registered as an upgrade. Previously, updating the product was simply a matter of unpacking the archive into the destination folder.
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Installation failed on many systems

Hello,
Yes, but with a catch: if I provide a ZIP of the application instead of a MSI, the user can also simply unpack it in the destination folder.
I'm not sure where this difference comes from. In order investigate the problem, please send me all the resources and the steps that I need to take in order to reproduce it.
No. The old system didn't use windows installer and it's not registered as an upgrade. Previously, updating the product was simply a matter of unpacking the archive into the destination folder.
As a workaround, you can use the Folder Removal operation in order to remove the application's folder before installing the new version.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Fulgan
Posts: 101
Joined: Mon Feb 27, 2012 10:42 am

Re: Installation failed on many systems

I'm not sure where this difference comes from. In order investigate the problem, please send me all the resources and the steps that I need to take in order to reproduce it.
I can't because I don't understand the difference between the system where the installer works and the ones where it doesn't work.


edit If you want, we can do a remote assistance session on one of the affected machines.
As a workaround, you can use the Folder Removal operation in order to remove the application's folder before installing the new version.
That will not work, unfortunately (once again, it's because of history: some users have some custom modules implemented as additional executables in that folder and, a long time ago, the application user to place several config files in that folder that contains important information. We can't force users to move them. Or rather, we could, but we can't do that in the installer).

Return to “Common Problems”