Not enough storage is available to complete this operation

[pr1smiley]

Gent's

after downloading the x3 version and running as an admin i get the following error , any suggestions

btw i have 400GB of free HD space

MSI-0028.png (8.82 KiB) Viewed 8707 times

[FrancescoT]

Dear User,

For I what I see by your screen-shot, the error seems not to be related with the free space available.

Are you sure that the IA installer gets not corrupted? Because it seems so.

Did you use the Web or the Full installer of the product?

Regards

[GFXDude2010]

I am facing this same issue. I've recently upgraded to InstallAware X3 20.0.0.2015. It is stock, except for a single plugin "AxoNet Plug-Ins for InstallAware 2.2.0.22" which I use for firewall rules. I am using Authenticode Digital Signature, and have ticked both "Sign the pacakge with Authenticode" and "Include All Executables required for Windows 8 logo". I'm not sure what the latter option does. I have had a few issues before getting the signature to sign properly due to Novell network credential issues, but re-logging in tends to resolve that issue when building.

I have not received the error when building Uncompressed, only when building Single File. It does not occur during build, only when trying to install. The machine has 40+gb of space available. The final installation of the product only takes around 300Mb, though the single installer is ~500mb. This only occurs in Windows 7 (x86 and x64). It does not occur in my Windows 10 test environment. I have not attempted Windows 8. (Will test this soon and update post with results)

It is built on my development machine, and saved to shared network location using Novell network sharing. From there, I copy the standalone installer local to the test machine in QA lab. I then attempt to run the installer from the local test machine, and receive this error. Restarting the test machine allows the installer to work as expected, which I find odd. Since the installer doesn't work initially after copying from a network share, but does work after restarting the target machine, I do not believe that the installer is corrupted, as suggested in the last post.

[FrancescoT]

Dear GFXDude2010,

the corruption may occur on the temporary extracted files and not on setup package itself. For example, typically an Anti Virus may alter such files under the local temporary folder.

Anyway let me know if you have any other result to share.

Regards

[GFXDude2010]

I have been using the same test machine for probably 50+ test installations of the software. However, this issue has only come about in the past two days. The only significant changes I've made to the installer during this time is rearranging some msicode that backs up the current install before putting in place the new version, and added a few new batch scripts to remove registry and firewall entries on uninstall.

[FrancescoT]

BTW, I suggest you to update to the latest version available (IA X3 20.04.1). This includes some optimizations to the generated boot-strap.

Please note that due your current version, once installed the update, you need to use a new re-generated license file to activate the product.

Regards

[GFXDude2010]

I have taken your advice and updated to to the latest version of IA X3 20.04.1.2015, however the issue persists.

We use this same version for a few other installers, and none of them experience the same issue. They take the same path of copying to the network share, then being copied to the local machine to test the installation.

[FrancescoT]

Dear GFXDude2010,

for what you say the issue doesn't seem caused by a possible problem with the project or script (however everything is possible).

The only option that comes to my mind, it's to use "Process Monitor" tool to verify if exist any possibility to track down the effective cause.

You can download the tool from;
https://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

Hope this helps you.

Regards

[GFXDude2010]

I finally noticed that the machines this error was occurring on only had 2GB of memory. The installer is ~500MB, so I assume during the decompression it would run out of memory and begin paging data. This seems to throw the error in the original post. I've just added a higher memory requirement to the application.