IA17: Not enough storage to process: XP only

[JeffryPaul]

Recently upgraded from IA15 to IA17.0.4. I believe the problem regarding compression still exists, at least on Windows XP. I am not able to replicate this error on Windows 7, Vista, or Windows 8.
My main setup calls a second setup prior to the Finish screen. Both setups have been updated to include LANGUAGE=English compiler variable, and both have been recompiled with IA 17.0.4 using "Best" compression.

The main IA setup calls a second IAs Setup using Run Program $TARGETDIR$\AnotherSetup.exe
As the second setup is decompressing I receive the error: Runtime error in install: Not enough storage is available to process this command. Also included a screenshot. If I run that second setup from outside the main setup (silently or interactively), no problems.

Any help is appreciated.

[FrancescoT]

Dear JeffryPaul,

Honestly, I'm not quite sure that this problem could be related to a compression/de-compression error.

If for you it is a possible to send me those packages or a sample that replicates the issues, I'll try to verify it.

If you don't want to use the forum, contact me at; support@installaware.com .

Regards

[sjziegler]

I got the same error message when trying to run my first single file installation in IA 17. My installation does not call another one, but contains multiple "Run Program" and "Run Program As" lines. I am also running XP. It ran fine on a Windows 8 machine.

[sjziegler]

I tried reducing the compression incrementally all the way down to none, with the same results each time. I also tried creating a CD/DVD installation, but it just failed more quickly. We had planned to deploy this to our customers in the next few days. Please help!

[FrancescoT]

Dear User,

As with the my previous reply to "JeffryPaul", I'm not quite sure that this problem could be related to a compression/de-compression error.

If for you it is a possible to send me your package or a sample that replicates the issues, I'll try to verify it.

If you don't want to use the forum, contact me at; support@installaware.com .

Regards

[Aaron Young]

Some of our customers have also been running into this on Windows Server 2003 after we recently upgraded our installations to IA17.
I was wondering if this issue has been found and resolved in IA18 which I also have, but have not yet installed.

Regards,

- Aaron.

[FrancescoT]

Dear Aron,

honestly, we are not informed of similar problem and ... we was not able to replicate it.

Regards

[danielb]

I have same problems on both a XP machine and a 2003 Server after upgrading to IA17. Upgraded to IA18, but the problem remains. This a serious problem problem for us.
On Windows 7 och Windows 8 in same domain there are no problems. I've also tried the solution mention in http://www.intelliadmin.com/index.php/2007/04/not-enough-server-storage-is-available-to-process-this-command-solution/ without success. I will send the installation by mail to you.

Best regards,
Daniel Bengtsson

[FrancescoT]

Let me check it.

Regards

[sjziegler]

GOOD NEWS! We finally solved our issue with XP. During my install I display more dialogs than might be common for a simple installation, which ours is not. We are actually running lots of commands to upgrade databases. In one case I had 77 calls to display a the same error dialog, passing it variables to handle the text which was displayed and then going to a label that cleans up the install. I replaced these with go to label error. This label is below the last line of code after Terminate Installation and does the call to Display Dialog error and go to label cleanup. My application will now run on XP. My co-worker who discovered the issue by commenting out all of the display dialog calls suggested that there may be a difference between how the memory is allocated on XP and other versions of Windows. In any case, we will now finally begin to deploy this application to our large and diverse customer base. Hopefully some of the rest of you can benefit from our findings.

[FrancescoT]

Dear Sjziegler,

many thanks to share these useful information.

By the way, I found the same results testing an user project.

Regards

[Aaron Young]

We still have customers running into this issue on XP and Windows Server 2003; we have tried updating to InstallAware 18 and that did not resolve the problem.
I am now in the process of reverting back to IA 2012 (the version we were using before having the issue.)

We are using very generic dialogs (those provided by the template) and do not do much in the way of custom scripting.
Has anyone else discovered a method of replication or a solution?

[FrancescoT]

Dear Aaron Young,

I have personally verified this "possible" issue and honestly I am not able to replicate the same.

Just for example, I have tested every single package created using my personal IA projects and any of these work fine on a Win XP machine.
I can also assure you, that creating a new project from scratch the problem is not reproducible as well.

For what I have personally verified, the problem is caused by an improper use of setup resources.
Consider also that due the UNICODE support introduced with the most IA recent versions, an increment of required runtime memory It's unavoidable ... and unfortunately with a legacy OS as it is WIN XP, this is more noticeable (mainly due to the kernel enhancements available with the most recent OSes).

Regards

[Aaron Young]

Francesco,

Reverting a build machine back to using IA 2012 did resolve the issue for us.

I understand that without replication, troubleshooting, let alone resolving a problem such as this is extremely difficult and we have had no luck replicating this problem internally either.
It does seem that the majority of instances seem to occur on Windows 2003 Server machines and to a lesser extent XP.

Changing back to IA 2012 does seem to indicate the problem does lay with the IA product or some framework component it utilizes/doesn't between that version and IA 17.
The install projects themselves have not been altered at all between version updates, so I'm confident it's not something we have changed.
Our installations use the .NET Project Template and we use a subset of the Dialogs provided, we do utilize 2 3rd party plug-ins (AxoNet - UpgradeCode and mdPlugins - InstallFONTs.)
Otherwise our install is very basic and does nothing out of the ordinary.

Our own product is discontinuing support for Windows XP and 2003 Server at the end of the 1st quarter of 2014, so I don't foresee this being an issue past that point.
In the mean-time, it's an inconvenience we now have a workaround for (using the 2012 version IA.)

We will continue to try and replicate the problem and if we do so will provide you with that information.

Regards,

- Aaron.

[kpm30519]

I am using IA16 as well. and I am having this exact same issue-- Not only on Windows Server 2012, but I've also seen it on a Windows Vista (Business) 32- bit version, which means I absolutly cannot release our prodict. (If it happens on one it will happen on many...)

Changing /removing compression had no effect, and neither did changing the IRPStackSize as suggested in an offshoot of this thread.

So, how do I generate a license for an older version?


K.