Check our other helpful areas that might answer your question

Hi,

I have created an installer package with a number of deferred custom actions that are set to run in the execute sequence from 6401 to 6408. These custom actions are all of type 1174 (Deferred asynchronous, wait for return code, vbscript). When it is run on Win 2000 (SP3) or Win XP the installation runs fine and all of the actions are called correctly. However, when running on Win 2003 Server, the first action is called and returns correctly but then the rest are skipped.

There is no evidence in the installer log file (created using msiexec /i installfile.msi /l*v mylog.log) to suggest why they were skipped. They just don't appear.

I have inserted an inline popup at sequence 6601 which is calledby the script suggesting that it hasn't crashed.

Has anyone experienced this problem before and, if so, is there a fix?

Many thanks,

Anthony