IA17: Not enough storage to process: XP only

Postby **FrancescoT** » Wed Feb 05, 2014 12:36 pm

Dear Timo,

As I already discussed with you by email ... Unfortunately, there is not too much that we can do on IA side.

Regards

JoWag · Postby **JoWag** » Wed Feb 19, 2014 4:13 am

We have the same issue on a Windows XP and Windows 7 32-bit system.

Our current solution is to reduce the "Display Dialog:" calls from 33 to 28. But it's not a good solution. It would be nice to know whats the problem with the dialogs on a Windows 32-bit (it's not the memory or hdd space) and how we can fix it without dialog limitation.

I append a example project. If you cannot reproduce the error, add more "Display Dialog:" lines to the MSI code.

Postby **FrancescoT** » Thu Feb 20, 2014 9:03 am

Dear JoWang,

The sample you posted is not an appropriate way to conduct a test even if, the one you posted worked always fine with my verification.
You are only repeatedly calling "Display Dialog" in your script, with the sole scope to intentionally cause a system memory resource saturation.

Honestly I don't know which is your personal experience with developing, but what you are trying to demonstrate, It is the same that to allocate a buffer dynamically (repeatedly ) until the system memory get consumed and then ... the application crashes.

Unfortunately as I already said, there is not too much that we can do on IA side.

With OSes as WIN XP there are less system memory resources available ... and we can't change this fact.

Regards

JoWag · Postby **JoWag** » Fri Feb 21, 2014 1:12 am

Dear FrancescoT.

I try to demonstrate that it's a problem if you have a lot of dialog's to display in your setup (on a windows 32-bit system). Thats all. My problem is your error handling. Why it's not possible to show a error message that our client can understand if the setup cannot run on this system? And why a lot of this error messages so that our clients need to kill the setup with the task manager?

Regards, JoWag

Postby **FrancescoT** » Fri Feb 21, 2014 12:15 pm

Dear JoWag,

I am very sorry, but I really don't understand which sort of more detailed error message you would like to receive from the installer.

The error message; "Not enough storage to process xxxx" is an OS error message and its meaning I suppose is enough clear.
This error state can be returned in any circumstances where this system condition are meet and this "Conditions", are not limited to a specific OS or Platform. This error state can be returned by any OS version ... IF SYSTEM RESOURCES ARE NOT ENOUGH TO SATISFY THE PROCESS REQUEST.

Unfortunately and due the mode used by legacy OS as WIN XP to handle the system memory, this specific error state has much more opportunities to be triggered.

Finally, if you search over internet for "Not enough storage to process win xp", you will find how it is popular and annoying, this specific issue with WIN XP.

Regards

AH-NP · Postby **AH-NP** » Mon Feb 24, 2014 4:32 am

Hi,
We have the same problem with windows 2003 R2, 4 Gb RAM… (2.5 Gb free when we encountered the issue)…
Don’t have any problem with the same setup on another PC, windows 2003 R2, 2 Gb RAM, 800 Mo free when we made the test.
So what can we do, everything worked fine with IA9R2…
Windows sever 2003 ends of life is for July 2015, not before…
Can you please make more test and try to resolve this issue?
I understand that this is a difficult error to reproduce for you, but we need :
- A workaround for this (how our customers can install our products, what can we say to help us ?)
- A resolution in a future release.
Regards
AH-NP

Postby **FrancescoT** » Tue Feb 25, 2014 3:52 am

Dear AH-NP,

do you really belive that we have not executed enough verification in house about this specific matter?

Unfortunately, I can't tell you anything more of what I've already said with my previous answers.

Regards

MartinIW · Postby **MartinIW** » Fri Feb 28, 2014 2:53 am

Hi there,
what we did in this case is not a very clean solution, but for us it works.
Our normal setups are compiled in IA17 now. But we set up an virtual mashine with the old IA9R2 to creat a setup for each version when our customers are reporting problems on their Win2003/XP mashines. For our 2 products this means we have to create 4 setups so far.
For us it works this way but i think IA changed something that causes now the moemory-problems. In my opinion it must be the change in UNICODE that came up with IA17 that causes this problems.

By the way Windows 2003 supports ends in 2015 but this may not stop customers from working with it.
Its not recomended and you will not get any security-updates or patches any longer. but who cares if there is a windows2003 server running in a company in a private network?

I hope this will help someone to workaround this error like we do.

Greetings,
Martin

Postby **FrancescoT** » Fri Feb 28, 2014 12:39 pm

Dear Martin,

......For us it works this way but i think IA changed something that causes now the moemory-problems. In my opinion it must be the change in UNICODE that came up with IA17 that causes this problems.

If you have a look at my previous reply; Mon Nov 25, 2013 7:14 pm ... I have already aswered to your assumption.

Regards

MartinIW · Postby **MartinIW** » Tue Mar 04, 2014 2:35 am

Sorry Francesco,
but are you supporting XP and Windows 2003 or not?
"...some more recent features are not handled properly" is not what i would expect if a bug like this is cumming up.
Its not only a label showing something wrong. We talk about our customers are no longer able to install our products!?
Is someone doing something against this "not properly working features"?
Sorry but for me it looks like you want to sit it out and wait for XP/2003-support to end.

AH-NP · Postby **AH-NP** » Mon Mar 10, 2014 10:15 am

Hello,

All of our customers who have the problem have the Terminal Server role activated on their windows server 2003.
So we have reproduced the problem at office by enabling this role.
The problem occurs with the sample setup generated by Installaware Project wizard, without any changes.
If we uninstall the role, the setup works without any issue…
Can you please try to reproduce the issue using this configuration ?

Thanks

AH-NP

Postby **FrancescoT** » Mon Mar 10, 2014 12:02 pm

Dear AH-NP,

let me try.

Regards

bluish · Postby **bluish** » Fri Mar 14, 2014 3:51 am

AH-NP's solution worked for us!

I removed the Terminal Server role from our Windows Server 2003
restarted
launched again the installer that had the problem, which successfully installed the program we neeeded
added again the Terminal Server role
after the restart I only needed to configure again the Terminal Server to use the correct Terminal Server License Server (the same machine for us)

Hope it can help someone.

Maybe a better solution could be to simply stop the Terminal Server service, but I've not tested it.

AH-NP · Postby **AH-NP** » Mon Mar 17, 2014 10:25 am

Hi Francesco,

Have you had time to watch this ?

Regards

AH-NP

AH-NP · Postby **AH-NP** » Mon Mar 24, 2014 4:38 am

hi Francesco,

Can you please give me feedback on this issue ?
We need to now what we should do for our futures release, this is impossible for us to keep 2 versions of Installaware (IA18 for Win 7 and Win 8 and IA9R2 for XP and windows 2003...).

Regards

AH-NP