TDMS file error occurs after several hours

Question

I have a compiled LabVIEW 2010 SP1 executable running on a Windows 7 PXI computer that is occasionally producing the following error message:
"LabVIEW: LabVIEW could not load the TDMS file component.
The top-level VI <my VI's name> was stopped at unknown on the block diagram of  <my VI's name>"
This program is interfacing with equipment under test over a number of PXI cards and ethernet connections. It alters inputs to the system based on script commands, while receiving and displaying outputs. During testing, state changes are sent to a TDMS file. The system can run for hours but will usually produce the above error message... eventually.
The error seems to indicate that a LabVIEW file is missing, but the TDMS files are being created, so I may not be understanding the meaning of the error. Does anyone know what the actual cause(s) of this error message are?

Answer 1

The code writes to the TDMS file using the "TDMS Write" VI from the TDM Streaming Palette. These write VIs are located in 12 different sub VIs in a program loop within my main VI. Every 50ms they execute, service the I/O,  and write to the TDMS file if data in the particular sub VI has changed state. Some are writing floating point numbers, most are writing strings. There are about 750 total channels being written. I know that posting the code would be more usefull than describing it, but I think posting the source code would be frowned upon by my company. There are over a hundred custom VIs and external hardware connections that are required to effectively run this code anyway.
Regarding timing, there doesn't seem to be a particular amount of time that has to pass before this issue occurs. I was given a screenshot that shows the error occured after 11 hours of running. I was also told that the same error had occured about 6+ hours into a test once. I can say that this error doesn't seem to occur quickly, as in within the first hour or so. It seems to require long duration tests.