Runtime error R6025 in a built app using static ref and Fieldpoint

[ChristianRoy]

I get two error messages when the built version of my program terminates:

•  Runtime Error! This application has requested the Runtime to terminate it in an
   unusual way. Please contact the application's support team for more information.
  
•  Runtime Error ! R6025 - pure virtual function call
  

This does not happend in the development environment.

As the 3 joined VIs show, the bug involve a static reference to a VI that performs a FPwrite. Even if that VI is never called.

Is there any workaround. Some proper way to "close" the static ref. I would like to keep using the static reference since it makes for an easier to maintain program (no broken path if you rename the refered VI).

Thank you all

[BenjaminR]

Hi,

The error primarily occurs when you fail to close FieldPoint references in LabVIEW. Make sure that you are closing all references to your FieldPoint module before running your application.

This error can also occur if "Script Blocking" is enabled in Norton AntiVirus. You must disable this feature in order to use Microsoft Word ActiveX containers. Please refer to the Microsoft KnowledgeBase for steps to do this.

[ChristianRoy]

I don't understand what you mean by "closing all references to your FieldPoint module before running your application".

My built application is running alone on a freshly started standalone machine (I dont have any fieldpoint connected to that setup yet).

The only "reference" I have are an IOpoint control (in a running subvi) displaying an "intended" future connection and a FPwrite in the static reference that is never called. I have even try to close the static reference with no success. (I dont know if it makes sense to close a static reference?). By the way, if the IOpoint stays hidden during the execution (ex. on a different tab page) the bug doesn't show up.

On your other point, I dont have Norton AntiVirus installed. I could disable my antiVirus but I dont use any ActiveX either.

A last point.

After spending days isolating the problem in the simple example I have previously attached,  I manage to solve the problem on that example but not in my real case. The solution was to drop the static reference and force the VI in memory with the "build property/Source files/Always included". Unfortunately, in the real case, the refered VI is not found when I try to open it and the bug seems to show for some unkown reason (no static ref refering to Fieldpoint around).

Hope you can help

Christian

[BenjaminR]

Hi,

Do you have older versions of LabVIEW Run-Time Engine on your PC?  Try to remove all of it and reinstall only the lasts’ version you have.

Can you give me more details about your application, i.e. LabVIEW version, Runt-Time Engine version, …?

[ChristianRoy]

Hi,

Still no progress...

To be on the safe side, I have uninstall every NI products and reinstall a minimum configuration from the LabVIEW 8.5.1 package. I have tried with the following:

NI LabVIEW 8.5.1
NI LabVIEW Advanced Signal Processing Toolkit 7.5
NI LabVIEW Digital Filter Design Toolkit 8.2.1
NI LabVIEW PID Control Toolkit 8.5.0
NI LabVIEW VI Analyzer Toolkit 1.1
NI LabWindows/CVI 8.1.1 Run-Time Engine
NI Measurement & Automation Explorer 4.4.1
NI-FieldPoint 6.0

After that I have also installed the NI-FieldPoint 6.0.1 package from http://joule.ni.com/nidu/cds/view/p/id/996/lang/fr. All with the same result.

Christian

[BenjaminR]

Hi,

Have you tried to test your system on a ‘Blanc PC’, i.e. in which no NI Software are already installed, no spyware, no Antivirus… Moreover, when you uninstalled all NI Software have you deleted all the registries?

Let me know the result on another PC.

Message Edité par BenjaminR le 05-22-2008 02:35 AM

[ChristianRoy]

It worked!!

I haven't try to delete the registry entries on my machine (and install all the LabVIEW stuff again) but on a "blanc PC", with no NI product, both the simplified and the full versions of my program run and terminate flawlessly.

So it could be an old registry entry or the NI LabWindows/CVI 8.1.1 Run-Time Engine on my PC that causes the bug (the blanc PC used the NI LabVIEW Run-Time Engine 8.5.1 instead).

Anyway, now I know what to do for the target system : a real good clean-up.

Thank you very much!

Christian

P.S. Je m'excuse pour le "posting" anglais... Il semble que l'interface français de mon PC m'envoie ici systématiquement. Merci encore.

[Logan_081]

Hi to all,

The step which allow to solve the problem are listed in the document linked below: 

Runtime Error (R6025) When Using LabVIEW 

Regards