Command copy exited with code 4 when building - Visual Studio restart solves it

Question

Every now and then when I build my solution here (with 7 projects in it) I get the dreaded \'Command copy exited with code 4\' error, in Visual Studio 2010 Premium ed.

Answer 1

I faced same issue. I deleted post-build events and it started working. Some times when we add some SQL components it may add post build commands also.

Answer 2

What fixed it for me: dig down to the specific solution for the project you want i.e NOT the overall solution file for all the projects.

Do try - I tried everything else mentioned here but to no avail.

Answer 3

I faced the same issue in case of XCOPY after build is done. In my case the issue was happening because of READ-ONLY permissions set on folders.

I added attrib -R command before XCOPY and it solved the issue.

Hope it helps someone!

Answer 4

I had the same issue. It was caused by having the same flag twice, for example:

if $(ConfigurationName) == Release (xcopy "$(TargetDir)." "$(SolutionDir)Deployment\$(ProjectName)\" /e /d /i /y /e)

Observe that the "/e" flag appears twice. Removing the duplicate solved the issue.

Answer 5

Can be caused by VMWare Workstation with Shared Folders

I have the problem always when the destinatinon folder of the xcopy is also mapped as Shared Folder in a VM.

I solved it with a script running in the vm and deleting the content of the shared folder.

Answer 6

This can happen in multiple cases:

1. When the complete string path is longer than 254 chars.
2. When the name of the file to be copied is wrong.
3. When the target path is wrong.
4. When the readonly attribute is set on the copied file or target folder.