I have a solution on VS 2010 that has been building without errors, then out of no where the build started failing with the following error :-
**error MSB3073: The command "xcopy "C:\Program Files\Microsoft SDKs\Kinect\Developer Toolkit v1.5.1\Redist\amd64\FaceTrackLib.dll" "C:\Users\HP\Documents\FaceTrackingVisualization\Out\SingleFace\x64\Debug\" /eiycq
xcopy "C:\Program Files\Microsoft SDKs\Kinect\Developer Toolkit v1.5.1\Redist\amd64\FaceTrackData.dll" "C:\Users\HP\Documents\FaceTrackingVisualization\Out\SingleFace\x64\Debug\" /eiycq
:VCEnd" exited with code 9009. C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets 113 6 SingleFace**
I have no idea, in the solutions online people say to look for spaces or indentation errors but i dont understand where to edit these changes.. the error points me to these code lines the error line is the bold line
Target Name="PostBuildEvent" Condition="'$(PostBuildEventUseInBuild)'!='false'"
Message Text="Description: %(PostBuildEvent.Message)" Condition="'%(PostBuildEvent.Message)' != '' and '%(PostBuildEvent.Command)' != ''"/
**Exec Command="%(PostBuildEvent.Command)$(BuildSuffix)" Condition="'%(PostBuildEvent.Command)' != ''"/**
/Target
How do I fix error code 9009? Download Outbyte PC Repair application See more information about Outbyte; uninstall instructions; EULA; Privacy Policy. Click the Scan Now button to detect issues and abnormalities. Click the Repair All button to fix the issues.
Error Code 9009 means error file not found. All the underlying reasons posted in the answers here are good inspiration to figure out why, but the error itself simply means a bad path.
In my case i had to change $(MSBuildBinPath)\msbuild.exe in my Post-build events to "$(MSBuildBinPath)\msbuild.exe" because the path contained blanks.
As a side note: i only had to do that in VS 2013 - both VS 2012 and 2010 could handle this without the quotes.
This will happen when some crappy installer has destroyed the system environment, particularly the PATH environment variable. So msbuild can no longer execute the xcopy.exe program.
Get basic diagnostics by starting a command prompt and typing PATH
. Verify that you see c:\windows\system32 listed. Then type where xcopy.exe
and verify that you get only one hit, the one in c:\windows\system32. Then type xcopy /?
to verify that you can run xcopy. If you don't know how to fix it then ask at superuser.com
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With