TDMS File Corrupts on Close in LV 2009 SP1

Question

I have an application that logs data to a TDMS 2.0 file, LV 2009 SP1, Windows 7 x32.
Initially, I set it up so that the app opens one R/W reference to the file.  The state machine program writes data to the file in one step, then reads back the last 1000 points in another.  The logging is slow, roughly 1Hz.  There is no possibility of concurrent Reads and Writes.
When the program closes, I call the TDMS CLOSE method.
When I restart and try to read the data, I get error -2511/0xFFFFF631 "LabVIEW:  The specified TDMS file is corrupt."  Every time.
When I try and open the file in the TDMS viewer, the viewer shows the wrong number of samples in the properties, then shows no data at all (I assume it's eating the error, since it does not present it to me).
I have tried:
1) commenting out the code that reads.  No good.
2) Opening a separate reference each time I wish to make a read.  Nope.
3) Buffer On/Off
4) Flushing
5) Deleting the index and trying again.
6) Removing the CLOSE function
7) Killing the app instead of gracefully closing
8) Changing the filename/path
9) Writing to an SSD disk
10) Writing to a SATA disk.
None of that works.  Essentially, the TDMS file is fine until it is closed.  Then it is corrupt.
Any ideas?

Answer 1

Hi Jed,
I have a couple of questions:
Have you tried with the latest TDMS component? It's free to download, and here it is: http://zone.ni.com/devzone/cda/tut/p/id/9995
Is that possible or convenient for you to post your reproducible VI here, it would be great helpful for us to look into?
I have made a very simple VI for recovery corrupted TDMS files, attached in this post, maybe you can have a try, but please backup your file before trying.
Attachments:
RecoveryTDMSFile.vi ‏17 KB