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

[rsw]

Hi Chris,

No problems, let me know how it goes and if that still doesn't help I will look into it further for you,

All the best,

[minnellac]

I checked the security settings for each of the three LV dll's that are included in my project. They are all identical, but I don't appear to have any problem accessing lvanlys.dll or niTdmHW1_0.dll. I tried adding read and execute priviledges to "Everyone" for lvStorage.dll anyway. It didn't make any difference.

While I was in the limited account looking at these things in Windows Explorer (the limited account still had the default Tile view set) I noticed that there is metadata associated with the other two dll's (see image). This may not be significant at all, but to me, it indicates that the three dlls were not all created the same way. Is it possible that some care needs to be taken when creating a dll to make it accessible to Limited Users, or to guarantee that any other libraries that are dynamically accessed by the dll also have those priviledges?

Anyway, I'm looking forward to getting to the root of this.

Thank,
Chris




Message Edited by C. Minnella on 01-08-2008 10:05 PM

[rsw]

Hi Chris,

Thanks for getting back to me, I've been looking into the DLL's you list and can see no information on our internal support regarding issues with them, if the permissions are set correctly then they should run fine. I am still trying to replicate the issues your having here, as no machine currently exists on the network with local login to a restricted account this is something I shall setup today, I will also have a chat to our System Engineers here to see if they have ever come across this permissions error.

I have 1 final thought regarding this and I'd be grateful if you could try, it's in regards to the tdms file itself. Where are you reading it from? (path wise, i.e. My Documents or c:\) and also could you check the permissions of this file also to ensure normal users have access.

Hope to get an answer back to you before mid afternoon,

All the best,

[rsw]

Hi Chris,

If the above path & permissions of tdms files ideas havn't worked,

Just had a word with our system engineers here any there is a minimum user level required to run a labVIEW program that communicates with TDMS, the lowest group they know of under Windows that will work (but still prevents users from being able to create new accounts) is power user. If it works under power user and admin and not under restricted user then I'm fairly certain this is the problem. In which case it's not possable to read the tdms files as a restricted user.

Hope this helps,

[minnellac]

The TDM file is being read from under the user's local settings directory. I'm an sure it is accessible because in the actual program, I actually create the file just before attempting to read it back and generate the file map.

I'm not sure if the customer will accept having the user set up as a power user, but I'll check into that. If you could confirm the behavior on your end with the files I sent, that would be helpful.

Thanks,
Chris

[rsw]

Hi Chris,

Sorry but all our lab machines are in use at the moment and I'm unable to use my own machine as it has administrator access, but due to security issues we're not advised not to add any extra accounts etc. I was told by a Systems Engineer who has 5+ years experience in LabVIEW that you do need minimum permissions of power user under Windows in order for all VI functions to work.

If you can wait until tomorrow I can get a lab machine built up for this purpose and check this for you, just to keep you updated. I understand your customers wish to use this on accounts with restricted access and hopefully I can find a workaround to the permissions problem with your particular VI's.

All the best,

[rsw]

Hi Chris,

A PC in the Lab came available, I have attempted to run your included VI as both administrator and restricted user and get back an error that relates to the following KB:

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

I know that you mentioned you installed items based on this KB which is why I'm a little puzzled to be getting this error, would it be possable to upload the source so I can debug this within the LabVIEW environment?

Thanks,

[minnellac]

The source vi for that app was in the zip. Did you receive that error when running the vi in both Admin and Limited accounts? If that is the case, does the lab machine have the NI-USI components installed? On a fresh (virtual) computer, I can run that app after installing the runtime and the usi components in an admin account.

Thanks,
Chris

[rsw]

Hi Chris,

Sorry I forgot the source was sent with the .exe in the zip file, the lab machines has ni-usi installed on it, I think it may be a bad ghost of the machine and am currently in the process of recreating the lab machine. I will let you know how I get on over the course of today.

Thanks,

[minnellac]

Thanks for your effort on this. I did confirm that the software functions under a power user account. I am probing the customer to see if this could be an acceptable compromise.

Chris