Applies to
FastReporter 2, FastReporter 3
Question
Why won’t my measurement file open in FastReporter 3?
Answer
When a measurement file fails to load in FastReporter 3, the following messages are displayed:
FastReporter 3 (64-Bit)
FastReporter 3 (32-Bit)
If you use the 64-bit version of FastReporter and you are unsure if the file format is supported, you can try to open the file in the 32-bit version. Both versions of FastReporter 3 can be installed and run simultaneously on the same computer.
If the measurement file is from an accepted format and fails to open in both versions of FastReporter then it is possible that the file is corrupted.
The size of the file can give us a clue as to whether it could be corrupted or not. In the example below we can see that proper trace files vary in size (depending on number wavelengths, events etc.) but all the files are at least a few KB in size except for one which has been corrupted:
If the file is only a few bytes in size, then it essentially means that there is little data contained within the file. However, it is an indication only, we can also see corruption in files which still have the complete data set.
If you are still unsure whether the file is corrupted, then please reach out to our Technical Support team and they will be able to confirm this for you.
How did the file get corrupted?
As with all computer files, corruption can occur during file transfer (USB, cloud, email etc.).
The original file, if still stored on the EXFO unit, should still be intact. You can verify this by opening the file directly on the unit. If as expected it loads, reattempt the file transfer perhaps this time using a different transfer method (or another USB stick).
IMPORTANT
It is good practice to keep the original measurement files stored on the EXFO unit until the file transfer success has been confirmed.