TDM vi's work in Admin account, but not Limited user

[minnellac]

I have an app that I wrote using the TDM VIs that works perfectly in the development environment and as an executable in an Admin account in WindowsXP. I am trying to deploy the app for use in a limited user account, and I am getting an error about an unrecognized file type. Is there a way to enable this functionality?

The VI is used to create a file map of a custom TDM file that was created using the TDM header writer VIs. I've included the VI and the executable in the archive, as well as a sample file to read (select the .tdm, not the .bin in the path control when running the program).

The actual error text is:
Error -2564 occurred at Open Storage

Possible reason(s):

LabVIEW: The software installed on this computer does not support the file format you requested. The Storage VIs access files through plug-in libraries LabVIEW and DIAdem install. Visit ni.com to download the library you need.

Thanks,
Chris

[rsw]

Hi Chris,

You may find the following KB useful:

http://digital.ni.com/public.nsf/allkb/B2045400ECC627F1862571EA005A6B6E?OpenDocument

With that installed your program should work, if not please let me know and I'll look into it further for you.

[minnellac]

The NI-USI components are installed. I should have been more clear. I've tried my depolyed application on another system without LabVIEW installed (but, obviously, with the run-time). It works fine as an admin user, but not as a limited user.

Thanks,
Chris

[rsw]

Hi Chris,

Sorry, I fully understand your issue now and am currently looking into it, just out of interest you do also have the checkbox marked for "Storage VI's Support" in your installer? I've found nothing with specific issues with XP security and using these VI's so far but will continue to look into it and attempt to replicate the problem

Thanks,

[minnellac]

I can't look at my actual project file (and build specifications) at the moment, but I don't remember seeing a checkbox for including Storage VI's Support. Where exactly is that? I have checked the additional installer to include the NI-USI Support.

Chris

[Matt_W1]

If possible you could try the tdms file format (easy to convert back a forth to tdm if needed). I believe the tdms functions use a different method than tdm for writing the files, so they may not have the same problem.

Personally I prefer tdms over tdm since the TDM functions need to use the UI thread to write data (may not be the case now, but was true when tdms first came out), and I find the API for tdms more pleasant.

Matt W.

[minnellac]

The TDMS VIs probably are better, but I started this project before they were available, and I spent a considerable amount of time with the TDM Header Writer VIs to create my file format. I don't use the TDM VIs to write the files; I do that all with my own binary format that is fast and efficient. I also stripped out all the extraneous gunk that the TDM files like to put in, and customized the files with my own properties. Unfortunately, I am disappointed with the time necessary to read and write properties, but it's too late now to replace the whole system with a database backend.

Anyway, I'm hopeful that there is a solution to this problem. I doublechecked all the options in the installer and app build specifications, and I didn't see the checkbox for Storage VI Support. I have a fuzzy memory of this; is it possible that it existed in a previous version of the builder?

Chris

[rsw]

Hi Chris,

It may well have done, which version of LabVIEW / Runtime Engine are you using? I can then try to reproduce the issue on my machine and then find what/why it requires administrator account privelages.

Thanks,

[rsw]

Hi Chris,

One thing that I have come across is the lvStorage.dll, if you run a search for this on your machine to ensure it's installed all the packages correctly (which I'm guessing it has as this works under admin) and whe you find it, ensure that normal users have permissions to use it via right clicking on the dll > properties > security. If not you may need to add normal users. This is already setup on my own machine so I'm unable to verify that this is the problem, but it's worth a check!

Thanks,

[minnellac]

I'm using LV 8.5. Sorry I didn't mention it. That suggestion on the security setting of the lvStorage.dll seems like a good one. I'll check it out when I get back to the machine. I know that dll is included in my build, but I'm not sure what the security settings are. I'll play around with those settings when I get a chance. I just checked the test app that I sent, and the settings for the dll match those for the exe.

Thanks,
Chris