LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Failure: "might.cpp" line 815 on LabVIEW executable

Hi,

I have a program written in LabVIEW 6.1 on a Windows XP platform. The program includes an ActiveX container that shows an Internet Explorer content window (just like the "Using the Microsoft Web Browser ActiveX Control" example found on http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B123AE0CB9BF111EE034080020E74861&p_node=DZ52051&p_submitted=N&p_rank=&p_answer=&p_source=External
, but without the activex queue in that example).

After I built the executable, I was able to run the exectuable on the development machine without problem. However when my client runs it on his PC with LabVIEW runtime engine 6.1 installed, he gets the message:

Failure: "might.cpp" line 815
For assistance in reso
lving this problem, please record the procedeing information and navigate to www.ni.com/failure or contact national insturments.

I cannot find any information on might.cpp on the NI support site. Any idea of what can be done to fix this problem?

Thanks!

Dan
0 Kudos
Message 1 of 3
(2,767 Views)
Hi dan,

you must contact NI support sending them the problem. "might.cpp" is a source module of LV and they can investigate the error.

Another thing you have to take into account is that LV stores the class ID and not the application. Has the client PC the same MS IE version installed? If not, the error could also result from different versions of the Active-X control.

As with the reporting Toolkit for MS Office you have to build a different version of your app for each different version of the control.

Waldemar
Waldemar

Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions
0 Kudos
Message 2 of 3
(2,767 Views)
Hello Dan,

I agree, I would recommend that you create a service request via www.ni.com/ask so that one of our engineers can effectively track and help you with this problem. Our engineers can then work with you to try to reproduce the problem and/or create a 'bug report' should the problem turn out to be incorrect behavior. Creating a service request helps us to better record and track the information in the event of these types of errors.

Thanks!

Liz Fausak
National Instruments
0 Kudos
Message 3 of 3
(2,767 Views)