LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

ActiveX Control Could not be Loaded

I was using an instrument driver supplied with the Coherent Labmax TOP earlier today and it was working fine. Later in the day I would get messages that the ActiveX control was not properly initialized. On the front panel I see the ActiveX container says "Control could not be loaded" as below. I found this link which says to repair the Runtime engine. Oddly enough, I don't see the 2014 Runtime engine in my list of NI Software, does anyone know how to uninstall it or repair it? 

 

activex.PNG

0 Kudos
Message 1 of 10
(2,840 Views)

Were there any Windows updates on the computer?

 

Ben64

--------------------------------------------------
The best way to say thanks is to give kudos!
0 Kudos
Message 2 of 10
(2,821 Views)
I don't believe so. In the span of about 3 hours away from my computer it stopped working. And my computer was not restarted then.
0 Kudos
Message 3 of 10
(2,815 Views)

You don't by any chance have any other applications open that might be trying to talk to the LabMAX, do you?  Any Coherent programs running in the background?

 

For what it's worth I have used one of those before and found its USB connection method to be entirely too buggy to use.  Ended up using a USB-to-Serial adapter and building my own set of driver VIs in order to get any amount of stability out of the device.

Message 4 of 10
(2,806 Views)
No I just have the one application, and I'm developing on a computer without the labmax attached. I agree, their LabVIEW drivers are old and it's weird to have the ActiveX control running at all times.
0 Kudos
Message 5 of 10
(2,800 Views)

If you have LabVIEW dev environment, you shouldn't need the run-time engine.  Have you restarted the computer?

 

You can try repairing LabVIEW if nothing else fixes the problem.

0 Kudos
Message 6 of 10
(2,734 Views)

Hi Gdrag,

 

I've tried re-installing LabVIEW and restarting the computer, but this has not fixed my problem. I don't know why the run-time engine would effect it, but I linked to the article provided by National Instruments that suggests it as a solution.

0 Kudos
Message 7 of 10
(2,725 Views)

Maybe a system restore?

 

Ben64

--------------------------------------------------
The best way to say thanks is to give kudos!
Message 8 of 10
(2,711 Views)

The fix for me was to re-install the vendor's software. Even though I don't intend to use it, it registers the ActiveX component correctly and I can work with it in LabVIEW again. Thank you all!

0 Kudos
Message 10 of 10
(2,703 Views)