File access permission denied

[Double_D]

I occasionally have problems building a CVI project due to an error of the following type:

Failed to copy z:\CVI Projects\SCPI_Test_6485\cvibuild.SCPI_Test_6485\Debug\SCPI_Test_6485.exe to z:\CVI Projects\SCPI_Test_6485\SCPI_Test_6485.exe. File access permission denied
Build failed.

I most recently saw this with CVI 2013, but I have also seen it with CVI 2012.  I tried to delete the executable, but I received a message from Windows stating that the file was in use by another process (this was after closing CVI).  I didn't find an obvious entry in task manager for the process that had the file open.  After logging off and then back in, I was able to build the project.  I noticed that there was an old entry on this topic from 7 or 8 years ago.  Has anyone one seen this problem with newer CVI versions and WIndows 7?

[Jason-H]

Hi,

First, could you please post a screenshot of the error messages? You might also try running LabWindows/CVI as Administrator if permissions are an issue. I have a few questions that might help us determine what is going on. Can you replicate this issue on another computer? Has the application only recently begun to show this behavior? If so, what has been changed or  added? What is this application doing?

[Double_D]

I can post screenshots the next time it occurs (if I remember).  I have seen this problem on at least a couple of relatively small CVI projects.  It is an intermittent issue, not repeatable by any sequence of steps that I am aware of.  The applications typically involve GPIB communication with an instrument - trigger the instrument, take a reading, etc.  I am currently running CVI 2013 on a Win 7 64-bit machine.  I'm pretty sure that I also saw this on an XP box running CVI 2012 as well.

[Jason-H]

I know that this error can happen when files are trying to be saved in Program Files. Have you checked the permissions for the z drive? When this issue occurred on the XP machine, did it have the same or similar hardware setup?

[Double_D]

I use the Z: drive every day to save data.  I checked the permissions and I have full control.  The XP box did have a similar setup to my current machine. 

[Jason-H]

Is Z a local or network drive? If it is a network drive, I would suggest saving the project locally and recompiling to see if this issue still occurs. Do you have some form of source control? If so, what is it and is it set to automatically back up? It may be accessing it to push it at the same time you are trying to access it. In that case, disable the source control and check for the error. Another thing to check would be an anti-virus or firewall. It may be that one of these is intermittently keeping you from accessing these files.

[Double_D]

Z: is a network drive.  The problem doesn't occur often enough that I want to move the project to the local drive; it is more of an occasional nuisance.  As for source control, I use TortoiseSVN.  I don't know that this does any kind of automatic backups, but I suppose that it is possible.  I will try to disable antivirus and/or firewall software the next time this occurs to see if that solves the issue.

[Double_D]

It looks like this problem may be caused by the Windows Indexing Service running on the server.  Other users have had similar issues with other types of files.  I will continue to monitor the issue.

[wuchunc]

Hello There,

Is there any follow up on this issue? I often run into the same problem while CVI was almost done compiling my project and at the final linking stage, the program responded "Failed to copy (the exe file). File access permission denied. Build failed."

Sometimes, I can just exit CVI program then re-launch CVI to get a successful build. Other times, I will need to re-boot my Windows and re-launch CVI to make this work.

I am running LabWindows CVI 2015 on Windows 10 on a Dell XPS9360 laptop with SSD and file index off. I also found out that when this issue happens, even after exiting CVI program, I could not delete the exe file in question from Windows either.

[AvatarAang]

Hello, if you are running into this issue I would recommend posting a new thread and linking back to this one. That way you will get more user traffic over your post.