Alex99
Posts: 42
Joined: Thu Feb 14, 2013 9:28 am

Quite installation does not extract files

Hello, I use Advanced Installer for building installer into Single exe setup. And it works fine. But if I try to start Installer in basic UI mod (/qb parameter) during installation message appears:
Untitled.png
Untitled.png (7.3 KiB) Viewed 9372 times
In log I see:

Code: Select all

MSI (s) (38:34) [13:09:23:583]: Executing op: ProgressTotal(Total=926353114,Type=0,ByteEquivalent=1)
MSI (s) (38:34) [13:09:23:583]: Executing op: SetTargetFolder(Folder=C:\Program Files\MyApp)
MSI (s) (38:34) [13:09:23:583]: Executing op: SetSourceFolder(Folder=1\config~1\|config_secondary_server\)
MSI (s) (38:34) [13:09:23:583]: Executing op: ChangeMedia(,MediaPrompt=Please insert the disk: ,,BytesPerTick=65536,CopierType=0,,,,,,IsFirstPhysicalMedia=1)
MSI (s) (38:34) [13:09:23:583]: Executing op:  FileCopy(SourceName=db~1.con|db.config,SourceCabKey=db.config_4,DestName=db.config,Attributes=0,FileSize=585,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=58982400,,,,,,,)
MSI (s) (38:34) [13:09:23:584]: File: C:\Program Files\MyApp\MyFile;	To be installed;	Won't patch;	No existing file
MSI (s) (38:34) [13:09:23:584]: Source for file 'MyFile' is uncompressed, at 'C:\Users\user\AppData\Roaming\<MyCompanyName>\<ProductName><ProductVersion>\install\07DACF2\'.
MSI (s) (38:34) [13:09:23:585]: Note: 1: 1309 2: 3 3: C:\Users\user\AppData\Roaming\<MyCompanyName>\<ProductName><ProductVersion>\install\07DACF2\MyFile 
MSI (s) (38:34) [13:09:23:585]: Note: 1: 1309 2: 3 3: C:\Users\user\AppData\Roaming\<MyCompanyName>\<ProductName><ProductVersion>\install\07DACF2\MyFile 
MSI (s) (38:34) [13:09:23:585]: Note: 1: 1309 2: 3 3: C:\Users\user\AppData\Roaming\<MyCompanyName>\<ProductName><ProductVersion>\install\07DACF2\MyFile 
MSI (s) (38:34) [13:09:23:586]: Note: 1: 1309 2: 3 3: C:\Users\user\AppData\Roaming\<MyCompanyName>\<ProductName><ProductVersion>\install\07DACF2\MyFile 
MSI (s) (38:34) [13:09:23:586]: Note: 1: 1309 2: 3 3: C:\Users\user\AppData\Roaming\<MyCompanyName>\<ProductName><ProductVersion>\install\07DACF2\MyFile 
MSI (s) (38:34) [13:09:23:586]: Note: 1: 1309 2: 3 3: C:\Users\user\AppData\Roaming\<MyCompanyName>\<ProductName><ProductVersion>\install\07DACF2\MyFile 
MSI (c) (8C:7C) [13:09:23:591]: Font created.  Charset: Req=0, Ret=0, Font: Req=, Ret=Arial

Error 1309. Error reading from file: C:\Users\user\AppData\Roaming\<MyCompanyName>\<ProductName><ProductVersion>\install\07DACF2\MyFile.  System error 3.  Verify that the file exists and that you can access it.
MSI (s) (38:34) [13:09:34:848]: Product: NeoFace Watch -- Error 1309. Error reading from file: C:\Users\user\AppData\Roaming\<MyCompanyName>\<ProductName><ProductVersion>\install\07DACF2\MyFile.  System error 3.  Verify that the file exists and that you can access it.

MSI (c) (8C:7C) [13:09:34:851]: Font created.  Charset: Req=0, Ret=0, Font: Req=, Ret=Arial

Are you sure you want to cancel?
MSI (s) (38:34) [13:09:36:347]: Note: 1: 2265 2:  3: -2147287035 
MSI (s) (38:34) [13:09:36:347]: User policy value 'DisableRollback' is 0
MSI (s) (38:34) [13:09:36:348]: Machine policy value 'DisableRollback' is 0
Action ended 13:09:36: InstallExecute. Return value 3.
Option set Media->ExtractLocation: [AppDataFolder][|Manufacturer]\[|ProductName][|ProductVersion]\install
When I start install I see that free space on disk C:\ decreased approximately by 1GB, it is size of unpacked my application
I see that file C:\Users\user\AppData\Roaming\<MyCompanyName>\<ProductName><ProductVersion>\install\07DACF2\MyFile is not exist. I can't find "MyFile" by windows file searching tool.
I tried to create a simple installer project with several files to try reproduce it but installation ended successfully. What I could do wrong? How I can force extract files from command line?
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Quite installation does not extract files

Hello,

This can happen if the extraction path of your installer files has a long path. The maximum length of a file path in Windows is 260 characters. So, if your installer files would have a file path (after being extracted in the extract location) longer than 260 characters, then the installation package won't be able to access them. The extract location can be configured from "Media page -> Configuration tab -> Extract location" field".

However, if this is the case, then the installation should also fail when installing with full UI. In order to have a better view of your installation scenario, can you please send us the .AIP (project file) and a verbose log of the installation to support at advancedinstaller dot com so we can investigate them?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Quite installation does not extract files

Hello,

After investigating this issue it seems this happens because you set an install property from command line, when launching the EXE setup, like this:
  • MY_PROP="myValue
without closing the second quotes character. This is an invalid MSI command line, but unfortunately our EXE bootstrapper skips this validation. Therefore, the EXE bootstrapper will call the embedded MSI with a wrong computed command line and, thus the embedded installation files are not extracted at install time. This is an Advanced Installer limitation and a fix will be available in a future version of Advanced Installer. Thank you for bringing it to our attention.
Until then as a workaround you should simply set correctly the property from command line like this
  • MY_PROP="myValue"
or like this:
  • MY_PROP=myValue
If you have any questions let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Quite installation does not extract files

Hello,

This was fixed in version 16.2 of Advanced Installer released on August 1st, 2019.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”