CVI 9.0 ActiveX Control Error -143

[vix]

I've already searched into the forum, but none of the suggestions help me; the problem is easy to reproduce, so I hope someone could help me...

I compiled and created a build for the example \userint\activex\webbrowser supplied with cvi 9.0.

This example works fine (in debug mode, if I launch the release and if I install the build) but ONLY on the machines where CVI 9.0 is installed.

If I install on a fresh WinXP Pro SP3 with Internet Explorer 7.0 the program crashes with ActiveX Control Error -143.

The same crash even if I use a fresh WinXP Pro SP2 with IE 6.0, and WinXP Pro SP2 with IE updated to 7.0 version.

How can I have the webbrowser example working on machines without CVI 9.0 development system? 

[vix]

I realized that my problem seems very, very similar to those described in this thread.

Am I right? 

[Chuck_81]

Hi Vix,

I've seen the CAR associated to the forum thread you linked, and it refers to a similar issue as the one you're facing. Unfortunately this is a bug and R&D is investigating on this.

I'll reply to this thread as soon I'll get news from our developers.

Sorry again for the inconvenience,

Best Regards,

Fabio

[vix]

Unfortunately this is a very big problem for me

I run my application on a Solid State HDD which is only 1GB large: so I haven't free space enough to install and uninstall CVI Development System.

Are there some "tweaks" (registry editing, DLLs registrations, ...) I should do to have my application working, without a CVI installation?

I need this answer (or other useful informations) ASAP...

Thanks in advance

[jared · Accepted solution]

The bug is that the CVI ActiveX container has a dependency on the VC runtime that the distribution kit doesn't know about. Many applications install the VC runtime (such as CVI), which explains why this only happens on a 'fresh' XP installation.

The workaround is to add the attached merge module to your distribution kit. It will install the VC runtime with your application when it is installed on the target machines.

Hope this solves your problem and sorry for the inconvenience.

- jared

[Ian.W]

Jared,

I am having this same issue building with CVI 2009.  What guidance can you give about the version of that msm you posted and which one we should now use?

In Program files (x86)\Common Files\MergeModules I have a number of VC80 and VC90 (and x86 vs x64) msm files that seem to be newer than the one you posted.

Thanks,

Ian

[LuisG]

Ian,

Try including the following merge modules in your distribution:

C:\Program Files (x86)\Common Files\Merge Modules\Microsoft_VC90_CRT_x86.msm

C:\Program Files (x86)\Common Files\Merge Modules\policy_9_0_Microsoft_VC90_CRT_x86.msm

C:\Program Files (x86)\Common Files\Merge Modules\Microsoft_VC90_ATL_x86.msm

C:\Program Files (x86)\Common Files\Merge Modules\policy_9_0_Microsoft_VC90_ATL_x86.msm

Luis

[Ian.W]

Thanks, Luis, but it gave the same result. In desperation I also tried several combination of the V9 and V8 versions, and later also including the MFC files in addition to the ATL and CRT ones. No luck. My test bed is a virtual XP Pro SP3 machine.

I presume there are some other dependencies we need to find ... or perhaps the security patch that drove dependency changes mentioned here is the culprit?

Thanks,

Ian

[LuisG]

Can you let me know which version of C:\Program Files (x86)\National Instruments\Shared\nicont.dll you have installed in the system where you're seeing this error?

Luis