Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers. Visit Stack Exchange

Sitecore Stack Exchange is a question and answer site for developers and end users of the Sitecore CMS and multichannel marketing software. It only takes a minute to sign up.

Sign up to join this community

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

I tried to install Habitat and followed all the instructions mentioned at: https://github.com/Sitecore/Habitat/wiki/01-Getting-Started

When I run the default task as mentioned in step 5 of wiki, I keep on getting the following error (i have already executed npm install and npm install -g gulp-cli):

[10:44:53] Starting '03-Publish-All-Projects'... [10:44:53] Starting 'Build-Solution'... [10:44:53] { Error: spawn C:\Program Files (x86)\MSBuild\15.0\Bin\amd64\MSBuild. exe ENOENT at exports._errnoException (util.js:1020:11) at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32) at onErrorNT (internal/child_process.js:367:16) at _combinedTickCallback (internal/process/next_tick.js:80:11) at process._tickCallback (internal/process/next_tick.js:104:9) code: 'ENOENT', errno: 'ENOENT', syscall: 'spawn C:\Program Files (x86)\MSBuild\15.0\Bin\amd64\MSBuild.ex e', path: 'C:\Program Files (x86)\MSBuild\15.0\Bin\amd64\MSBuild.exe', spawnargs:
[ 'C:\Projects\Habitat\Habitat.sln', '/target:Clean;Build', '/verbosity:minimal', '/toolsversion:15.0', '/nologo', '/maxcpucount', '/nodeReuse:False', '/property:Configuration=Debug', '/property:Platform=Any CPU' ] } [10:44:53] MSBuild failed! [10:44:53] 'Build-Solution' errored after 36 ms [10:44:53] Error: spawn C:\Program Files (x86)\MSBuild\15.0\Bin\amd64\MSBuild.ex e ENOENT at exports._errnoException (util.js:1020:11) at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32) at onErrorNT (internal/child_process.js:367:16) at _combinedTickCallback (internal/process/next_tick.js:80:11) at process._tickCallback (internal/process/next_tick.js:104:9) [10:44:53] 'default' errored after 2.12 s [10:44:53] Error in plugin 'run-sequence(Build-Solution)' Message: spawn C:\Program Files (x86)\MSBuild\15.0\Bin\amd64\MSBuild.exe ENOENT Details: code: ENOENT errno: ENOENT syscall: spawn C:\Program Files (x86)\MSBuild\15.0\Bin\amd64\MSBuild.exe path: C:\Program Files (x86)\MSBuild\15.0\Bin\amd64\MSBuild.exe spawnargs: C:\Projects\Habitat\Habitat.sln,/target:Clean;Build,/verbosity:mi nimal,/toolsversion:15.0,/nologo,/maxcpucount,/nodeReuse:False,/property:Configu ration=Debug,/property:Platform=Any CPU Stack: Error: spawn C:\Program Files (x86)\MSBuild\15.0\Bin\amd64\MSBuild.exe ENOENT at exports._errnoException (util.js:1020:11) at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32) at onErrorNT (internal/child_process.js:367:16) at _combinedTickCallback (internal/process/next_tick.js:80:11) at process._tickCallback (internal/process/next_tick.js:104:9) [10:44:53] '03-Publish-All-Projects' errored after 49 ms [10:44:53] Error in plugin 'run-sequence(default)' Message: spawn C:\Program Files (x86)\MSBuild\15.0\Bin\amd64\MSBuild.exe ENOENT Details: code: ENOENT errno: ENOENT syscall: spawn C:\Program Files (x86)\MSBuild\15.0\Bin\amd64\MSBuild.exe path: C:\Program Files (x86)\MSBuild\15.0\Bin\amd64\MSBuild.exe spawnargs: C:\Projects\Habitat\Habitat.sln,/target:Clean;Build,/verbosity:mi nimal,/toolsversion:15.0,/nologo,/maxcpucount,/nodeReuse:False,/property:Configu ration=Debug,/property:Platform=Any CPU Stack: Error: spawn C:\Program Files (x86)\MSBuild\15.0\Bin\amd64\MSBuild.exe ENOENT at exports._errnoException (util.js:1020:11) at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32) at onErrorNT (internal/child_process.js:367:16) at _combinedTickCallback (internal/process/next_tick.js:80:11) at process._tickCallback (internal/process/next_tick.js:104:9) [10:44:53] '03-Publish-All-Projects' errored after 58 ms [10:44:53] Error in plugin 'run-sequence(Build-Solution)' Message: spawn C:\Program Files (x86)\MSBuild\15.0\Bin\amd64\MSBuild.exe ENOENT Details: code: ENOENT errno: ENOENT syscall: spawn C:\Program Files (x86)\MSBuild\15.0\Bin\amd64\MSBuild.exe path: C:\Program Files (x86)\MSBuild\15.0\Bin\amd64\MSBuild.exe spawnargs: C:\Projects\Habitat\Habitat.sln,/target:Clean;Build,/verbosity:mi nimal,/toolsversion:15.0,/nologo,/maxcpucount,/nodeReuse:False,/property:Configu ration=Debug,/property:Platform=Any CPU Stack: Error: spawn C:\Program Files (x86)\MSBuild\15.0\Bin\amd64\MSBuild.exe ENOENT at exports._errnoException (util.js:1020:11) at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32) at onErrorNT (internal/child_process.js:367:16) at _combinedTickCallback (internal/process/next_tick.js:80:11) at process._tickCallback (internal/process/next_tick.js:104:9)

Any suggetions to fix the error?

Thanks in advance.

Nicks

The default Habitat repo has major dependencies on Node, NPM, Gulp and other tooling that is very problematic for developers. If you just want the site locally, and have a TDS license, I'd suggest using the TDS fork and just doing Deploy Solution. github.com/HedgehogDevelopment/Habitat/tree/TDS-latest . It simplifies it. Note: this is a comment, not an answer, as I know it doesn't resolve your specific build problem....but it resolves mine! :-) – Sean Holmesby Sep 17, 2018 at 3:40 i was also facing the same issue, but now fixed after changing buildtoolversion from 15.0 to 14.0 – Pradeep Gupta Mar 27, 2018 at 14:48

I was able to determine this 'auto' value, looking at the logic on the gulp-msbuild\lib\msbuild-finder.js

You can find more details in the below blog link.

https://sivalingaamorthy.wordpress.com/2018/09/17/error-spawn-cprogram-files-x86msbuild15-0binamd64msbuild-exe-enoent/

Thanks for the update but even after implementing the suggested changes I am still getting the same error. Any other suggestions? – Nicks Aug 16, 2017 at 5:19 Two suggestions: 1. Check if you have the latest NodeJS version installed in your computer. 2. Delete the folder node_modules and then run npm install again – João Neto Aug 16, 2017 at 6:54

Thanks for contributing an answer to Sitecore Stack Exchange!

• Please be sure to answer the question . Provide details and share your research!

But avoid …

• Asking for help, clarification, or responding to other answers.
• Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers .