tdms.dll error loading file in DIAdem

[Joe_Gerhardstein]

I'm trying to load a TDMS file written in LabVIEW 2010 into DIAdem 2010, but receive the attached error indicating an ACCESS VIOLATION in tdms.dll.

I have several machines that this file loads into DIAdem 2010 fine on, but of course the one I need it to work on is the only one that it doesn't work on.

The machine in question has a "fresh" install of Windows XPSP3 with minimal other stuff installed (it's a Dell Optiplex GX620, if that mattters).  As mentioned, the file loads fine on several other machines with DIAdem 2010 on it.  The machines that it works okay on are running Windows XPSP3, XPSP4 and Win7 (all Dell machines).  I have attached a list of installed applications on the PC in question.

Any one have any thoughts?  Are there any programs that are incompatible with DIAdem?  Are there any installers that DIAdem (or tdms.dll in particular) depend on that need to be installed also?

[AndreasK]

Could you please compare the tdms.dll version on the sytem that works and the system that does not.

Could you please compare the tdms.dll version on the sytem that works and the system that does not.

Option Explicit

dim fsi : set fsi = CreateObject("Scripting.FileSystemObject")
dim wsh : set wsh = CreateObject ("WScript.Shell")

On Error Resume Next
dim niSharedDir  : niSharedDir  = wsh.RegRead("HKLM\Software\National Instruments\Common\Installer\NISHAREDDIR")

dim tdmsDirRef       : tdmsDirRef       = niSharedDir & "tdms\"
dim tdmsVersion : tdmsVersion = fsi.GetFileVersion(tdmsDirRef & "tdms.dll")

msgbox tdmsVersion

[Joe_Gerhardstein]

The ones that work are all 2.2.1546.609.  The one that doesn't is 2.2.1496.920.

Is there a way to update this?  Can I just copy the DLL across, or are there other DLLs that need to be updated at the same time?

[Joe_Gerhardstein · Accepted solution]

I copied the newer DLL over to the machine that didn't work, and that seems to have fixed the problem.  

Does LabVIEW 2010f2 install a newer version of the DLL than DIAdem 2010 does?

[AndreasK]

There is an update installer at

http://zone.ni.com/devzone/cda/epd/p/id/3008

There is an update installer at

http://zone.ni.com/devzone/cda/epd/p/id/3008

Better put back the old version and run the installer.

Takes you to the safe side for future updates.

[Joe_Gerhardstein]

So, before you provided the link to the updater, I did a search on USI (which I believe is the underlying driver for TDM/TDMS) on the driver update page (http://www.ni.com/drivers/).  Any idea why this patch doesn't come up?

[AndreasK]

In this case it is a two layer access.

In this case it is a two layer access.

tdms is an own component. If the native tdms VI's are used LabVIEW does not access USI.

DIAdem access tdms by USI.

In this case it is a two layer access.

tdms is an own component. If the native tdms VI's are used LabVIEW does not access USI.

DIAdem access tdms by USI.

So in this case only the tdms component is updated/fixed and USI just makes use of the new

TDMS component. So USI does not change at all.

In this case it is a two layer access.

tdms is an own component. If the native tdms VI's are used LabVIEW does not access USI.

DIAdem access tdms by USI.

So in this case only the tdms component is updated/fixed and USI just makes use of the new

TDMS component. So USI does not change at all.

Its a dependence graph.

DIAdem depends on USI

USI depends on TDMS

[AndreasK]

I feel like an echo 🙂

I feel like an echo 🙂

Does not like my browser

I feel like an echo 🙂

Does not like my browser

browser

I feel like an echo 🙂

Does not like my browser

browser

brow

I feel like an echo 🙂

Does not like my browser

browser

brow

b

I feel like an echo 🙂

Does not like my browser

browser

brow