genericmgr.cpp error in line 778

[Andrey_Dmitriev]

Hallo,

I've got exception genericmgr.cpp error in line 778. Occured sporadically and relative rarely. IMAQ Vision 7.0 is used.
Here was a topic about same exception, but in line 775... IMAQ 3.0 inastalled (but not used).

May be anyone else have seen such exception?

with best regards,
Andrey.

[RobertH]

hello andrey,

which version of LabVIEW do you have installed?
Can you give an overview of the software and drivers installed on your system?

regards,

Robert H
National Instruments

[Andrey_Dmitriev]

Windows 2000 Professional (ENG)

LabVIEW Run-Time version 7.0

IMAQ Vision 7.1.1:
NIVision.dll 7.1.1.4004
NIVisSvc.dll 7.1.1.948

No any NI Framegrabber used.
No development modules are installed omn the target machine.

[RobertH]

hello,

can you additionally provide the log-file, which is created by LV after the error occurs and maybe a fragment of your VI, which causes the error?

regards,
robert h
national instruments

[Andrey_Dmitriev]

Robert,

Thank you for help, but unfortunately I cannot provide log file, because unable to found this file in temp directory. I guess that crash log file is not created, because no LabVIEW Dev.System  installed on target machine. Only LabVIEW Run-Time Engine. This "crash log" file seems to be created only if error occured in LabVIEW, but don't created if error occured within builded application.
I have recompiled my application from 7.0 to 7.1.1. The "same" error present anyway, but now in line 840 (also in module genericmgr.cpp).
This error occured sporadically sometimes 2-3 time per hour, and sometimes 2-3 days software running without problems.
Its difficult to locate which SubVI caused this problem, because application contained 1000+ SubVIs and this problem not present in development environment. So, application cannot be simplified for isolating problem.
Our customer is very unhappy, because this industrial system running 24 hours per day 7 days per week and must be "crash-free".  And I haven't idea how we can help him for solving this problem.

Andrey.