IDriver.exe: hangs on NT when removing backup files?
Standard project, 7.02.
We are having problems with IDriver.EXE hanging at the end of an install on Windows NT4.
There seems to be issuing with cleaning up temporary files - The task monitor indicates that MSIExec is taking 50% of the machine's CPU but the "removing backup files" prompt is never removed.
This problem doesn't seem to happen on Windows 2000 or XP.
Can you reproduce this with any other projects on Windows NT 4 machines? If so, I can test this further.
If you can't reproduce with other projects, I'd recommend building a new Release with new Release name of your current project. Does the same behavior occur?
In this case, MSI engine hangs for some reason. Check the log to see where it chokes.
I notice similar behavior from MSI2.0 (Not at the same place), it hangs for quite a well (a couple of minutes) before it starts to move.
I have also experienced this. I am
using InstallShield 7.04, Install ran on Windows XP machine.
The message box says
"Removing backup files"
This happens after OnFirstUIBefore()
I do not enter OnFirstUIAfter().
I talked to the support but they wanted
a log. Since this was not reproducible
they do not want to consider it as a bug.
If any one knows the reason or solution
please drop a line.
same thing happening to me
I get the same problem. I don't know exactly when it's occurring, but here is my config:
(Also happens on DevStudio 9)
Windows 2000 SP 4 w/all critical updates (build and install machines)
(Also happens on plain 2000 and 2000 SP 3)
msiexec.exe takes all the CPU time. Killing the InstallShield task yields an IDriver.exe not responding window.
This reproduces all the time. I've been in contact with Support about this for a few days.
Here are some interesting tidbits:
- this takes much longer when booting with /numproc=1. Not time-wise, but it happens much less frequently. (A cyclical install/uninstall test took 12 hours uniproc where it was failing at 7-20 minutes before on a dual proc)
- issuing a 'net stop msiserver' between each step in the install/uninstall test does not help at all -- so it's probably not a continual memory leak of msiexec.exe.