06-09-2020 03:49 PM
RavensFan the original poster did respond - see my ~2pm post. The problem could be very rare. Of course there could be many more folks that have had the problem and just don't post to a forum - or post to a Forum you read (e.g., versus a Windows forum).
A1Penguin, you might consider trying to use the Windows Alert system to track down what is changing the permission settings. I'm not familiar enough with the system, but I found this.
Steve
06-09-2020 04:14 PM
My colleague ran into this issue a few weeks ago. It was resolved, but he's not here right now for me to ask how.
06-09-2020 04:37 PM
@maherhome wrote:
RavensFan the original poster did respond - see my ~2pm post. The problem could be very rare. Of course there could be many more folks that have had the problem and just don't post to a forum - or post to a Forum you read (e.g., versus a Windows forum).
A1Penguin, you might consider trying to use the Windows Alert system to track down what is changing the permission settings. I'm not familiar enough with the system, but I found this.
Steve
I'm sorry. I had not seen your follow up message.
Also, I do respect my local IT support who is a pesonal friend. But I also know that he will be quick to claim a problem is in a piece of software he doesn't know. Even when some IT policy changes some mysterious OS settings without them fully understanding everything that is impacted.
To IT people, they think every problem is "user error".
11-09-2021 12:05 PM
"My colleague ran into this issue a few weeks ago. It was resolved, but he's not here right now for me to ask how."
How did he resolve this issue, labview changing the permissions of files to one owner and no one else can use it?
11-09-2021 12:20 PM
@ReturnoftheWolf wrote:
"My colleague ran into this issue a few weeks ago. It was resolved, but he's not here right now for me to ask how."
How did he resolve this issue, labview changing the permissions of files to one owner and no one else can use it?
Err... he retired, and I never got around to asking him. 😞
11-09-2021 12:39 PM
Just for the record, since there is some new activity on this thread, I am still suffering with this issue. We do have windows work groups due to corporate security concerns. Every time this happens, I need to get someone with administrator privileges to reset the privileges on the file. About half the time I just give up on the load file and open the top level VI directly, which I would prefer not to do. The rest of the time, I need to be in the project. Sometimes the system administrator is not readily available. I have pretty much given up hope of ever getting this resolved and am also just hanging on until retirement. 9 years to go 😉
01-05-2022 01:24 PM
I am also having this issue at my company. We work around it by fixing the permissions on the project file as needed. It's a 30 sec fix so we quit trying to find root cause.
01-05-2022 08:10 PM
My goodness -- have you never heard of Version Control Systems, things like Subversion and Git, systems? Even with a single developer (me), having the "latest version" safely residing on the VCS Server, I can go home, open my laptop (I can't carry my desktop, monitors, etc. home with me), update my copy of the code I just committed to the Repository, and continue working "with the latest version". [I do need to remember to Commit my evening's work back to the Repository before leaving for work ...].
This works really well for groups of programmers as well. I advise looking into this.
Bob Schor
01-05-2022 08:28 PM
My typical routine is to commit changes at the end of each workday. There should be no need to delete and copy back from repository every day. Only one system so only one developer can access at a time (typically via remote desktop). Also, project is huge and takes > 5min to copy across the network.
Would like to figure this out but IT says it shouldn't happen and NI says
labVIEW isn't changing permissions. 🙄
01-05-2022 08:55 PM
@A1Penguin wrote:
Just for the record, since there is some new activity on this thread, I am still suffering with this issue. We do have windows work groups due to corporate security concerns. Every time this happens, I need to get someone with administrator privileges to reset the privileges on the file. About half the time I just give up on the load file and open the top level VI directly, which I would prefer not to do. The rest of the time, I need to be in the project. Sometimes the system administrator is not readily available. I have pretty much given up hope of ever getting this resolved and am also just hanging on until retirement. 9 years to go 😉
Is it newly created files/folders only, or is it actually changing permissions on existing files?
I can't speak for exactly what you are seeing, as I haven't done development in the sort of (frankly strange sounding) environment you are describing, but I have had issues deploying apps where it seemed like files didn't have the inherited permissions I thought they should. This was on creation/deployment though; I haven't experienced issues with existing files somehow changing permissions.
Actually though... I don't remember if it was files I created in LabVIEW itself I had issues with, or ones deployed with a LabVIEW built installer. When I have a little time, maybe I'll try creating a quick test to see if I can duplicate what I'm talking about.