Copy File Action Error

I'm trying to copy a file to a network location over a VPN (Copy File(s) action).  It fails every time with close to 100% of the copy complete in FB.  Note that I recently moved to Windows 7 and updated to the latest FB 6.3.0.1916 in the last few months, so I can't test with the previously working configuration, but I know the FB project itself is the same as what used to work.

The error I always get is:

Filed to copy File : C:\Local\Path\File-2010-03-23.zip -> \\server\data\path\deploy\File-2010-03-23.zip
Win32 Error : The specified network name is no longer available

The two paths it actually uses (from the log) are fine, and a file does get copied over, it is just incomplete and thus corrupt.

Copying the file manually using Explorer works fine and using the FB xcopy action also works fine, so I assume some kind of bug in the copy files action, but I'm not sure.  It isn't a big deal, since xcopy is a perfectly usable workaround for me, but I thought I would at least report the issue in case others are seeing it as well.

Hi Erik,

Do you have the same problem if you map the network path before copying the file using the Map Network Drive?

Regards,
Paul.

It appears to work fine if I copy to a mapped drive. That said, it also then worked with the network name, so I’m not sure what this means. If I unmap the drive, copying to the share name seems to fail again, sometimes completely disconnecting the VPN. I’m going to write this off as a Windows quirk and just use xcopy or a mapped drive, since those seem to work just fine. Thanks!

Hi Erik,

I was talking to Vincent about this and he said that he often sees the same thing when copying files across the VPN here, even when just using Explorer to copy the files. Using XCopy or Robocopy should be more reliable.

Regards,
Paul.