RT data logging and control VI stopped working after upgrading from 2015 to 2017

[CaveJohnson]

I have a VI that is deployed onto a cRIO 9118 that is logging data from a few sensors and controlling some outputs. I am running it in scan interface and have it structured properly, with the read in a synchronized loop, and the tdms write in a separate loop. I had this VI running on a computer in labview 2015. We were having troubles with that computer so we moved to another and did a fresh install of 2017. Now on the 2015 computer I was able to log data, and then ftp it to the computer. But now with labview 2017 I get this error when I try to open the file that is created:

USI encountered an exception: TDS Exception in Initialize: Tds Error: TdsErrNotTdsFile(-2503):

Everything else works fine, and there are no errors coming from the tdms open, write, or close. Just when I try to open them in excel with the tdms importer. I also tried opening them on another machine to see if the tdms importer was corrupted and it gave me the same error. What am I missing? Could something have been corrupted during the install? or am I missing some software on the cRIO?

I actually just ran two tests. I created a VI on the computer and on the cRIO and wrote an empty tdms file. the one on the computer worked, and the one on the cRIO gave me that error. My best guess is that I'm missing some software on the cRIO? Any help would be great, thank you!

[Mike.B]

Hi CaveJohnson,

This typically means the TDMS file is corrupted. That it only throws the error opening the file from your cRIO and not the one from your computer heavily implies the cRIO is the culprit here. As an aside, a previous user generated a tool to help locate the corrupted segment of a TDMS file should you need to use this in your troubleshooting.

Would you be open to force reinstalling the software on your cRIO?

Less likely to prove helpful, but you could also see if you can read in the supposedly corrupted TDMS file in LabVIEW. If you can read it there, perhaps it is the  TDM Excel Add-In for Microsoft Excel that needs to be force reinstalled.

[Bob_Schor]

In my (limited) experience, LabVIEW 2017 is "buggy" compared to LabVIEW 2016 (it may have to do with the Toolkits and Modules, rather than LabVIEW, itself).  I've had multiple "failures to install", in two cases forcing me to wipe the PC and reinstall Windows and everything else.

If you find you cannot get LabVIEW 2017 to work, but have LabVIEW 2016 available, I would recommend calling NI and getting their advice on how to completely remove LabVIEW from your PC, do that, reboot, and install LabVIEW 2016.  [Note that "backing out" of LabVIEW 2017 is a non-trivial task, as I found out to my chagrin ...].

Bob Schor

[CaveJohnson]

I tried both of your suggestions and tested the file with that utility. It yielded an error 8, I'll have to investigate further what that might mean. I also uninstalled, and then reinstalled the software on the cRIO. After It still gave me the same error. We're doing some testing right now, but afterwards I might follow the other suggestion and just reinstall labview with 2016.

[CaveJohnson]

Re downloaded labview to 2015 SP1 and still have the same problem. I think that's even the original software that I had, so I'm still working on the issue.

[TimothyDug]

Hi CaveJohnson,

Did you go through with the force reinstall yet? Is the error 8 on the force reinstall? Can you post a screenshot of the code? Or if it is small, just the VI itself.

Thanks,

[CaveJohnson]

Yeah, I still get the same error after the reinstall with the different version. I ended up just setting up a network stream and saving the data to a tdms file on the computer as a workaround and it seems to be working. If you would like to take a look at the code it can be found here: https://forums.ni.com/t5/Version-Conversion/Need-help-downgrading-project-from-2017-to-2015/m-p/3775...