InstallAware

Just started getting this error...List Index out of bounds (1485)...out of the blue. Happens with all projects when I start to do a build. Hit build again and it works....

List Index out of bounds (1485)

I'm having the same problem while trying to open my project in IA, and this is preventing me from opening my project:

List index out of bounds (1)

And since this was not the first time this happens, I suppose this is some sort of IA bug. Is there any specific reason for this error to keep happening from time to time? How can I avoid it? Can I fix this project error in some sort of way or should I start my project from scratch once again?

Thanks in advance.

At present there is no fix for this I'm afraid, as you are right in assuming that it indicates an unrecoverable corruption of one, or more, script files.

However, we are constantly looking to improve our error handling on this front - please submit any scripts that fail via our support system (please remove all DLL's, EXEs, etc from the archive in order to keep size down!).

Hi there, Neillans!

Should I send it through forum or e-mail?

Thank you very much!

Please submit it via our support system at http://support.installaware.com.

Actually I solved this a long time ago. Can't remember exactly what I did now, but seem to think that it had something to do with canceling a build and then trying it again. But what I do now days before any build I am going test thoroughly or post, the first thing I do is delate all temp files, reboot and then build.

Haven't seen the problem since.

Actually I solved this a long time ago. Can't remember exactly what I did now, but seem to think that it had something to do with canceling a build and then trying it again. But what I do now days before any build I am going test thoroughly or post, the first thing I do is delate all temp files, reboot and then build.

Haven't seen the problem since.

Hi

Neillans, I'm not being able to register for the Support Center...

SteveDude, I have tried to what you suggested -- clean the Release folder and temp files (*.BAK, *.DLL, *.TXT) and reboot before trying again -- but IA still doesn't open my project. I have detected that replacing the current .MIA file with an older version, made IA able to open the project again.

But in this case, you know, a few days of features implementation will be lost.
Any other suggestions?

Thanks for the help!

What error are you getting registering with the support system ? Would help to diagnose the problem and help further ....

Hi Neillans,

Sorry for not providing enough information... Actually, I'm not receiving the confirmation mail after I register. I have already tried to use an alternative mail address and checked my "spam" folder on both of them, but found nothing.

Is there any other way to confirm my registration or something?

Thank you very much!

I have validated both of the accounts.

I have already opened a new ticket for that matter.
I hope you guys can find a solution for my problem and improve the handling of corrupted script errors.

Thank you very much, Neillans.

Tiago,

Finally remembered after installing v9 on a new box. Had a similar problem, just not opening old projects, but during build.

When I first posted this, the problem was actually with a third party plug-in and simply updating the plug-in solved the problem.

...in any case that was it for me.

From my experience I find it unusual to have so many problems with as the software has improved greatly and since the later builds of v7 can't really name one problem I have that wasn't related to a plug-in or my own coding issues...except for a persistent annoyance of 20MB+ single file installs having the initialization dialog disappear for several seconds before showing the first dialog on Windows Vista. That's been around since I have had IA.

Hi Steve,

Thanks for your positive comments

Your feedback is interesting too ... I'll make a note and investigate to see if we can enhance the logging information from the compiler to give more state information about plugin triggered errors, as well as improve the initial form apperance on large installs.