Runtime error R6025 and Vision Image window freezing

[GregSands]

I'm running LabView 8.0.1 and Vision 7.0 (our site license currently only covers to this version).

For some VIs (running in LabVIEW, not runtime) on some machines, the following occurs:

When clicking on an Image window with the pointer (Tool 1) the Image window freezes - i.e. cursor position is not updated, and the user is unable to click further.  This is usually, but not always, remedied by changing the tool to something else and back again.  In any case, when the application is closed, it causes a R6025 runtime error.

1. On two machines (with the same VIs used) this does not ever occur, but on two others it always does.  The only difference would be in the other software previously installed - those without the problem had LV7.1 installed earlier, while those with the problem went straight to 8.0.1 - and also the working machines had Vision 8.0 evaluation installed briefly - perhaps some code remained after uninstalling.  Also, the problem machines are much newer and faster (3.2GHz P4s rather than 2.4Ghz P4 or 2.1 GHz Pentium M).
2. I can create a simple program on the problem machines which use an Image window, and get the Image events, and no error occurs.  I haven't been able to track down what extra code is required to cause the error, but it's possibly code that modifies the Image ROI.

I've looked at the other message on this forum regarding error R6025 but it seems to be quite a different problem.

I can imagine the solution will be to upgrade to Vision 8 (which we're waiting for our site license to catch up to!), or reinstall LabVIEW starting with 7.1, but if anyone has any other ideas where this may be occurring, I'm all out of them myself!

Many thanks,
Greg

[Jeffrey_P]

Good afternoon Greg,

This appears to be a very peculiar issue.  I have seen this R6025 runtime error.  In most cases, it been caused by script blocking in Norton Antivirus.  It might be a shot in the dark, but you might want to disable this feature in Norton Antivirus.  This is usually associated with ActiveX objects or routines, but it might be worth a shot!

Please post back with the results, if you get a chance!

Respectfully,

[GregSands]

Thanks Jeffrey, but that doesn't seem to fit here.  All the computers involved (with and without the problems I describe) have Symantec AV Corporate installed, with exactly the same configuration, and there doesn't seem to be any options to do with script blocking at all.

Cheers ~ Greg

[Jeffrey_P]

Greg,

First off, Vision 7 by default won't install support for LabVIEW 8.0.  How did you get Vision to install support for LabVIEW 8.0?  We have a knowledgebase from www.ni.com/support that has a utility designed to help with this.  If you did not use this utility, then there is a chance that all of the proper folders and files did not get moved properly.  Please take a look at the following link:

http://digital.ni.com/public.nsf/websearch/25FD880AC87C4DA6862570B30056C572?OpenDocument

If you have been through this process, and still this problem is happening.  Then, there is a possibility that there is something corrupted in the IMAQ image control.  I would try going to the following directory:

C:\Program Files\National Instruments\LabVIEW 8.0\resource\PlugInControls

Delete everything in this folder, and then repair the IMAQ driver and the Vision Development Module.  This should fix any corruptions in these files!

Respectfully,

[GregSands]

Thanks Jeffrey, you pointed me in the right track.  Turns out that where I had installed Vision 8.0, then uninstalled and gone back to 7.0, it had left version 8 of NIVision.dll, so LabVIEW was using the newer code that works OK with LV8.  I couldn't get the utility you mention to work properly, but if I install the latest IMAQ 3.13, it seems to all work fine - that upgrades the dlls to version 7.1.1.  For some reason, although we have a site license for Vision 7.1.1, we don't have the installs available anywhere (not on the NI site or own own repository).  Hopefully we get the full upgrade to version 8 (or 8.20 now I guess) soon - though that's out of my hands.

So it all makes sense in the end - thank you very much.

Cheers ~ Greg