Page 1 of 1

Access violation in IA8 signing package with Authenticode

Posted: Fri Aug 07, 2009 4:54 am
by Geocentrix
I am consistently getting the following message:

Access violation at address 004E9B7D in module 'miae.exe'. Read of address 00000010

in a handful of projects in one or two places in the build process:

1) Immediately after 'Creating Windows Installer database' (or)
2) Immediately after 'Prepared SFX data'

which are the steps where InstallAware signs the package with Authenticode.

Once the error has occurred, all subsequent builds also fail (usually at place 1), until I reboot my PC.

I am using Build 'Ame - Rej.thm.080808'

Has anyone else come across this problem and found a reliable solution, please?

Andrew

Access violation in IA8 signing package with Authenticode

Posted: Fri Aug 07, 2009 5:34 am
by Geocentrix
I have found a solution - turn off my anti-virus program (actually, suspend it for the duration).

I am using Kaspersky Internet Security 8.0.0.506 ... but it makes no complaint about running InstallAware. When K is turned off, the problem disappears completely.

Is this a known bug in IA8?

Andrew

Posted: Fri Aug 07, 2009 9:19 am
by MichaelNesmith
I would hardly call this a bug with InstallAware, if it happens only when Kaspersky is running. Please contact Kaspersky so they can fix THEIR bug for you.

Posted: Fri Aug 07, 2009 11:39 am
by Geocentrix
Michael

The tone of your response is rather dismissive. It could be a bug in either program - you are rather too quick to blame Kaspersky. It may be that Kaspersky merely uncovers a bug in IA8.

A better response would have been to say 'thanks for pointing this out, glad you've found a workaround, we'll look into it and provide a more robust solution going forward'.

Regardless of whose bug it is, I would expect InstallAware to fail more gracefully than suffering an access violation. And I would expect IA to work properly while a very common anti-virus program is running.

Since the problem only manifests itself in IA, my perception is that it is a bug in IA.

Andrew

Posted: Fri Aug 07, 2009 4:53 pm
by MichaelNesmith
Unfortunately we simply don't have the resources to work around bugs in thousands of third party software.