I am getting the above error while I am using robocopy command. I have given all possible permissions on both source and destination folders but still I am getting this error. Any idea how to fix this.
3 Answers
Is this to and from ntfs partitions?
If you are coping to FAT of EXT then add the /FFT parameter to assume FAT file times (2 second granularity) ext2/ext3 also uses 2 second granularity.
You could also try using the /COPY:DT parameter, by default robocopy copies the data, attributes and timestamp /COPY:DT will skip the attributes.
Also check your share permissions as well as your ntfs permissions

- 208
- 1
- 6
-
2Yes, it is to and from ntfs and also shared the folder on network as well as full permissions on both source and destination folders. Still it is giving me same error. Also tried by using COPY:DT. but nothing seems to work. – sam Jul 18 '11 at 13:52
-
Did the `/FFT` parameter solve the issue? – Glemi Dec 13 '22 at 09:05
For me it worked fine when I ran the command directly on the server, but when I ran it from PowerShell remoting I would get this error. I was also trying to copy files from the local machine to a network share. The fix for me was to use:
Invoke-Command -ComputerName $sourceServer -Credential $credential -Authentication Credssp -ScriptBlock {
& RoboCopy "C:\Source" "\\OtherServer\C$\Destination" /E
}
Specifically, using -Credential $credential -Authentication Credssp
fixed the issue for me.
You didn't provide enough info to know if this is the same issue you were having, but thought I'd mention it for others who encounter the same error message.

- 22,611
- 14
- 112
- 118
It may be a simple answer... check the space left on the Target drive.
-
Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jul 09 '23 at 13:18