InstallAware

I've built a fairly simple setup, creates a website in IIS, and installs a windows service. Problem is that it crashes after install, the eventlog shows fauling module is ahadmin_wrapper.dll. I've googled and it seems to be an old bug that has been fixed. Now, here's where I seem to be having a brain fart, I can't find a way to update InstallAware Studio itself, there's no "Check for Updates" button anywhere in the app. I'm on Build Moooya.9.26.11.

So is there a way I can update to a version of 2012 that has this bug fixed, or is there a workaround in case there is no further update to Studio 2012?

kamau,

I'm not sure if there is an upgrade to your version but a couple of things come to mind you might want to think about:

1. Have you downloaded the latest license file for your release? I have a distant recollection that "things" happen in the latest license file for a specific version which complement the IA installation and that might "fix" some things but I might be way off the mark, in short, my equivalent of your brain fart.

2. Perhaps you can download the latest X3 release and see what happens in your project when you build it with that. I think you have a trial period with X3 so expect nag screens.

Bear in mind that installing a new version tears down what you have installed already so make sure you have the installation media for your licensed version to hand to put it back afterwards if you try X3.

Hope this helps you in some minor way.

Thanks for your suggestion. I checked, I do have the license .exe for my installation, and it's fully licensed, did it some time back. I'm hoping to avoid having to upgrade to X3 as there will definitely be a cost involved and the co. will not agree to pay. I'm hoping there's a hotfix or update that can fix the crash as it is a bug in InstallAware itself, not my setup.

So is there no button to check for updates anywhere? Very strange that an app that creates setups that can update over the web would itself not be updateable.

I appreciate your concerns but I really don't know what options are available. I think we'll have to see if Cap'n Francesco has any suggestions about things. I'll try and research that error for you and see if anything else comes to mind but I think I've more or less sucked clean any marrow that might still be resident in my ageing bones.

Dear kamau,

can you please contact me at support@installaware.com .

Regards

E-mail sent.

Received!

I guess this thread can be closed.

It appears the bug is in the ahadmin_wrapper.dll assembly and there is no fix available for IA 2012 Studio. I find this a bit bizarre as it's only 3 years old and while I don't expect an update to have new features, I'd expect at least bugs to be fixed. You may ask why we can't just give in and upgrade, let me explain.

We bought InstallAware sometime in 2012, with plans to migrate our old InstallShield setup, to IA. Unfortunately we had political turmoil in the country until almost mid 2014. Business stalled and so the migration kept being put off as priority was to give clients the features they asked for, not upgrading a working setup. So IA sat there on our build server fully licensed but never used. Well, now it's 2015, business is getting better and we're virtualizing all our previous servers and the last one left is the build server which has failed to run properly as a VM because of a bug in the InstallShield licensing where it can't build via command line.

So we decided to see if we could migrate to IA2012 and finally migrate to a VM and got stuck with this bug. The finance guys will not authorize $1k outlay for now as it's not mission critical, the old setup works, it's just a pain having an old HP server sitting there only to build the setup. Hopefully, they'll agree in a couple of months.

Thanks for your help guys.