Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation on Windows (win7) fails #240

denised opened this issue Sep 11, 2013 · 4 comments

Installation on Windows (win7) fails #240

denised opened this issue Sep 11, 2013 · 4 comments


Copy link

@denised denised commented Sep 11, 2013

When I try npm install ws (on my win7 machine), I get the following errors:

C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\Microsoft.Cpp.x64.Targets(152,5): error MSB6006: "CL.exe" exited with code
-1073741515. [D:\Sandbox Consulting\node_modules\ws\build\bufferutil.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\Microsoft.Cpp.x64.Targets(152,5): error MSB6006: "CL.exe" exited with code
-1073741515. [D:\Sandbox Consulting\node_modules\ws\build\validation.vcxproj]

I am using npm 1.2.32 and node 0.10. I have just re-installed Visual Studio 2010 Express for Windows Phone, the win 7.1 sdk and python 2.7.5. I was getting a slightly different error message before. However both times, the errors seem to be about some inconsistency between MSBuild and the vcxproj files.

Googling, you can see quite a few questions about npm install errors on windows, sometimes stemming from trying to install bcrypt. My suspicion is that these issues are related, and may be related to an internal inconsistency snafu with MS products, as discussed here: But in my case, following their advice did not fix the problem for me (though it did change the error message)

I'm not enough of a windows dev to really debug the problem. And I don't know how the build process is supposed to work on windows (how are the vc project files being generated, for example). But I think if someone figures it out, there are a lot of related issues out there that would be fixed.

Copy link

@MichaelPaulukonis MichaelPaulukonis commented Sep 13, 2013

I also failed to install ws, but got a different error message.

Here is the relevant chunk of the npm log:

487 verbose about to build C:\Users\mpaulukonis\AppData\Roaming\npm\node_modules\ws
488 info build C:\Users\mpaulukonis\AppData\Roaming\npm\node_modules\ws
489 verbose from cache C:\Users\mpaulukonis\AppData\Roaming\npm\node_modules\ws\package.json
490 verbose linkStuff [ true,
490 verbose linkStuff 'C:\Users\mpaulukonis\AppData\Roaming\npm\node_modules',
490 verbose linkStuff true,
490 verbose linkStuff 'C:\Users\mpaulukonis\AppData\Roaming\npm\node_modules' ]
491 info linkStuff ws@0.4.30
492 verbose linkBins ws@0.4.30
493 verbose link bins [ { wscat: './bin/wscat' },
493 verbose link bins 'C:\Users\mpaulukonis\AppData\Roaming\npm',
493 verbose link bins true ]
494 verbose linkMans ws@0.4.30
495 verbose rebuildBundles ws@0.4.30
496 verbose rebuildBundles [ 'commander', 'nan', 'options', 'tinycolor' ]
497 info install ws@0.4.30
498 verbose unsafe-perm in lifecycle true
499 silly exec cmd "/c" "(node-gyp rebuild 2> builderror.log) || (exit 0)"
500 silly cmd,/c,(node-gyp rebuild 2> builderror.log) || (exit 0),C:\Users\mpaulukonis\AppData\Roaming\npm\node_modules\ws spawning
501 info ws@0.4.30 Failed to exec install script
502 info C:\Users\mpaulukonis\AppData\Roaming\npm\node_modules\ws unbuild
503 verbose from cache C:\Users\mpaulukonis\AppData\Roaming\npm\node_modules\ws\package.json
504 info preuninstall ws@0.4.30
505 info uninstall ws@0.4.30
506 verbose true,C:\Users\mpaulukonis\AppData\Roaming\npm\node_modules,C:\Users\mpaulukonis\AppData\Roaming\npm\node_modules unbuild ws@0.4.30
507 verbose C:\Users\mpaulukonis\AppData\Roaming\npm,[object Object] binRoot
508 info postuninstall ws@0.4.30
509 error ws@0.4.30 install: (node-gyp rebuild 2> builderror.log) || (exit 0)
509 error spawn ENOENT
510 error Failed at the ws@0.4.30 install script.
510 error This is most likely a problem with the ws package,
510 error not with npm itself.
510 error Tell the author that this fails on your system:
510 error (node-gyp rebuild 2> builderror.log) || (exit 0)
510 error You can get their info via:
510 error npm owner ls ws
510 error There is likely additional logging output above.
511 error System Windows_NT 6.1.7601
512 error command "d:\dev\nodejs\node.exe" "d:\dev\nodejs\node_modules\npm\bin\npm-cli.js" "install" "-g" "ws"
513 error cwd D:\temp\WebText
514 error node -v v0.10.5
515 error npm -v 1.2.18
516 error syscall spawn
517 error code ELIFECYCLE
518 error errno ENOENT
519 verbose exit [ 1, true ]

Copy link

@MichaelPaulukonis MichaelPaulukonis commented Sep 13, 2013

If I run the shell as administrator and attempt a global install, it works just fine.

The installation instructions could be updated to reflect this.

Copy link

@jcollum-hcg jcollum-hcg commented Sep 13, 2013

This is from experience: developing in Node on Windows is a PITA. I went to an Ubuntu VM and am very happy with that decision.

Copy link

@heri16 heri16 commented Jan 5, 2015

28\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
MSBUILD : error MSB4132: The tools version "2.0" is unrecognized. Available tools versions are "4.0".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.