LoadPanel error -143 (ActiveX Control Error)

[mwgesner]

I have an CVI 9.0 built application which includes the 3D graph ActiveX control (cw3dgrph.ocx).  The installer for this application was also built using CVI 9.0; I am including all of the LabWindows/CVI Run-Time Engine merge modules (except for .NET Support as we do not have Visual Studio installed on the development box - when I attempt to include .NET Support, a moduloe dependency check shows that .NET Support cannot be delivered with the installer) plus 3D Graph Control Support.  I have set up the installer to register cw3dgrph.ocx as an ActiveX server on installation.  The cw3dgrph.ocx file is installed to the System folder. The users are rebooting after installation.  I am seeing the following behavior:

1. When installed to the development PC (which currently has CVI 9.0 installed) or to a PC which has ever had CVI 9.0 installed (including those in which CVI 9.0 was uninstalled), I have no problem with the call to LoadPanel which loads the panel containing the 3D graph control.

2. When installed to a "fresh" XP installation, I see error -143 (ActiveX error) in the call to LoadPanel.  Note that this is a different error than an unregistered ActiveX control.  

This seems to have the look of a missing/incorrect version of a Windows-related .dll as opposed to a CVI Run-Time Engine or other merge module problem.   

[EadieU]

Thank you for reporting this.  We have verified that this is a bug and have filed a request for R&D. 

[EadieU]

 In case you are interested, the request was filed as Corrective Action Request (CAR) #165495.  You can call into NI and check on its status.   Thank you again for your feedback.  We greatly appreciate your help.  

[Alan A]

I'm using CVI 8.5.1 and believe I am seeing a similar issue regarding -143 Load Panel errors, with a registered MSFlexGrid activeX control.   I get the problem on distributed runtime code, and also on my development code.   Is this  likely the issue related to 165495?   If so, is there a work-around that I can do that avoids me needing to upgrade to another PC.   I have essentially the same set up as my colleagues, and they do not see this issue.   It suggests to me it is related to some dll versions.   Did the 165495 fix identify any suspect dll's? 

Cheers,

Alan

[vix]

I think it's the same problem solved here

[Alan A]

Hi Vix,

The problem I had was on the actul machine I've got CVI installed on.   I did find a workaround though - I downloaded and installed the CVI 2009 version, compiled and ran my code with that.  Then miraculously everything worked on CVI v 8.5.1.

Clearly a common dll issue, but not clear where!

Cheers,

Alan