InstallAware

After reinstalling InstallAware 5.31 and reopening my project I get this error during build:

Error during build: Access violation at address 00000000. Read of address 00000000

This happens after all files are copied. It's not clear to me what is cousing this access violation...

Greetings
Frans.

Did you reboot the system after installation? Maybe a DLL got replaced during setup and a reboot is needed to complete the upgrade.

Yep I did reboot. Even now after a few days (reboots) the problem persists...

I solved the problem

WhenI de-installed the old version also the mdTools (for a MSDE 2000 installation) where de-installed. And My project still tried to use it...

Reinstalling the mdTools solved the problem...

Thanks anyway for your time!

That's interesting. You did not get an error when you loaded your project? The IDE warns of missing plug-ins when you load a related script, so I am surprised.

I had the same problem. I included MDAC 2.8 SP1 (was not installed with IA) and try to build setup. In build progress screen I got the message: Error during build: Access violation at address 00000000...
After adding the MDAC feature to my IA9 R2 SP3 installation it works.

I'm using IA9 r2 evaluation copy on Windows Vista machine and am seeing "Error during build: Access violation at address 00000000. Read of address 00000000" for a project that compiles without error using InstallAware Express (version 7?). The Example User Feedback IA 9 r2 project compiles without error on my machine so I presume that IA installed correctly. The build is for the application that I was thinking of buying IA 9 for use on. Any ideas? The only message preceding the error indicates "Cleared output folder ...". I tried including MDAC Refresh 2.8 in the build but this had no effect.

IAUser,

Do you have any patch references to sources that don't exist or are referring to IA 7 builds?

You may need to try uninstalling an reinstalling InstallAware. This has fixed this error for some...

I see no patch references in the project. I tried reinstalling my demo install of InstallAware and was told that my installation password is now invalid.

Could it still be some Application Runtime that is not being satisfied? If so is there a way of knowing which one(s) is(are) missing?

Thanks for your suggestions.

I dicovered strange behaviour while trying to reproduce this problem. I have a project and built it. Then I added a not installed Runtime (for instance .NET 1.1 with SP1). Klick on build single file => IA tells me that the runtime is not installed and the an other error message appears: "Unable to find save script records for". After that the project is not loaded any more and I am in a blank project...

What do you mean by "Then I added a not installed Runtime"?

I mean that I selected a runtime (to add it to my project) that was not installed locally. To check if the mentioned error message appears. Now clear?
Maybe you can try this at home/office to see what I mean.

Sorry to anger you, but you still haven't provided any clear steps on how to produce the "unable to find saved script context for" and then a blank project. This also doesn't appear related to the Access violation, so if you want this looked at, I think it will be best to start a new thread, otherwise please stay on topic.

I need clear steps like:

Click this.
Delete this.
Build setup.

Notice results.

Sorry, I opened a new thread because as you said this has nothing to do with this thread, I just encountered the error by trying to reproduce the error in this thread here.
So please follow my problem up here:
http://installaware.com/forum/viewtopic.php?f=2&t=5932

OK, so I think you were on the right track in trying to reproduce this.

By following the instructions you posted for the Unable to find saved script context for issue, I was able to reproduce this Access violation by:

Going to [installpath]\InstallAware\InstallAware 9 R2\Plug-Ins

Rename folder "dotNET Framework Runtime" to "dotNET Framework Runtime1"

Select the .Net framework 1.1 runtime.

Try to build (build type irrelevant).

Result: