Is the VBScript still in there? Does it still reference the correct references in the directory table? (Repeated edits can create additional directory table entries such as INSTALLDIR1, INSTALLDIR2, etc. You need to make sure that the coding in the VBScript is still correct for your updated WSI project.

If all is well with the script, is it still running in the right place? You could add in a line such as

msgbox "I'm running" and this message should pop up on the screen when the vbscript runs.

AngelD is off skiing at the moment, so you will have to either reference the previous thread or let us know in more detail what he gave you and what you are doing. Otherwise, I think he's back next week.

Hi EdT,

Thanks for the response. The VBscript is still there in an external file and it still points to it correctly within the Execute Immediate and Execute deferred MSI script.

When you saud additional table entries, where do you find where these are defined e.g. INSTALLDIR1, INSTALLDIR2 etc? It maybe that it's incremented from INSTALLDIR to INSTALLDIR1 or something. It's worth a look anyway.



Thanks,

Gareth

For the record, INSTALLDIR, INSTALLDIR1, etc, are all references to Directory Table entries. However, as you have sorted your own problem, I will lock this thread.