LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

The message "the file xxxx.vi is not a vi" appears when the user changes from one XP login to another

We have an LV .llb file that starts and runs correctly when the user logs in under one user name in Windows XP. When he logs out and logs in as another user, that same .llb file gives the message "the file xxxx.vi is not a vi". An LV example vi runs correctly, so it doesn't seem to be a Labview problem (but not positive about that)
 
Any ideas?
 
Chuck Gantz
0 Kudos
Message 1 of 4
(4,465 Views)

Are there any differences in user privileges between the accounts? Is one user an admin while the other is just a general user?

This Knowledge Base looks right up your alley. Give it a try and let us know what comes of it. It was written in regards to Windows 2000, but it is probably valid for XP, too. Hope this helps!

Jarrod S.
National Instruments
0 Kudos
Message 2 of 4
(4,444 Views)

Hi Jarrod,

 

I tried doing the third option "Changing Permissions of LabVIEW Temporary DirectoryChanging Permissions of LabVIEW Temporary Directory" without success. I'm not sure I did it right because of the differences between XP and 2000. I dragged the temp folder in the allowed users local folder to the shared folder. When I go to the user that couldn't run the vi I still get the same problem. I was told that both users are set as admin.

I didn't try scenarios 1 and 2 because I didn't know what to do in XP. I may need to brush up on my XP security to try those.

 

Thanks.

 

Chuck Gantz

0 Kudos
Message 3 of 4
(4,433 Views)

Hi Chuck,

      You may want to confirm that the users who see problem, really are in Local-admins group for the workstation.

But instead of making everybody an Admin, I would log-in as Admin, then check/set permissions on the shared .llb, to give any "User" "Modify" (or even Full Control) permission to it.  Usually it's a permissions issue associated with specific VIs (the VI's retain their creator/owners permissions), but you might want to check the permissions on parent folders.  If you set Folder permissions (Users/Modify), don't forget to propagate settings to child objects!

Cheers!

Message Edited by Dynamik on 11-11-2005 05:21 PM

When they give imbeciles handicap-parking, I won't have so far to walk!
0 Kudos
Message 4 of 4
(4,428 Views)