File permission issues when sharing project

[maherhome]

Hi,

We are sharing a project amongst two developers that each have an account on a (Windows 7) machine. They are part of a windows group and don't develop at the same time.  All directories and files are in the group and are set to inherit permissions.  After one user develops using Labview, all the files that he saved when using Labview have the group permission removed and the second developer can no longer open the files.  Our sys admins claim Labview is somehow changing the permissions.  Has anyone seen/overcome this?

Thanks,

Steve

[RavensFan]

Where is the file being saved?

If both users have full access to the directory where the files are being saved, there shouldn't be any problems.  I'm sure LabVIEW isn't doing anything to change access rights.

I'm concerned about the comment "part of a windows group"?  Most PC's in a corporate environment are part of an actual network domain, and don't use that poorman's excuse for network access rights of a workgroup that Windows seems to want to use for standalone PC's and those not registered onto a network.

[maherhome]

Where is the file being saved?

No place special.  We have a labview project/ directory under our own directory under C:/ that roots all the Labview project files.

If both users have full access to the directory where the files are being saved, there shouldn't be any problems.  I'm sure LabVIEW isn't doing anything to change access rights.

Both users have full access.  If I create a new file it has the correct permissions (a local group).

I'm concerned about the comment "part of a windows group"?  Most PC's in a corporate environment are part of an actual network domain, and don't use that poorman's excuse for network access rights of a workgroup that Windows seems to want to use for standalone PC's and those not registered onto a network.

I wouldn't be too concerned 😃  We have a nationwide federated domain.  The "group" is a local group on the computer for two people specifically to share this labview project.

Steve

[Bob_Schor]

I've just done this "by hand" for some programs we develop that we want "all users" who log on to the computer to be able to use.  I did a search to see if there was a "better way" (i.e. a programmatic way) to do this, and came across the following, which might be a (partial) solution:  http://forums.ni.com/t5/LabVIEW/File-permissions-same-old-story/m-p/2393792#M742019

[maherhome]

Thanks for offering, but it doesn't really apply to my situation (I'm mostly dealing with RT and FPGA files that can't access host file permissions).

I don't really understand why this is happening; it appears Labview is actively foregoing file system configurations and stripping away permissions.  To what end?

I see my only approach is to write a script that will reset file permissions before/after users work on their files.  

Steve

[A1Penguin]

I realize this is a very old post.  I was wondering if you ever got resolution on it.  The same thing has been happening to me for the last several years.   As soon as we bring in a new user, the project file and possibly a few other files have their permissions become set so that the new user owns them and others can not load or copy them.  Our IT people claim that LabVIEW is doing it as well.

[RavensFan]

Well, nothing has changed in the last 7 years.

I still don't know how you think LabVIEW could cause a new user to take "ownership" of a file.

The same questions still apply:

1.  Where are these files saved?  (local drive, network?)

2.  Are users all logging onto the same PC, or from different PC's?

I don't put much faith in things IT people say.  They aren't familiar with LabVIEW.   And when they don't understand something, they will always blame it on the other software.  It is never THEIR stuff that causes issues.

[maherhome]

We ended up giving up and having each user have their own sandbox.  We (carefully) updated the users through git.

We have an extensive hierarchy of security layers (DHS) - I can only guess there was some subtle interaction there.

With all due respect RavensFan, I get a chuckle out of "I still don't know how you think LabVIEW could cause a new user to take "ownership" of a file".  As if all computer bugs can be reasoned a priori  😃

We have excellent IT support and I put much faith in them.  Of course, they're not familiar with LabVIEW details but they sure are familiar with file systems and OS bug reports and system issues and bug patterns from hundreds of applications.  You should respect your IT support - they can save your bacon.

Steve

[A1Penguin]

Thank you for your fast reply. 

The files are saved in C:\\test executive\revision x\

All users log into the same PC. 

As far as I can tell, it only happens the first few times a new user starts working on the project.  That user gets the ownership and all others can not access the file.  It appears to be mainly the project file.  The main VI can be opened outside of the project. 

I have never seen this happen to any other files besides LabVIEW.

It may very well be IT's stuff that is causing the problem, but they are denying it and I need to start somewhere trying to figure this out.   You do realize that I am NOT the same person who posted originally?   I am yet another user from a different company who is experiencing the same thing.

[RavensFan]

---

@A1Penguin wrote:

It may very well be IT's stuff that is causing the problem, but they are denying it and I need to start somewhere trying to figure this out.   You do realize that I am NOT the same person who posted originally?   I am yet another user from a different company who is experiencing the same thing.

---

I do.

But you are just the second person in 7 years to claim to have an issue.  (Mind you most people probably don't share things the same way you are, multiple people using same PC.)

The original poster never came back to claim whether they solved the problem or not.

I suspect it is a Windows permissions issue.  If all users have permissions to read and write to a particular directory, then there is no reason for any particular user to be locked out no matter who the owner of the file is.  The only thing I can think of is if when a user has the project file open, Windows puts a lock on it so someone else can't use it simultaneously.  And perhaps there was a LabVIEW crash that kept the person who had it open from properly closing it, and/or saving it, so the operating system still has a file lock on it.  I know we do see this happen from time to time on AutoCAD files that are saved on a network directory.  But that has nothing to do with ownership.