Page 1 of 1

One-off install failure

Posted: Wed Nov 15, 2006 6:15 am
by IanM
One of my users is having problems with the install failing on one particular PC. We have tried various copies of the install.exe but the problem persists. The same install has worked on thousands of other sites.

The error log shows errors 1708 and 1709 (unhelpful) but this appears to be where the failure occurs:

MSI (s) (40:04) [10:08:36:810]: Doing action: ACTEZ
MSI (s) (40:04) [10:08:36:860]: Note: 1: 2205 2: 3: ActionText
Action start 10:08:36: ACTEZ.MSI (s) (40:04) [10:08:37:060]: Creating MSIHANDLE (4) of type 790542 for thread 772
MSI (s) (40:7C) [10:08:37:120]: Invoking remote custom action. DLL: C:\\WINNT\\Installer\\MSI35.tmp, Entrypoint: ActProc
MSI (s) (40:7C) [10:08:37:290]: Closing MSIHANDLE (4) of type 790542 for thread 772
Action ended 10:08:37: ACTEZ. Return value 3.
Action ended 10:08:37: INSTALL. Return value 3.

Any clues?

Ian

Posted: Wed Nov 15, 2006 8:25 am
by MichaelNesmith
Not without knowing more, sorry.

Re: One-off install failure

Posted: Fri May 15, 2009 1:17 am
by ericgentry
IanM wrote:One of my users is having problems with the install failing on one particular PC. We have tried various copies of the install.exe but the problem persists. The same install has worked on thousands of other sites.

The error log shows errors 1708 and 1709 (unhelpful) but this appears to be where the failure occurs:

MSI (s) (40:04) [10:08:36:810]: Doing action: ACTEZ
MSI (s) (40:04) [10:08:36:860]: Note: 1: 2205 2: 3: ActionText
Action start 10:08:36: ACTEZ.MSI (s) (40:04) [10:08:37:060]: Creating MSIHANDLE (4) of type 790542 for thread 772
MSI (s) (40:7C) [10:08:37:120]: Invoking remote custom action. DLL: C:\\WINNT\\Installer\\MSI35.tmp, Entrypoint: ActProc
MSI (s) (40:7C) [10:08:37:290]: Closing MSIHANDLE (4) of type 790542 for thread 772
Action ended 10:08:37: ACTEZ. Return value 3.
Action ended 10:08:37: INSTALL. Return value 3.

Any clues?

Ian
I have found this, too. I know why it is happening, but I don't know how InstallAware is involved. The reason this happens is that the MSI that InstallAware creates does not contain an ActionText table.

I am trying to figure it out, and will post again if I find the reason InstallAware intentionally removes this table.

Posted: Sun May 17, 2009 7:44 pm
by MichaelNesmith
It has nothing to do with the ActionText table text...which is removed, by the way, so you don't have to manually translate your MSI database messages - and instead Windows Installer's built-in translations are used.

An InstallAware pre-defined and compulsory custom action is failing, this would happen only if %TMP% is undefined or ill-defined. Check to see if that is your circumstance?