Setup stands at 100%

[grisu1976]

Hi,

has anyone experienced this:

Sometimes my setup stands at 100%, the msiexec still works, but won't come to an end. What is the problem?

thanks,
Carsten

[Joshua]

Carsten,

If you leave the setup to run, will it eventually end? Or does it hang permanently? I would suggest logging your install to determine where and why it's hanging. Perhaps you simply have alot of self-registering files, and this is the place during the install where this registration takes place. Just a suggestion.

Hope this helps!

[grisu1976]

Hi,

I have logging of my setup always enabled. But I see nothing extraordinary. If my setup hangs (it does only seldom hang), it hangs at 100%, sometimes when it deletes its temporary files or something like that. The log file sometimes looks like a log file from a completed setup.

The things that I do per InstallScript are all logged and I see in the log file, that they are finished...

Thanks anyway...

[Jennifer]

Does it hang on all operating systems?

[grisu1976]

No, just on Windows NT 4 SP6. And it does not hang on every setup. On Windows 2000 occured a hang after reboot of my setup.

I've installed now the Hotfix for ISD 7.04, could that help?

thanks,
Carsten

[alatten]

Hi Carsten,

as far as I know, one of the things fixed by the Hotfix is related to crashes on NT4.0SP6 machines. But I'm not sure anymore which kind of projects was affected by this problem. However, I think applying it is a good idea.

Andrees

[grisu1976]

hi !

It seems that the hotfix does not work either. But the "hang" of my setup is not reproducible, it only happens sometimes (on the same disk-image).

[BigAlbert]

Hi there ::

As far as I know every time I had such kind of problem it was becuse of the self-register component - the CA that responseble for this is the last one in the execute sequense this why you can see that in the progress bar the Installation is finished but the computer is in the "dead - lock".

try this::
1) save the current version of your .ism file.
2) delete all the "self-register" component from your project.
3) close your project and reopen it.
4) recompile the project.

try the installtion now and see if its ends if so then this is the problem you have to narrow down your option's which is the "naoty" com object that responsebole for this.

try to see if by mistake you havent mark it as "self-register" component and "Key-File" at the same time.

[BigAlbert]

Hi there ::

As far as I know every time I had such kind of problem it was becuse of the self-register component - the CA that responseble for this is the last one in the execute sequense this why you can see that in the progress bar the Installation is finished but the computer is in the "dead - lock".

try this::
1) save the current version of your .ism file.
2) delete all the "self-register" component from your project.
3) close your project and reopen it.
4) recompile the project.

try the installtion now and see if its ends if so then this is the problem you have to narrow down your option's which is the "naoty" com object that responsebole for this.

try to see if by mistake you havent mark it as "self-register" component and "Key-File" at the same time.

[chunqin]

Hi BigAlbert,

My uninstallation sometimes hang at "Removing backup files..." where the progress bar is at about 100%. I could not figure out the reason, and came across your comment above. I have two dlls that I check "Self register", and I'm wondering they are causing the hang like you said.

How can I find out if it is really these self register dlls that are causing the hang? And if it is, what should I do to fix the problem?

Btw, my setup is InstallScript msi project, and I'm using developer 8.

Please help. Thanks a lot!
:(

[BigAlbert]

chunqin :

As I wrote in thread it sound's like 'vudu' ...

-- The easyest way to know if they are causing the problems are to delete the from the project and to test if the problem is beeing solved or not - that's the way I found the answer , it toulk me hours but I think that there is no other way .

other than that I know that they are other reasons such as the 'Microsoft version 2.0 help files merge modules' - these can cause a hang uf about 5 minutes.