filemgr.cpp error line 5662

[DavidL]

hi,readers
I 'v got an error (on filemgr.cpp line 5662) on a vi that acquire around 8000 files a day.
That error happends 1 time every 1 or 2 days.
I 've got lots of files in my directory (around 50.000).
Has someone has already had such problems ?
Thanks for help.

[DavidL]

I forgot to say i m using LV6.1 on win2000

[GianniM]

Hello,

Unfortunatly, your problem was reported for the 6.1 version of LabVIEW, but it wasn't reproductible, so not corrected. For the moment I'm not sure that it's solved in the 7.1 version.
Can you provided us a piece of code that I can test to try to reproduce the problem (not the all application)?

Gianni Martinico
Applications engineer
NI France.

[DavidL]

hi,

could you tell me wich underVI could be involved? because my application is quiet huge, and my client very far away from me, so that i can't make tests myself when the problem appears.
Thanks for caring.
Best Regards

David LECLERCQ
Sifial France

[GianniM]

Hi,
It's not possible to determine exactly which function is involved, because many functions can handle a part of this module. Even if we find the function, the fix will only be applied on the next version of LabVIEW, and not on the 6.1. I think, the best way for you, if you can't reproduce the problem with a code snipset, is to try with the trial version af LabVIEW 7.1 (US), and ,if the problem goes away, upgrade to last version.

Gianni Martinico.
Applications Engineer.
National Instruments France.

[DavidL]

I've reduced the number of files in my directories (from more than 50.000 to 8000 max) and the problem doesn't seems to happend anymore.
I'll let you know if i find some more clues about it.
Best Regards

David LECLERCQ
Sifial France

[DavidL]

My client, still have the problem, randomly once a day, and starts to be very upset.
The program is running on sources 7/7d & 24/24h.

-Do you think it could change something if i compile a stand-alone executable ?

-Can i install LV6.1 and 7.1 simultaneously on the same computer, so that i could switch easier between versions ?

-Would it helps you if i try to see wich of my vi is running when the crash occurs, and send it to you, even if it's not directly executable ?

Thansk for your help.

David LECLERCQ
Sifial France

[DavidL]

Problem seems to be solved.
A file that was opened with a "open file" vi, was not closed. Since it is closed with a "close file" vi, no more error.