Page 4 of 4
Re: IA17: Not enough storage to process: XP only
Posted: Mon Mar 24, 2014 9:46 am
by FrancescoT
Dear AH-NP,
I tried what you reported with installing the Terminal Server role and I can replicate the same as well.
However, this doesn't demonstrate any direct relation of the problem with the Terminal Server role specifically.
Instead, it is directly related to the effective system resources available once the Terminal Server is installed and then running.
Currently I can only confirm when this problem occurs, it is caused by "low system resources" available with those OSes.
I can also confirm, that we are investigating if exist anything that we can do on InstallAware side.
At the same time, I can't give you any foresight or assurance, that we'll be able make this possible.
Regards
Re: IA17: Not enough storage to process: XP only
Posted: Thu Mar 27, 2014 7:08 am
by AH-NP
Hi Francesco,
The example with TSE role is the only way I found to always replicate the issue, with a simple project.
I agree that this is related to system resources and not to TSE role
My problem is that I can’t keep the two versions of Installaware in my build process.
We’ve just buy the upgrade (we didn’t have maintenance free upgrade) for IA18 so if we can’t build all our products for all our customers with IA18, we will come back in IA9 and request for a refund of IA18 product (and I am sorry about that, I’d rather use IA18 which have more functionality…)
Regards,
AH-NP
Re: IA17: Not enough storage to process: XP only
Posted: Thu Jun 05, 2014 11:06 am
by FrancescoT
Dear Users,
just to inform that the latest IA update (18.07) available includes a fix that should solve this problem.
Regards
Re: IA17: Not enough storage to process: XP only
Posted: Thu Nov 20, 2014 6:34 am
by stevepro
Unfortunately we just spent two days upgrading from IA 15 to IA 18.8 and have discovered the problem is not resolved. We are now rolling back to 15 as many of our clients use XP and Win 2003 and they won't be upgrading anytime soon.

Re: IA17: Not enough storage to process: XP only
Posted: Thu Nov 20, 2014 9:49 am
by FrancescoT
Dear Steve,
honestly, it's very strange what you are reporting.
Did you use a correct license file to activate IA 18.08?
Regards
Re: IA17: Not enough storage to process: XP only
Posted: Tue Dec 02, 2014 9:44 am
by AH-NP
Hi,
I can confirm that since 18.08 release, the problem is solved !
Regards
AH-NP
Re: IA17: Not enough storage to process: XP only
Posted: Tue Dec 02, 2014 1:17 pm
by FrancescoT
Re: IA17: Not enough storage to process: XP only
Posted: Tue Dec 02, 2014 4:21 pm
by sjziegler
How do I determine which build I am running?
Re: IA17: Not enough storage to process: XP only
Posted: Wed Dec 03, 2014 12:02 pm
by FrancescoT
Dear Sjziegler,
- click the "Version" button from the main ribbon menu (IA IDE Project view) for the BUILD version.
- The product version is listed under Add Remove Program.
Hope this helps you.
Regards
Re: IA17: Not enough storage to process: XP only
Posted: Wed Dec 03, 2014 1:52 pm
by sjziegler
I am running 18.05, so I guess I will download the latest one.
Re: IA17: Not enough storage to process: XP only
Posted: Tue May 19, 2015 11:10 am
by NHSRuss
We're running IA17 and experiencing this same error and have a client unable to proceed with an update of our software. We need to get this client updated in short order and was hoping to get some details on what the fix was so we can try to work around the problem until we're able to update to 18.
We've had a number of successful installs at other client sites and internally without the error so clearly there is something environmental contributing to the problem, as the error message would also lead you to believe, but it does not appears to be as simple as available disk space or RAM. Can you elaborate on what you found to be the source of the issue so we might work with the client to help them expand their currently limiting resource and get past this issue?
Regards,
Russ Horton
Re: IA17: Not enough storage to process: XP only
Posted: Tue May 19, 2015 1:36 pm
by FrancescoT
Dear Russ,
unfortunately, I don't believe there isn't anything that you can do or to work on.
If the problem you are having is exactly the same of the one described with this thread, you may try to "temporarily" disable or remove the TSE role ... but before to proceed consult the Microsoft documentation for any possible downside.
Of course the one above is not a solution or either an effective workaround.
Hope this helps you.
Regards