04-25-2023 12:42 PM - edited 04-25-2023 12:55 PM
I am working for a company that has many old test stands, running LabVIEW version as far back as LabVIEW 8 on ancient PCs. We are contractually obligated to keep these old PCs and stay with the original LabVIEW version.
When I use the off-line installers for older LabVIEW versions, many do not install LabVIEW.ini, resulting in this message when I try to access Tools/Options (This message from LV2011, but other versions produce similar):
When I copy and paste LabVIEW.ini from another version of LabVIEW into the correct location, I still get this message, even when I set the file to let everyone have full access (Read/Write) to it.
Any help in correcting this setup would be much appreciated.
Solved! Go to Solution.
04-25-2023 01:19 PM
If LabVIEW.ini does not exist, it will be create on first launch with default entries.
The problem is not the location, but the permission. It is either the containing folder permission or the file permission itself. If you right-click the LabVIEW.ini file and look at properties...security, is there anything that stands out? Also make sure the ini file is not open in another application (e.g. ms word, etc.).
04-25-2023 03:53 PM
The ini file was not being created on launch, which makes me think the read/write permission issue is not due to security settings in the file, but rather in the folder where the ini file should be created. I will research that. Thanks for your help.
04-25-2023 04:17 PM - edited 04-25-2023 04:18 PM
Also see if it makes a difference if you run LabVIEW as administrator. (close LabVIEW...right-click...run as administrator).
04-25-2023 04:31 PM
Looks like it is a folder permission issue. I am trying to fix it myself, but may need to get IT involved. Thanks again.
04-25-2023 06:08 PM
Our IT department had write access disabled in all of the Program Files subfolders. I was able to go into the National Instruments subfolder and give all users "Full Control" access. This solved the problem.