Failing with a bad memory reference - Advanced Installer Community
adamdc78
Posts: 76
Joined: Wed Mar 19, 2014 7:42 pm

Failing with a bad memory reference

I've been seeing a lot of MSI logs similar to the following lately:
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.
Obviously the timestamp and MSI temp file names vary.

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.
Attachments
The error message.
The error message.
MSIError.jpg (15.33 KiB) Viewed 3668 times
Last edited by adamdc78 on Thu Jul 16, 2015 7:32 pm, edited 3 times in total.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Failing with a bad memory references

Hello,

Yes, please please send us an .AIP (project file) and a verbose log of the installation to support at advancedinstaller dot com so we can investigate and test the scenario on our side.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Failing with a bad memory reference

Hello Adam,

We have tested the scenario and replicated the behavior. This seems to be caused by an Advanced Installer issue. A fix will be available in a future version of Advanced Installer, thank you for bringing it to our attention. We will notify you when the fix will be out.

Until then, I'm afraid there is no workaround unless you are willing to change the installation type to a different option than "Per-machine if user is administrator, per -user otherwise".

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”