mdm
5th November 2003 16:24 UTC

installer hangs up and install.log not written
deploying on many servers. some hang up and process doesn't end. since install.log not written until installer finishes, we can't tell how far the installer got.

is there some way to put time limit on whole install process or each ExecWait call so installer will proceed in any case?

mdm

Joost Verburg
5th November 2003 16:35 UTC

So you execute a process that does not finish? You can put a message box before each ExecWait call or terminate the process using the Task Manager.

mdm
5th November 2003 17:02 UTC

yes, one of the exec calls does not finish. not sure which one. this is a silent install...unattended.
I was thinkiing that I could change all the ExecWait calls for Exec a nd Sleep(some time value)..a little sloppy, but it seems like the installer would proceed either way and take longer too. This is not my favorite soln, suggestions are welcome.
Another thing is that install.log works fine if I hit an Abort or finish properly...the log doesn't write if I hang up tho. So solution to the hanging problem would also solve the install.log problem.

thanks,
mdm

Joost Verburg
5th November 2003 17:32 UTC

Is it impossible to solve this hanging problem in the process? You can run it once with some message boxes to find out which process causes the problem.

kichik
5th November 2003 19:57 UTC

install.log is written as the installer goes. It is not flushed, but is written. If you open the log and see nothing, it's probably still waiting in Windows' cache. It should be written once you terminate the installer, and will surely not contain anything that comes after the hanging execution.