Runtime error in setup script

[scott]

One of our QA guys who runs a new setup nearly every day started getting a error message box that appears approximately halfway through the installation of our product. The message states the following:

Runtime error in setup script:
Line 247: Unable to create directory

While just hacking around on his machine to see what's going on we managed to find that it worked if he did not use the install for all users option at the beginning, and instead installed it only for the current user. I forget how but we saw it trying to use an invalid path at C:\\Application Data\\<guid>... folder, so apparently InstallAware is picking up a bad "All Users Application Data" folder on his system.

Firstly, any thoughts on how to correct this? While he's able to use the workaround of "Current User Only" for now, I'd like to solve this.

More importantly, how do we troubleshoot such errors? What does "Line 247" mean? Line 247 in what file? The "setup script" for InstallAware appears to be many files. Also, is there a log file created on the users machine when they run InstallAware to help us troubleshoot such problems?

Thanks in advance for your assistance.

[MichaelNesmith]

Hi Scott

I am not sure why your QA guy got that error...its certainly out of the ordinary, but we'll need detailed information to troubleshoot it.

Line 247 refers to the execution point that the error occured, I am guessing this might be where Apply Install is called. The line number is the number of the line in the main script, after the include scripts have been merged.

[scott]

I am happy to provide detailed information, but as I mentioned in my first post, I am not sure how to troubleshoot such an error and I am very interested in learning. So please help me understand what information to provide so we can troubleshoot this.

Also is there an install log created when the installer is running? Is there a way to create one?

[MichaelNesmith]

I'll ask the PM what sort of information might be helpful. In the meantime you can try to reproduce this issue on other computers and try to find what's common on the ones that experience this problem.