"File in use" issue

[topraka]

Hello:

A colleague is creating an application on his computer and placing it in a shared folder.

When I try transfer the file through the company network to the deployment computer, I get a message to the effect that some of the files are in use, and the transfer does not take place.

Colleague's LabView is shutdown.

How could I resolve this issue?

Thanks,

Ahmet Toprak

[voraciousniuser]

Hi Ahmet -- There are a couple of things that you can try:

Depending on what kind of file your collegue is creating, check to see if the application that opens it by default has the document open (For ex. when you do report generation and send out an excel file and that file is open in excel you will get this error)

The easiest solution is a restart of windows and it would most probably fix your issue.

Thanks
VNIU

[Dennis_Knutson]

Are you trying to replace something on the destination computer? Is it a VI, exe, DLL? Any of those loaded or running on the destination?

[topraka]

Thanks for the advice. We did reboot the computer a few times but it does not help.

Ahmet Toprak

[topraka]

The short answer is "no".

Ahmet Toprak

[Dennis_Knutson]

You OS obviously thinks some of the files are in use at the destination so a little more information is called for. Are any of the files names given? What are they? Any services like datasocket or the web server running on the destination?

[topraka]

I solved the problem, sort of that is:

Installed the full version of the LabView on the target computer.

Direct responses to your questions: The file names are:
- create data string 1.vi
- get 2000 proof date_time 1.vi
- Untitled.vi

There is nothing special running on the development computers. (I later involved another colleague who also had the development environment. Same problem with his computer as well.)

From both development computers I was able to transfer other files without any difficulty.

Thanks.

[Dennis_Knutson]

I'm glad you got it to work but I still don't understand why it failed. Without LabVIEW on the target pc and without LabVIEW running on the pc's you were copying them from, I don't understand what could have been in use. From the file names, they sound like VIs that someone developed and are not part of the LabVIEW distribution so they couldn't be anything the LabVIEW environment would be aware of.