InstallAware

Install file built with InstallAware studio 9.

We have just one customer who is experiencing this error, but he is seeing it on two separate Windows 7 64 bit machines. The installation appears to run correctly but towards the end of the routine we see two errors, after which InstallAware reports the installation as having failed. The error messages are:

Microsoft Visual C++ Runtime Library
Runtime Error!
R6034
An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information.

Then the second message:
Error
There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor.

I found a MS support article (http://support.microsoft.com/kb/2003976) which appears to refer to a similar error and the suggested workaround removed the first of the errors above but not the second.

If anyone can shed any light on why we might be seeing this error or any steps we could take to resolve the problem I would be extremely grateful.

Paul

Dear Paul,

In order to help you I need more info about your installation.

what happens running your setup on 32 bit OSs?
Which component in your Installation uses a call to "Microsoft Visual C++ Runtime Library"?
are you sure that you are using the correct "Microsoft Visual C++ Runtime Library" version (x86 or x64)?


Regards

Hi Francesco

My apologies, I realise I missed a (probably vital) line out of the first error message I posted. The full message was:
Microsoft Visual C++ Runtime Library
Program: c:\windows\syswow64\MsiExec.exe
Runtime Error!
R6034
An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information.

The install gives no problems on 32 bit OS machines, nor on the vast majority of 64 bit. The install itself is a very simple "patch" for an existing software package. For various reasons the method we use is to include a number of updated files within the "Creatives" section of the install and then within the MSI code we delete the original files and copy over the new versions. The MSI code is very simple indeed: a whole load of DELETE FILES and COPY LOCAL FILES commands, we write the target folder to a registry key, fire up Notepad with a text file with details of the update and that's about it.

As far as I am aware there is nothing in our installation which is making any calls to the MS C++ library at all. As the error was reported by MsiExec.exe my assumption was that the issue was somewhere in the way the InstallAware installation program was interacting with the Windows installer. The other piece of information which I guess may be relevant is the failure message returned by the installation program after the two errors - it finishes saying "The InstallAware wizard for... has failed: 'This action is only valid for products that are currently installed'. Please check your settings and try again."

I don't know whether any of that helps. I really appreciate any insights you can give me.

Regards,
Paul

Dear Paul,

Very probably, but I am just supposing this, your way of doing the patch it is not quite correct.

A patch project should have the same logic flow of the base project which is related to.
Are you sure that with the approach you are using to update your setup files, still respects the original code flow?
This because you receive the message;

'This action is only valid for products that are currently installed'

Probably due the above considerations, it causes an error with MSI engine ... but it is strange that happens only on some restricted x64 OSs.

Is it possible to have a look at your projects?

Let me know.

Regards

Hi Francesco

I'm not sure I fully know what you mean by "the same logic flow". The initial install performs all kinds of actions including installing drivers, registering components and installing a couple of hundred files. All the "patch" does is to replace a small number of those files with later versions. The patch may not even be run on the same machine as the actual program is run on if the installation location is a shared network location, so it is a very simple maintenance process - delete a few files, copy a few new files.

Anyway, I am very happy for you to look at the projects and really appreciate any assistance you can give with them. Can you let me know which files you need to see and I will upload them for you to take a look at.

Many thanks,
Paul

Dear Paul,

What I mean is, if you used a base project that perform some actions, your patch project should be the copy of this plus any modifications.
So mainly, the script you used with your base project should keep the same identical logic.

Anyway send me your projects (base and Patch) or a sample project, if you are able to replicate your issue.
I'll verify it of course!

Regards

Will do. I'm probably missing something obvious, but how do I PM you? I'd prefer not to post the projects publicly.

Paul

Dear Paul,

contact me at: [email protected]

Regards