Identifying an error line

Got a problem you cannot solve? Try here.
matthewj
Posts: 66
Joined: Tue Dec 07, 2004 12:48 pm

Identifying an error line

Postby matthewj » Mon Oct 09, 2006 2:36 pm

How can I identify the exact line of an error message? If I build my installer in the IDE, it runs properly on my VMWare test machine. If I build it from my FinalBuilder script, then it is failing with an error message:

Code: Select all

Runtime error in setup script:
Line 74: List index out of bounds (73)

Now, this is quite interesting because I've been looking at the script and commenting a few lines out, and the error initially was on line 64 with a 63 in parenthesis. Anyway, I only include the msi20 install scripts, but can't work out why it might be failing at all. I tried an uncompressed install in the hope I might be able to see the text, but that didn't work.

I've tried turning on logging, but it obviously fails before that starts.

This is a script that has been in use for a while, but now stopped working. I just upgraded to 6.03 due to another issue I thought maybe fixed.

I've spent a few hours trying to work out why this might be happening, but can't. Is there anything changed in 6.03 that might be causing this behaviour? I wondered if a dialog might be the cause.

Thanks,

Matthew

MichaelNesmith
Posts: 3452
Joined: Thu Dec 22, 2005 7:17 pm
Contact:

Postby MichaelNesmith » Mon Oct 09, 2006 4:10 pm

Hi Matt,

I think FinalBuilder might be updating the MPR project file directly during its build process. To check if this is the case, try to build from the command line using miabuild.exe, and also specify the /r parameter to regenerate a new revision code.

See if that works. If it does, then the problem might be with the FinalBuilder action. In this case just call miabuild.exe directly from the command line using FinalBuilder, instead of using its built-in action.

If not, let us know!
Michael Nesmith
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/

matthewj
Posts: 66
Joined: Tue Dec 07, 2004 12:48 pm

Postby matthewj » Tue Oct 10, 2006 6:44 am

Just to close this off, I was using an old license application installer, and that seems to have been the cause. Obviously something was incompatible somewhere. Perhaps this will help some other person who falls over this later!

Matthew


Return to “Technical Support”

Who is online

Users browsing this forum: No registered users and 48 guests