Microsoft Report Viewer Redist Crash

[tiger9091]

I am using Installaware Studio Admin. We have a working install for a .NET 2.0 application. We just added reporting to the app, and I added the Microsoft Report Viewer redistributable. The Report Viewer installation is crashing on a couple of our test machines, but not all. I am confident this is Microsoft's crash, not an Installaware problem, but we are trying to script a workaround into Installaware.

What we have noticed is that when the Report Viewer installation crashes, immediately rebooting and restarting the installation allows the installation to proceed without issue. However, when I added a Reboot and Resume Setup option to the setuprepview include script, it did not resume the setup. What I am trying to do is simply require a reboot when the install detects that the Report Viewer redist needs to be installed, then resume the setup. If anyone has any other ideas, i would appreciate the help.

Thanks,

Tiger9091

[MichaelNesmith]

Hi Tiger9091!

When you say Reboot and Resume does not work, do you have any details? This function should work with single file, web based, and uncompressed installers, as long as the directory from which setup is running remains accessible immediately after reboot, and the setup file can be read.

Note that Reboot and Resume simply restarts your setup. It does not resume execution from where it last left off in your setup script, in case that was your intention.

[tiger9091]

The Resume portion of the 'Reboot and Resume' did not work. It did reboot the machine, but the install never restarted. I was running it from a mapped drive. I am using VMWare for the test and have only Windows XP on the VM. However, what I was trying to do was get it to resume beyond the reboot point in the script. Based on your explanation, it makes sense that idea will not work.

Any other ideas about forcing the reboot and then continuing the setup without re-executing the reboot each time? I assume a registry write would require an Apply Install, and the Pre-reqs are very early in the script.

[MichaelNesmith]

Hi Tiger!

Reboot and Resume actually works well with prereqs, because previously installed prereqs won't be reinstalled, and the installation will either install the next prereq in line, or move to the main installation phase. So either way, it will be as if setup is indeed resuming from exactly where it left off.

I think the problem is the mapped drive. It may be that the drive mapping is not yet active (especially if VMware tools must be loaded beforehand for it) when the system tries to run the setup again. You can copy the setup to, for example, the VMware machine's destop, and try running it from there. You will see Reboot and Resume works just fine.

[tiger9091]

Thanks for the info, I will try that.