CopyFile to network drive fails in CVI 2017

[richferrara]

I have a LabWindows application that runs a test tool program for a radar system.  It accesses a RAM area on one of our radar processors as a network drive and attempts to copy files to it (CopyFile "filename.txt", "\\[IP address]\ram2").

This worked in CVI 2013.  In CVI 2017, it returns an error code of either -5 (invalid file name path) or -6 (access denied).

[mkossmann]

Are you able to copy these files manually using the the Windows GUI on the PC running the CVI2017 version of your tool ?

If that also fails, read about the changes in Windows networking  which were introduced by Microsoft for security reasons:

See https://support.microsoft.com/en-hk/help/4046019/guest-access-in-smb2-disabled-by-default-in-windows... and https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-by-default-in-windows.

https://support.microsoft.com/en-us/help/2696547/detect-enable-disable-smbv1-smbv2-smbv3-in-windows-... might be helpful, too

[richferrara]

Yes, copying them manually in Windows Explorer or at a command prompt works fine.

[Gaus]

Hi,

Try the following

CopyFiles ("C:\\path\\filename.txt", "\\\\[IP address]\\ram2\\filename.txt");

Jan

[richferrara]

It's too late for me to try anything, I already uninstalled CVI 2017 and went back to 2013 so that I can continue working on my project.  Perhaps someone at NI can look into this.  If it's a bug in LabWindows (which it seems to be), it's a big one since copying files is such a common and important operation.  There's nothing in the release notes to indicate that the behavior of CopyFile was changed on purpose.

[Gaus]

Hi,

I did the test using W7 and CVI2017 copying from local machine to a network file server without problems

Jan