Hello everyone,

I'm currently packaging "Mirror 7.2.6" which is a cosmetic surgery software using Wise Studio 7 and when I perform a setup capture, I will get prompted in Wise a RunTime error that says.

Microsoft Visual C++ Runtime Library
RunTime Errror!
Program: C:\Program Files\Al.... <--Truncated
R6034
An application has made an attempt to load the C runtime library incorrectly.
Please contact the applications support team for more information.


Here is a snapshot.
[link]http://picasaweb.google.com/lh/photo/xhQDOAPjv40eRSjmVXKXbA?feat=directlink[/link]

The three files that it chokes on with this error is...

1. MFCM80.dll
2. MFCM80U.dll
3. MSVCM80.dll

I can click "Ok" to get through it, the MSI is created and I slap together a quick wrapper for testing. I'd thought I would just ignore these RunTime errors and see what happens.

I can get the application to install successfully, but when I got to launch the application it fails from the start. I get a generic error message.

I checked the event viewer and the only thing I could find in the "System" log was


Event Type: Error
Event Source: SideBySide
Event Category: None
Event ID: 32
Date: 2/16/2010
Time: 2:41:35 PM
User: N/A
Computer: VMCORE0N
Description:
Dependent Assembly Microsoft.VC80.OpenMP could not be found and Last Error was The referenced assembly is not installed on your system.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


There was absolutely nothing in the Application Log.

Any ideas what could be going on here?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
At a guess, I'd say that you have a problem with side-by-side C++ runtimes. Quite why that should be a problem on a packaging box - which really ought not to have any side-by-side junk - escapes me.

ProcMon, as ever, will show you exactly what's going on.

EDIT:
Try installing the relevant C++ runtime before you start the capture and see what happens. If that works, you could try packaging the runtime in a merge module which you can add to the package.
Answered 02/16/2010 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity