Error 6 occurred at TDMS Open in TDMS

Hi,
I have a application that is using the TDMS VI's to generate a Logfile.
The application ran correctly for 12 days. (Each errors, and some parameters - every hours - was correctly written to my TDMS file).
Then, the following error occured :
Error 6 occurred at TDMS Open in TDMS - Write data SubVI V1.2.vi->D2XX MultiTester V1.5.vi
Possible reason(s):
LabVIEW: Generic file I/O error.
=========================
NI-488: I/O operation aborted.
I join my VI that manage the TDMS file.
The error seems to come from the VI "TDMS OPEN". The corresponding TDMS file is effectively at the specified path, and its content is OK (all expected infos are present). The file is called LogFile_0_1.TDMS.
Depending on the TDMS file size, the application automatically creates a new file. I tried to force that to get a new TDMS file (assuming that the active file was corrupted or blocked). A new TDMS file was created (LogFile_0_2.TDMS.) but only the first tab (root) was created. Then the same "Error 6 " was still present, exactly like before.
Do you think this problem can come from Windows?
Or does it come from my application? What is not optimal, is that this "TDMS - Write data SubVI V1.2.vi" is called about every second, and the "TDMS OPEN" function is called unconditionally (even if no modification on the TDMS file are needed).
How can we explain that this bug appears after about 12 days only?
I also join you the LogFile_0_1.TDMS that I converted to an Excel file, and the LogFile_0_2.TDMS that was not correctly created.
Thank you in advance for your support.
Michael
Solved!
Go to Solution.
Attachments:
LogFile_0_1.xlsx ‏560 KB

MarcoMauri wrote:
My guess is that you forgot to close the TDMS file and each time your VI is called a reference is created.
It could be that after a week the maximum possible number of references was reached, and you got the error.
Regards,
Marco
Marco,
That's not just a guess, that is a very real possibility. And lets not forget the memory leaks from not closing references.
ALWAYS close ANY references you create. If you open a reference to a file, make sure you close it.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Similar Messages

Unable to prepare project for publishing the project could not be prepared for publishing because an error occurred. (file already open with write permission)

Get this message when I try to publish my iMovie project. "unable to prepare project for publishing the project could not be prepared for publishing because an error occurred. (file already open with write permission)"

See the discussion here:
https://discussions.apple.com/message/16784714#16784714

An unknown error occurred (-42110) when opening itunes after upgrading

when opening itunes i get "an unknown error occurred (-42110) when opening itunes after upgrading to latest version.

Try the following user tip:
iTunes for Windows 11.0.2.25 and 11.0.2.26: "Unknown error -42110" messages when launching iTunes

An error occurred [CANF] when opening Illustrator

Adobe creative cloud recently updated now getting error on opening of illustrator... Any ideas folks?
An error occurred [CANF] when opening Illustrator

luminite design,
You may roll back here,
http://prodesigntools.com/adobe-cc-version-control.html
but unless this is a new general strangeness, you may try the list.
The following is a general list of things you may try when the issue is not in a specific file (you may have tried/done some of them already); 1) and 2) are the easy ones for temporary strangenesses, and 3) and 4) are specifically aimed at possibly corrupt preferences); 5) is a list in itself, and 6) is the last resort.
1) Close down Illy and open again;
2) Restart the computer (you may do that up to 3 times);
3) Close down Illy and press Ctrl+Alt+Shift/Cmd+Option+Shift during startup (easy but irreversible);
4) Move the folder (follow the link with that name) with Illy closed (more tedious but also more thorough and reversible);
5) Look through and try out the relevant among the Other options (follow the link with that name, Item 7) is a list of usual suspects among other applications that may disturb and confuse Illy, Item 15) applies to CC, CS6, and maybe CS5);
Even more seriously, you may:
6) Uninstall, run the Cleaner Tool (if you have CS3/CS4/CS5/CS6/CC), and reinstall.
http://www.adobe.com/support/contact/cscleanertool.html

Error occurs when I open the tasks list in MS Project Professional 2013 from SharePoint 2013

Hi,
I have created a SharePoint 2010 workflow for a tasks list that updates a list item column if the Date Complete <= Today's date & Percentage Complete = 100%
I used 'Set Field in Current Item' in the workflow & the values are updated in the list for the current item.
However, when I open the tasks list in MS Project Professional 2013 from SharePoint 2013, then I get a error "We can't write task - taskname to the SharePoint site. This is either because tasks list is in read only mode or because this task has a column
that requires unique value."
If I remove the 'Set Field in Current Item' in the workflow, then the error does not occur. However, the 'Set Field in Current Item' in the workflow is required.
Please provide solution to this issue ASAP. Your reply will be greatly appreciated.
Thanks in advance

Hi Jack,
A shot in the dark here. I'm not convinced the error is from the workflow. What is the definition of the list item column in SharePoint? Have you set the column to requiring a unique vale? Look at the column definition.

The below error occurs when are opening group policy management editor kindly suggest me what to do

Problem signature:
Problem Event Name:                        APPCRASH
Application Name:
mmc.exe
Application Version:
6.3.9600.16384
Application Timestamp:                     5215ef8f
Fault Module Name:
jscript9.dll
Fault Module Version:                        11.0.9600.17031
Fault Module Timestamp:                  530882eb
Exception Code:
c0000096
Exception Offset:
0000000000075a36
OS Version:
6.3.9600.2.0.0.272.7
Locale ID:
1033
Additional Information 1:                  ec0f
Additional Information 2:                  ec0f4898764fec44122dfe96fc36b0dc
Additional Information 3:                  4f6d
Additional Information 4: 4f6db505997e7dc082983dd077416716

Hi,
Would you please let me know edition information of the server where this issue occurred? Was it SBS 2011? Did
you remember which operation you had done before this issue occurred? For examples, install updates or third-party applications or any other?
On current situation, please run
sfc /scannow command to scan all protected system files and monitor the result. Please also check if all necessary Windows Updates were installed.
By the way, did you encounter any issue when open and use IE?
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Unable to install itunes and quicktime both error occur: system cannot open signified folder

my pc's specifications are : dual core processor, 1 gb ram,windows xp sp2 (os), 300gb hard disk

I have just found a way of sending some feedback to
Apple.
Will be interested to see what they say to this>>
I find it ridiculous that the cost of these ipods
does not include some on line support from Apple. We
have to try and rely on other users in discussion
forums. All I am finding is there are loads of others
on thee forums with similar problems unable to find a
solution.
Please advise.
Also found a number for 'tecnical support' after 5
days trying....
0870 876 0753
Will give them a 'polite' call tomorrow!!!!
Thanks for the phone No. I was having a problem with Quicktime which I couldn,t resolve by checking the discussion forums but that phone No. was a great help. Alhough you are talking to a call centre somewhere in the world and have to be careful with the language difficlties it was a help and it,s a shame Apple don't make this No. more easily available, so well done for finding that No.
You can go days or even months for a solution and I think Apple should have an online Tech. expert to help out.
Dell Windows XP Pro
Dell Windows XP Pro
Dell Windows XP Pro

Error occuring when opening file programatically?

I am trying to create a directory(ok) and then create a file from information obtained from a program(error). In this example i am calling the directory C:\TESTDATA\`serialnumber`\`type of test` and the file called `date``operator`.xls
However once the directory is created, an error occurs when i open the file to write my table into?
Can anyone help?
Thanks
Attachments:
test.llb ‏77 KB

Hi,
Can you do two things to help us help you? First, save your vi's using the "Save with options" selection "Development distribution", as some us don't have the OpenG libraries installed, and two, give us the error code/message you are getting.
Thanks
P.M.
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

FYI TDMS open and read on empty file gives no error's out

