activex control error -143 when Installing application on PC

[Andreas L]

Hi!

I have problems installing a developed program:
The software was originally developed using the mscomctl.ocx under CVI V7.1 and was also successfully deployed from there. Now we moved to CVI 8.0, made a few enhancements (not at any functions regarding the ActivX Control), and now we cannot distribute the application anymore. All the time the application produces the error stated in the subject line on a target machine when a customer tries to start the program. Installing and unsing the old version works without any problems.
We have already removed the used ActiveX controls and replaced them, tried to generate new Control Drivers, all without success...
The msm files included in the build are the cvirte.msm (We added this module manually, because the software is generated on a German PC)and the mscomctl.msm.

Regards

Andreas

[Andreas L]

Hi!

I just found the problem:

I also had to add the 'ActiveX Container.msm' to the build project and then the software also works on the target computer.

The only thing that is a bit strange to me is, that when I checked the module dependency, no error was generated, when the ActiveX Container was not added to the project. I think this missing module should produce an error message to programmer when executing the check!

Regards

Andreas

[Mert_A.]

Hi Andreas,

You should not have to manually add the .msm by the Add Additional Module button. If you distribute your application with the CVI Run-Time engine, you can either select the top-level "LabWindows/CVI Run-Time Engine" item in the Drivers and Component list, or you must select the "ActiveX Container Support" sub-component.  Doing so will ensure that your distributed application has the run-time support for ActiveX controls.

I understand that the Check Module Dependencies button may be somewhat misleading.  If you click the help button on the dialog and scroll down to the bit about the Check Module Dependencies button, it explains that this button simply ensures that for any .msm file included in your distribution, its dependency chain (items listed in the .msm ModuleDependency table) can be fully found and included in the distribution.  This button does not detect run-time dependencies of your project.

Hope this clears things up a bit.

Mert A.
National Instruments

[Mert_A.]

Oops. I overlooked the comment you made in your first post about having to add the .msm files manually because of the German Windows.  Since you are using 8.0 on a non-English OS on which Program Files is localized, you must add .msm files manually.  This bug was fixed in the 8.0.1 maintenance release, which you should consider upgrading to.

Mert A.
National Instruments