Robocopy between two servers

I am having permission problems using robocopy to transfer files between servers.    We have a ftp server running Serv-U , which has an action on every file uploaded to the site to run a robocopy script to copy that incoming file to a different place.   The script has been running without issues for a long time when the target destination is a different drive mounted on the server (ie D: to E:).    Now we're wanting to copy the data to a different server, and I'm running into permission problems.    I've not been successful finding a solution via the Googleverse.  
My action on successful upload is to run:
C:\Windows\System32\Robocopy.exe D:\xxxFTPROOT\xxx\inbound \\xxxftptst\xxxftparchive\xxx\inbound $LocalFileName /log:D:\RoboCopyLogs\log.txt
where the ftp server passes in the $LocalFileName correctly.

The error details in the Robocopy log are :
-------------------------------------------------------------------------------
   ROBOCOPY     ::     Robust File Copy for Windows                              
-------------------------------------------------------------------------------
  Started : Thursday, November 5, 2015 10:20:47 AM
2015/11/05 10:20:47 ERROR 5 (0x00000005) Getting File System Type of Destination \\xxxftptst\xxxftparchive\xxx\inbound\
Access is denied.
   Source : D:\xxxFTPROOT\xxx\inbound\
     Dest - \\xxxftptst\xxxftparchive\xxx\inbound\
    Files : C45632002.ITM
  Options : /DCOPY:DA /COPY:DAT /R:1000000 /W:30
------------------------------------------------------------------------------
2015/11/05 10:20:47 ERROR 5 (0x00000005) Creating Destination Directory \\xxxftptst\xxxftparchive\xxx\inbound\
Access is denied.

The FTP service is running as SYSTEM (which can't be changed at this time).     The share (xxxftptst\xxxftparchive) have full permissions open to Everyone at this time, which continue into the \xxx\inbound subdirs.
I verified using diskpart on the target server to make sure the volume is not read only - it is not.

Does anyone have any ideas on what to check next? Thanks in advance!
Tanner CroweAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

NVITCommented:
AFAIK,  System can't copy to a network share. Is not allowed.
1
Tanner CroweAuthor Commented:
Thanks NVIT -- assuming you're correct that could be the problem.   I'll see what I can do about changing to a service account rather than System which it has been running under for year.   Unfortunately that requires me to bring down a busy prod ftp server, so it will take some planning.
0
SteveCommented:
Agreed. you need to ensure the robocopy runs under an account that exists on both the source & destination. this could be a network account or a local account that exists separately on both systems.
0
Lionel MMSmall Business IT ConsultantCommented:
I just created a test using SYSTEM to copy from Windows 2012 to Windows 2003 share using UNC by putting this command in a batch file
robocopy c:\utils \\sbserver\backup\test /xj /r:0 /w:0 /s /NFL /NDL /TEE
and it worked--copied C:\Utils with no errors (I did check the option to run with highest privileges though). May I suggest you try to create a network connection and try copying it that network drive instead of the UNC.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Kyle GustafsonCommented:
May I suggest you try to create a network connection and try copying it that network drive instead of the UNC.

Network connections or mapped drives only work when you have an interactive user (like a human that logins in) to the system.  If you want this to run in the background as a scheduled task regardless of whether a user is logged in or not, it needs to be a UNC path using a service account of some sort to access the drive.  If it is in an AD domain, you could run it using a dedicated service account or even NT Service and then give the computer account access to the remote share.  

Scripts that require interactive user sessions will be problematic in the long run, at least that is what I have seen when other admins where I work have set things up like this as it requires auto-logins to work right so the user is logged in after reboots for patches or other reasons, which raise other concerns (clear text password in registry and so on...).
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.