I am currently getting the following error when running my setup.msi file containing a single compressed executable: "Runtime error in install: List index out of bounds. (76)"
When I run the uncompressed debug version it installs without a problem.
Has anyone encountered this problem?
Can someone who is willing to look at my MSI code please be so kind as to compile it and see if they get the same error?
I'm running InstallAware admin Studio version 6.24 SP4.02
Runtime error in install: List index out of bounds. (76)
I ran into a simliar problem (slightly different error message) a while back. The error I got was because I upgraded InstallAware to a new version, but then used the old registration exe.
You can check this by looking up the version on the Help menu > About. If you used an old registration exe it'll show an older version. New registration executables are available in the customer area.
You can check this by looking up the version on the Help menu > About. If you used an old registration exe it'll show an older version. New registration executables are available in the customer area.
I've also fighted with this problem - the reason was unmached if/else/end in long and complicated script with many includes (lack of procedures and functions forced me to such tricks). The compilation does not signal any syntax error, build was successful and installer was starting and executing up to this bad place (line 5547). But how to find this line with several levels of includes? PLEASE extend IA 'find' with simple 'go to line'..... and possibility to view final script (with all includes inserted to main script)
Jarek
Jarek
same here
Hello,
We encountered the same kind of error. With the size of our script it took much time to figure out which if was not ok. Turned out to be a compiler if /end that was mingled at the wrong level with regular if statements.
Is there a possibility to catch those at compile time?
We encountered the same kind of error. With the size of our script it took much time to figure out which if was not ok. Turned out to be a compiler if /end that was mingled at the wrong level with regular if statements.
Is there a possibility to catch those at compile time?
Who is online
Users browsing this forum: No registered users and 120 guests