Obviously the timestamp and MSI temp file names vary.Action start 18:47:07: AI_AuthorSinglePackage.
MSI (c) (58:B8) [18:47:07:533]: Invoking remote custom action. DLL: C:\Users\Adam\AppData\Local\Temp\MSI650A.tmp, Entrypoint: AI_AuthorSinglePackage
Action ended 18:47:07: AI_AuthorSinglePackage. Return value 3.
I can easily reproduce the behaviour by first selecting a per user install, then going back and selecting a per machine installation, or visa versa. Some times it happens on the initial setting of Per Machine or Per User, sometimes I have to alternate a few times between them.
I'm using the InstallTypeDlg:
- I set AI_InstallPerUser to 0 in the Init events.
- I set a public property IS_PER_USER to the value of AI_InstallPerUser when clicking Next
- I show the FolderDlg when clicking Next
I cannot determine a root cause, but it seems to be with that AI_AuthorSinglePackage custom action.
I can reproduce with the 'Installation UI' button or by running the actual installation MSI.
I can e-mail logs and a sample .aip to support if necessary.
EDIT The bad memory reference occurs when attempting to view the log via the UI after a crash.
FOLLOW US
Get the latest news in Application Packaging