I found that if you 'open' an empty (0 byte) file using TDMS open, you will not get any error messages when you open it, nor when you call functions such as "Get properties" or "List content", also no error when you close the TDMS file.
If the file is non-empty, but not a valid TDMS file, TDMS open returns an error.
I would have expected that I would get an error or a warning at least when trying to read a non-existant property or group, if not by the open function itself?!
The 2013 snippet below creates a 1-byte or empty file in the local user temporary folder, closes the file, then attempts to open and read it as a TDMS file. The temporary file is deleted afterwards.
If the file is empty, NO errors or warnings occur at any point. If the file is not empty, it fails on the TDMS open. (Note the sequence structure is because the path out of the tdms close is invalid if the tdms open failed.
This could conceivably cause an issue if your program does not do additional fault checking to catch existing but empty files. (Which of course shouldn't ever happen, but in some situations it could happen.)
QFang
CLD LabVIEW 7.1 to 2013

Hooovahh
I asked to list the channels in a named group. If that named group did not exist, I would think that should at least be a warning, but I could see how it should not be an error, it was just unexpected to me that reading a non existant group (in an empty file) did not indicate any issues at all. To me, 'error out' should give a warning or an error if something unexpected happened, but I may just have stricter opinion on something that by nature is very philosophical and open for debate. (And there are always tradeoffs, overt checks and bounds in a function obviously leads to overhead, and TDMS is optimized for performance, so that may be one reason it is the way it is.)
(This situation came up for me because when a file is first created, we datetime tag it and write a bunch of other meta-data to the file, then later (and over time) we add the spectrum goup + data. [Edit] actually, in the old code, if the file existed, it was assumed to have been setup correctly. so if the group exists, the old code assumed all the meta data has already been written [end edit].. One of the many fixes possible, I'll rely on the 'found' boolean output of the parameter read instead of relying on the error/warning. If the datetime tag is found, the code will asume the file exists and has been filled with the meta data I expect.)
Thoult :: I wasn't sure, but in either case, my intent was to provide extra information, not 'knock you' for participating in the discussion, I hope thats not how I came accross. English is a second language to me, so I sometimes come across 'wrong' from what I mean.
QFang
CLD LabVIEW 7.1 to 2013

"Unexpected Error" opening Diadem TDM files

A little background. I work in test area where we deal with several different data acquisition systems and, therefore, several different raw test data file formats. One of those data types is NI/Diadem TDM files. I have developed a single raw data loading function, using MATLAB, to handle the importation/reading of all of the different data types. For the TDM files, I am utilizing the nilibddc.dll library (provided by National Instruments) to open/read the data files. When I run the MATLAB code from the MATLAB development environment everything works fine. This is the good news.
The bad news happens when I compile the MATLAB code and try to load TDM files into MS Excel. What I am doing is using MATLAB’s compiler/deployment tool to create a generic COM dll (called MATLABLoadDataFile.dll). I am then referencing MATLABLoadDataFile in an Excel add-in which obtains raw data file name(s) from the user, and calls the single raw data loading function to load the data into Excel. This allows the users to easily import to Excel, all of the different file types we deal with. When the raw data loading function is called in MATLABLoadDataFile, an error occurs (-6204 “Unexpected Error”) when the DDC_OpenFileEx function is called. I have included several debugging statements in the MATLAB code to try and track down what is going on. The findings….the nilibddc.dll appears to successfully load with MATLAB’s loadlibrary command. All 135 functions in nilibddc appear to be available. When DDC_OpenFileEx is called, the code -6204 “Unexpected Error” is thrown, and the load data file function is exited (via error checking code I wrote in MATALB) without loading any data.
Now, more good news (I guess). The above behavior is only experienced on my development machine, and (so far) one end-user. After I deployed the data loading Excel add-in to several (approx 5) end-users, I discovered that the TDM data loading function worked perfectly, without any errors being thrown. The sixth end-user, unfortunately, experienced the same “Unexpected Error” I receive on my machine. I have dug deep into several things to try and determine the common thread between my machine and the sixth user without any luck. I have checked system path statements, MATLAB path statements (if installed ), registry entries, and component install sequencing (I ran the same msi installer package for all end users). Before I continue further which the deployment, I would like more information on how/why the “Unexpected Error” occurs.
FYI, all of the computers are running 32 bit Windows 7, MS Excel 2007, & MATLAB r2010a (some machines have it installed already, and some do not. The MATLAB Compiler Runtime Library was installed on all machines to run the compiled MATLAB code. The 2 “problem” machines are different in this regard, as are the 5 “good” ones, so no common thread).
Any help or suggestions will be greatly appreciated. If this is the wrong forum for this question, please let me know, or forward to the correct one. Thank You.
Solved!
Go to Solution.

Because the whole ddc system is based on dynaic library loading I would assume that one of them fails.
http://www.dependencywalker.com/
offers a tool depends.exe.
After starting it load the program (matlab.exe) to it and use the menu entry
Profile->Start Profile
The application will log all LoadLibrary and GetProcAddress entries and so on.
Have a look for red entries that might be related with ddc lib and ni usi.
A potential clash could be xerces or an installed NI-Excel Addin.
Could you check and come back with some information.
Greetings
Andreas

TDMS file error occurs after several hours

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?

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.

TDMS Open error -2519 on CompactRIO

I have a cRIO-9073 controller on which I am streaming analog input data at 40kHz from a 9215 module into a local TDMS file. Data collection is triggered via a switch on a front panel -- turn the switch on and it starts recording the A/I data and streaming to disk, turn the switch off and I shut down the A/I and close the TDMS file.
Everything seems to work fine but occasionally when I turn on the data collection switch I will get an error -2519 (LabVIEW could not load the TDMS file component) from the TDMS Open call. If I turn off the data collection switch, then turn it back on, the next call to the TDMS Open function hangs and never returns.
During this time I can see that other functions in my VIs are continuing to execute (other lights & values on my front panels continue to update), but I cannot stop the VI from within Labview on my windows development system -- hitting the stop button doesn't do anything. It seems that the only solution is to reset power on the cRIO controller.
Does anyone have any more details about this error -2519 or ever seen any problems with the TDMS Open function hanging?
Thanks,
AJ

Just to add a bit more information, I was having a similar problem except the application (both Labview dev environment and the app executable) was crashing. Searching Window's application log turned up this notice:
Faulting application name: LabVIEW.exe, version: 10.0.0.4032, time stamp: 0x4c24f059
Faulting module name: tdms.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c91c585
Exception code: 0xc0000005
Fault offset: 0x3505eff8
Faulting process id: 0x1e4c
Faulting application start time: 0x01cbbdc6da377ab1
Faulting application path: C:\Program Files\National Instruments\LabVIEW 2010\LabVIEW.exe
Faulting module path: tdms.dll
That exception code is an invalid memory access error. Looks like tdms.dll was being unloaded in the brief time between closing a file and opening a new file but LV didn't quite keep up. In any event, the workaround Herbert suggested stopped the crashes.

TDMS open problem

I have a TMDS file but every time I try to open it it gives me the error 2500. I tried to solve it with TDMS Defragment.vi, but I don't know if I'm using it correctly or if it doesn't work.

You might want to try deleting the *.tdms_index file and then open the *.tdms file again.
If that fails, we might need some more info, e.g. how big is the file, what does it contain, what app was it recorded with.
Herbert

"TDMS Open.vi" won't open file if not administrator

I have an app that I install and run from a subFolder of the program files folder, and there's a TDMS file that installs alongside it (it's a set of pattern match data that the app needs). When the app calls "TDMS Open.vi" everything works fine if I'm logged on as an administrator, but I get an error 8 (file permission error).if I'm not.
When I'm not an admin, I can run the exe that's in the same folder - why can't that exe then load the TDMS file? What am I missing here?
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

Ben wrote:
crelf wrote:
Why do I feel like I'm having an ACME Do-It-Yourself conversation?
That's because you are used to LAVA. We have trouble spelling TDMS or LVOOP on this forum.
At least someone's watching Thanks Ben!
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

Problem opening multiple .tdms files in subroutine

Heya-
I'm using LabVIEW 8.2, professional development system.
I'm using the Open / Read / Close TDMS functions as part of a subroutine in a larger program. The subroutine is supposed to open one of several TDMS files (each of which contains bulk data saved previously), extract the data, then restructure into a 3D array, which is passed back to the main program. The particular file TDMS file to open is controlled by the main program. The TDMS Close function is used after the data is extracted.
When running solo, the subVI performs as expected. When running as a subVI, it functions fine on the first call, but subsequent calls to open different data sets fail to actually open the TDMS file (or at least, the Read TDMS function generates an empty array). However, returning to the orginal file that was opened, the subVI works fine - it opens the TDMS file. It doesn't matter which file was intially used - whichever one was opened first functions fine, any others do not. That would make me think that the first TDMS file isn't being closed, except that I am using the Close TDMS function after reading.
Attached are the subVI (TDMS_to_3D_array), a quick test program that uses the subVI, and a .zip of two data sets
Not sure if the global variables located in the SubVI will default, so they are: UpperMaxCol: 55, UpperMinCo: 0, UpperMaxPixel: 48, UpperMinPixel: 6
Thanks in advance for the help
Dan
Attachments:
Data.zip ‏1060 KB
TDMS_to_3D_array.vi ‏54 KB
TDMS_loadfault_tester.vi ‏39 KB

Hi Dan,
Perhaps you would try a few things.
Use the TDMS Flush VI in the subVI before the TDMS Close VI.
Try running the program with the subVI open.
Wire the TDMS File refnum from the subVI back to the parent and observe its value as the program switches between TDMS files.
Perform the TDMS read in the parent VI, wire the TDMS Data and the Array Size of the TDMS dataset to the subVI. Does this make any difference?
Try the subVI without the Channel Name string indicator.
Include error cluster wires throughout the entire subVI. Wire them through the TDMS VIs, then through the nested For structures, and then back to the parent VI.
Let us know what happens.

Error 6 occurred at TDMS Open in TDMS

Similar Messages

Maybe you are looking for