IA17: Not enough storage to process: XP only

[FrancescoT]

Dear kpm30519,

I suppose you posted a reply to the wrong topic ... this is related to a possible issue with the generated sutup exe when executed under WIN XP.

Anyway, you can currently generate a license file for the served IA version only ( ... if your personal account is not expired).

Regards

[kpm30519]

No, this is the correct topic. I get the EXACT SAME ERROR on Windows Vista (32- bit Business edition) as well as Windows Server 2003 R2. I do not test on Windows XP. The point of this post is to let you know this issue is more widespread than what the OP posted. If you notice, OP Aaron Young has described exactly what I am experiencing, and also stated that reverting to IA 2012 resolves the issue.

Since reinstalling IA 2012, the issue has disappeared, thus showing that it is indeed an issue with one of the later releases.

K.

[FrancescoT]

Dear K,

... try to post a project that replicates your issue and I'll check it.

Regards

[FrancescoT]

Dear K,

... try to post a project that replicates your issue and I'll check it.

Regards

[MartinIW]

Hello together,
we have the same problem here. We updated a long while ago from 2009 R2 to 15 then 16 and now 17.
I know this post may be for XP only, but we mentioned the problem on now two computers with windows 2003 Server.
I tried the way back and installed 2009 R2 to create an setup with the same binaries like the setup we created with InstallAware 17 and it works!
So what I can say this works for us, but its not a solution. We now have to handle two setups with different installAware versions.
I didnt try to update to IA 18 because Aaron Young mentioned that didnt work either.
To come to a point: Is there any solution to get IA 17 working with Windows 2003 Server?
I also could send our setupproject if that may help!?

If that may also happen in XP we are in big trouble...because about 30% of our customers are using this at least.

Thanks in advance,
Martin

[FrancescoT]

Dear Martin,

have you also checked the suggestion reported by "sjziegler"?

by sjziegler » Thu Nov 14, 2013 9:51 pm

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.

Regards

[MartinIW]

I have not tried this yet because i only have 6 calls of "MessageBox:" inside our MSICode.
For me it seams that this is the problem.
We have one Setup for two different products. So we either show the one or the other dialog controlled by a compiler variable each time a dialog is called. This "Display Dialog"-calls are neccessary for us (in sum there are 26 of them inside our MSICode, only 13 for each product should be shown). I tried to comment out the dialogs used for one product and build the other. This works, but i dont want to take care for two setups from now. A step backward to 2009 R2 is not the way we want go. How can i get rid of this and will this behavior be fixed in newer versiens of IA?

Greetings,
Martin

[MartinIW]

Hi there,
it looks like I fixed the problem for us. I implemented the feature from IA 10 with the dynamic pictures in dialogs, so we need only 13 dialogs complete now.
The reason why we copied all dialogs was that IA 2009 R2 doesnt support dynamically loading pictures into them. But I am a little afraid, that when 'someday' we need more than these 13 dialogs we will run into that problem with Windows 2003 Server again. It looks like there is a dialoglimit since we updated to IA 17. Maybe its because the UNICODE changes IA made since that version. That would explain why it works on older versions.
However, Im glad that I found a solution so far.

Merry christmas and a happy new year by the way
Martin

[FrancescoT]

Dear Martin,

many thanks for sharing this usefull information.

In reality the problem is caused by WIN XP OS ..., it is a legacy OS and some more recent features are not handled properly.

Regards and Merry Christmas!

[Aaron Young]

Well, we have made no further progress with replicating this issue in-house, however we are starting to see more and more of our customer base run into this problem.

Customers receiving this error are mostly on Windows Server 2003 and Windows XP, however we have had some instances on Vista and Window 7 and that is a concern.
To try and troubleshoot this, we created a new install using InstallAware 18 from scratch using the InstallAware Quick Start Wizard that delivers a simple executable (with no functional purpose.)

We then had one of our customers experiencing the error run this new installation and found they got the same error.
This install is attached (project and exe) and contains no custom add-ins, dialogs or resources.

Right now, we are having to create special builds for these customers using InstallAware 2012 and we may have to revert back to this version for ALL builds, but obviously we would prefer to remain on the latest version of the InstallAware product.

Regards,

- Aaron.

[FrancescoT]

I'll have a look to your project.

Regards

[MartinIW]

Hi there,
I also have bad news. We tried the new setup on our WTS 2003 in house and it works. Thats why I thought we had a solution for this problem.
But now we sent the new setup to our customer and on his WTS 2003 the error remains.
Is there any solution in view or should we move back to IA 15?

Greetings,
Martin

[Aaron Young]

I'll have a look to your project.

Regards

Francesco,

I was wondering if you had had any luck replicating the issue with the provided files?

Regards,

- Aaron.

[FrancescoT]

Dear Aron,

yes, I have tested your package but it worked always fine.

I tested your compressed exe with both WIN XP and WIN 2003.

Note, I even tried your package with a very first release of WIN XP OS (without any service pack installed) and it completed the installation correctly (see screen shot).

xp_install_result.png (236.03 KiB) Viewed 26258 times

Regards

[T.Dettmar]

Hello,

we have the exact same problem. Some facts:

1. We aren't able to reproduce the problem internally. It only occurs on some of our customers machines (Windows Server 2003/XP)

2. On some machines it could be solved by adding the IRPStackSize parameter to the registry as mentioned before. This doesn't work an all machines.

3. I can confirm that at least in one case it has to do with the dialogs:
a. I made a clean new setup with the IA 16-Quick Start-wizard containing 16 dialogs (standard theme) -> failed
b. I reduced the dialogs to 3 (startinstallation, progress and finish) by deactivating them in the design view -> works
c. I reduced the dialogs in our real world application from 12 to 5 (custom theme) -> still failing but the progress bar now nearly reaches the end before the error occurs

4. The problem occurs in the silent mode (/s) too and it is no solution to skip the dialogs with a "if variable goto label"-statement.

Of course it is no solution for us, to criple all of our setups. And it is no solution to go down to an older IA Version, because we updated due to problems with IIS-Installation.

So we need a real solution for this problem. And this very fast, our customer threatens with the lawyer...

Timo